Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Publish on your own site, syndicate elsewhere

indieweb.org

Post reply on HN
Print view View original

231–240 of 261 posts

Re: Publish on your own site, syndicate elsewhere

#231

Post by wwweston »

_heimdall wrote: post #220
wwweston wrote: post #213

Earlier quoted context omitted.

XSLT is the solution domain specialists and philosophers. Abandoning it is the vote of the market and market interests, the wisdom of crowds at work. This is the era of scale not expertise, enjoy the fruits.

Its more the market makers that made the vote rather than the market itself.

Effectively no one was using XSLT at any point (certain document pipelines or Paul Ford like indie hackers being the exceptions that proved the rule). Browsers keep all kinds of legacy features, of course, and they could well have kept this one, and doing so would’ve been a decision with merit. But they didn’t, and the market will ratify their decision. Just like effectively no one was using XSLT, effectively no one will change their choice of browser over its absence.

Re: Publish on your own site, syndicate elsewhere

#232

Post by Zak »

pwdisswordfishy wrote: post #204
data_base wrote: post #83

Earlier quoted context omitted.

I use RSS Style[1] to make the RSS and Atom feeds for my blog human readable. It styles the xml feeds and inserts a message at the top about the feed being meant for news readers, not people. Thus technically making it "safe" for less tech savvy people. [1]: https://www.rss.style/

> message at the top about the feed being meant for news readers There's no real reason to take this position. A styled XML document is just another page. For example, if you're using a static site generator where the front page of your /blog.html shows the most recent N posts, and the /blog/feed.xml shows the most recent N posts, then...?

A reason to add that explanation to a styled RSS feed is to teach visitors what newsreaders are.

Re: Publish on your own site, syndicate elsewhere

#233

Post by Fileformat »

neilv wrote: post #91
data_base wrote: post #83

Earlier quoted context omitted.

I use RSS Style[1] to make the RSS and Atom feeds for my blog human readable. It styles the xml feeds and inserts a message at the top about the feed being meant for news readers, not people. Thus technically making it "safe" for less tech savvy people. [1]: https://www.rss.style/

What about Google killing XSLT? https://developer.chrome.com/docs/web-platform/deprecating-x...

RSS.style is my site. I'm currently testing a JavaScript-based workaround that should look just like the current XSLT version. It will not require the XSLT polyfill (which sort-of works, but seems fragile).

One bonus is that it will be easier to customize for people that know JavaScript but don't know XSLT (which is a lot of people, including me).

You'll still need to add a line to the feed source code.

Re: Publish on your own site, syndicate elsewhere

#234

Post by vegabook »

dingnuts wrote: post #16
vegabook wrote: post #15

This post like many recent ones like it, essentially wants the internet to go backwards to what it once was pre-LLMs [edit: and pre-concentration]. I'd like to suggest that you should follow through and go all the way to pre-internet itself, and rediscover handwriting, in-person local meeting groups, non-digital relationships, and using your hands not on a keyboard. Today I (with difficulty) left my macbook closed al…

I understand this attitude but when I look back at my rural youth I just hear you telling me that I should have had no one to talk to at all about many things. Let's not throw out the baby with the bathwater

You should treasure said rural youth because such lonely luxuries are rare, and will be even more so in the future. Spoken as a rural youth myself.

Re: Publish on your own site, syndicate elsewhere

#235

Post by lazarus01 »

ArcHound wrote: post #228
lazarus01 wrote: post #185

Earlier quoted context omitted.

I agree. To be more clear, that $60 is an estimate for a small configuration and includes serverless infrastructure to process 500,000 requests per month, plus storage, including a 20gb sql database and 100gb of object storage to serve video and images. More ideal for an application. You run the app in a container and only get charged for the requests, the sql database is persistent, so that cost $20/month and object…

Let me describe my setup, so that you can compare. I use a Contabo VPS for around 5 USD month to host my Wagtail (django-based) site. The DB also runs on the same infra and since it's SQLite I can back it up externally. I probably wouldn't be able to handle 0.5M requests, but I am nowhere near getting them. If I start approaching such numbers I'll consider an upgrade. Check out Wagtail if you'd like to have even more…

Thank you for sharing your setup, I will certainly examine it and compare a bit later. I know my setup is a bit over the top, but it is the easiest to learn, since I live in gcp everyday. I certainly don't expect the .5m traffic, but that is one of the lower tiers for cloud run, serverless execution service. This is just a poc to get my fingers dirty with the MVT pattern.

Re: Publish on your own site, syndicate elsewhere

#236

Post by pwdisswordfishy »

Zak wrote: post #232
pwdisswordfishy wrote: post #204

Earlier quoted context omitted.

> message at the top about the feed being meant for news readers There's no real reason to take this position. A styled XML document is just another page. For example, if you're using a static site generator where the front page of your /blog.html shows the most recent N posts, and the /blog/feed.xml shows the most recent N posts, then...?

A reason to add that explanation to a styled RSS feed is to teach visitors what newsreaders are.

A message explaining what feeds and feedreaders are would suffice for that.

Re: Publish on your own site, syndicate elsewhere

#237

Post by senfiaj »

pwdisswordfishy wrote: post #202
susam wrote: post #37

Also, don't forget to set up an RSS or Atom feed for your website. Contrary to the recurring claim that RSS is dead, most of the traffic to my website still comes from RSS feeds, even in 2̶0̶2̶5̶ 2026! In fact, one of my silly little games became moderately popular because someone found it in my RSS feed and shared it on HN. [1] From the referer (sic) data in my web server logs (which is not completely reliable but s…

Please also enable CORS[1] for your RSS feed. (If your whole site is a static site, then please just enable CORS site-wide. This is how GitHub Pages works. There's pretty much no reason not to.) Not having CORS set up for your RSS feed means that browser-based feed readers won't be able to fetch your feed to parse it (without running a proxy). 1. https://enable-cors.org/ >

You can try https://corsproxy.io/ as a workaround.

Re: Publish on your own site, syndicate elsewhere

#238

Post by jetbalsa »

wwweston wrote: post #231
_heimdall wrote: post #220

Earlier quoted context omitted.

Its more the market makers that made the vote rather than the market itself.

Effectively no one was using XSLT at any point (certain document pipelines or Paul Ford like indie hackers being the exceptions that proved the rule). Browsers keep all kinds of legacy features, of course, and they could well have kept this one, and doing so would’ve been a decision with merit. But they didn’t, and the market will ratify their decision. Just like effectively no one was using XSLT, effectively no one…

Blizzard used to use it for their entire WoW Armory website to look people up, They converted off it years ago, but for awhile they used XML/XSLT to display the entire page

Re: Publish on your own site, syndicate elsewhere

#239

Post by pwdisswordfishy »

mark_l_watson wrote: post #189

Q: While I agree strongly with the philosophy of this article, and twice I have set up static site generators for blogs hanging underneath my top level personal domain markwatson.com, each time I cause I could only blog when sitting at my computer, not when I was using an iPad or iPhone (I limit my daily time at a computer to just a few writing and coding sprints, otherwise I literally put my laptop away - out of sig…

You could use Substack/Blogspot/Mastodon themselves as your "static site generator".

POSSE (the concept linked here) is overrepresented in relation to revealed preference. PESOS (publish elsewhere, syndicate on site) is more compatible with how most people (including nerds) actually use the Internet; for all the talk about static site generators and "owning" your own "digital garden" >9/10 people would fall somewhere on the embarrassing part of the curve from the "Blogging vs. Blog Setups" comic. https://rakhim.org/honestly-undefined/19/>

If you migrated to a fediverse instance with longer post length limits, you could use that to actually blog/post while mobile, and meanwhile you have a script on your homepage that "lazily" syncs those posts to your static site—

When anyone visits your homepage, they see your site as it was when you last built it.

When you visit your own homepage, it automatically fetches your social media feed, patches the previous input to the SSG with the new content, and then uses the APIs of whatever you're using to host your site for rolling out the new posts.

Re: Publish on your own site, syndicate elsewhere

#240

Post by _heimdall »

wwweston wrote: post #231
_heimdall wrote: post #220

Earlier quoted context omitted.

Its more the market makers that made the vote rather than the market itself.

Effectively no one was using XSLT at any point (certain document pipelines or Paul Ford like indie hackers being the exceptions that proved the rule). Browsers keep all kinds of legacy features, of course, and they could well have kept this one, and doing so would’ve been a decision with merit. But they didn’t, and the market will ratify their decision. Just like effectively no one was using XSLT, effectively no one…

Its hard to judge usage when browsers stopped maintaining XSLT with the 1.0 spec. V1.0 was very lacking in features and is difficult to use.

Browsers also never added support for some of the most fundamental features to support XSLT. Page transitions and loading state are particularly rough in XSLT in my experience.

Post reply on HN