this post was submitted on 09 May 2025
21 points (86.2% liked)

Selfhosted

46654 readers
474 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Oh technomages of c/selfhosted, I come seeking your help once more because anywhere I look there's people trying to sell me on their service, something-something PODCASTS, or RSS for windows and all that, my brain cannot anymore.

I've got a blog I'm serving with nginx, and I would like to implement some sort of RSS feed. I'm pretty much new to the whole thing, but it was recommended to me. I did a bit of research and now I know those are like xml files that you subscribe to.

So, I wanted to know: In your experience, what is the best way to go about this? Do I have to make them myself by hand and put them in an /rss/ directory in the root of my blog? How do people subscribe to them? Got any resources?

I wouldn't mind writing them by hand actually, my whole website is hand-made, gluten free and organic. (maybe not the last one).

Thanks in advance <3

you are viewing a single comment's thread
view the rest of the comments
[–] 486@lemmy.world 3 points 4 days ago (2 children)

This is not quite true. As I mentioned in my other comment already, each feed entry needs its own unique UUID. You have to generate such a UUID for every entry.

[–] exu@feditown.com 13 points 3 days ago (1 children)

Per the RSS specification the guid field is optional.

And if you do want to provide it, any string works. So just count up from 1, use the title, current date or whatever for that field.

[–] 486@lemmy.world 4 points 3 days ago (1 children)

Thanks for pointing this out. I thought this had to be an actual UUID. Generating a unique string of arbitrary format manually is certainly much easier to do manually without additional tools.

[–] arjache@fedia.io 4 points 3 days ago

it can also just be the permalink for the post, which each post ought to have anyway. in RSS you can set isPermaLink=“true” on the guid to indicate it’s a permalink.

[–] akademy@lemm.ee 3 points 3 days ago

It's pretty easy to create a uuid. There are many ways to do it. Which is best for you would depend on how you're generating your website.