I would like to note that tinytinyrss has a bigger binary size than tinyfeed, making tinyfeed the tiniest option despite the misleading name

/s

Lots of options to handle your feeds on a self hosted setup. What are your criteria? What are you trying to achieve? We need something specific to make recommendations.

I would argue that where tinyfeed shines is that it does not require any dependency of any kind: not database to setup, not configuration, no nothing. You just give it a list of feeds and it generates a page for you. What you do with that page is up to, so it adapts well to lots of workflow. The trade off with that approach is that it is stateless so if you like to do bookkeeping (like read later / favorites features) then it's not for you.

As the other said, this is the rules of the community.

I like the disclosure part, not so much the [IAP] in the title, I would not personally characterize my project as an "IA project" but I understand waiting to promote 100% IA free projects.

Oh, that's very cool. We don't see that kind of lower-level app very often in Go. I discovered SPAs through this post, and one thing I don't understand is how it works on the client side. It seems to break most protocols, doesn't it?"

Not sure I want a vibe-coded (or vibe-ported) SDT library. All of those AI ports seem to have a lot of marketing but not many users, so it’s difficult to get any feedback on their actual quality.

But the mascot is great!

In the grass

Mostly no AI. I use it to review doc because I make a lot of typo / spelling error as English is not my first language. Recently I also used it to accelerate writing test cases but that's all.

This is not a recent or "fast" projet, I have been slowly improving it for 3 years now :-D

The easy version to see how cute she is

Bitbucket lol .I would rather not.

I used to love gitlab (great CI!) but the quality is really going down. Everything is slow and there UI is full of bugs (god I hate there virtual srolll in epics).

There is also sourcehut. They have the best CI for me but sadly issue / merge request management is mail based.

Gitea looks like it is going the gitlab way with enterprise support and cloud because they need to make money.

Forgejo is cool (how do you prononce it?) but I am really sad they based there CI on github action.

FINALLY! Caddy has been doing it for years! I still prefere caddy overall but it's nice to have as we don't always choose the stack we work with.

Learning auto-completion isn’t very fun at first, but adding it to your own tool feels great. A while ago, I made a small script to assume any role in AWS CLI with SSO, and once I added auto-completion, it was faster and felt great. It's the kind a details that make a difference.

Indeed I am human ! (That's what a bot would say 🤖)

This article is light on details. If you want some context on the new Green Tea garbage collector you can check out the actual issue: https://github.com/golang/go/issues/73581

Exactly.

the first piece of the Astral platform

Because obviously, everything need to be a platform when you are VC backed... 😮‍💨

The routing feature is so cursed XD

I don’t plan on adding thumbnails, as they go against my initial vision for tinyfeed as a text-first UI like lobste.rs. However! one of tinyfeed’s core tenets is flexibility and customization, so if you want thumbnails, you can simply create your own template. If you need help you can open an issue, I would gladly help.

Outside ou the bug tracker and mailing list they also use git web, which is a built it web interface for a git.

https://git.ffmpeg.org/gitweb

https://git-scm.com/docs/gitweb

Drag and drop isn't for me either but it's nice to have more beginners-friendly options in the self hosted community. Not everybody like to live in the terminal.

Just like the other comment said, tinyfeed is not what you are looking for, it's goal is simply to be an aggregator for links, not content.

I have thought about it but I don't think it's possible because of CORS. Every site would need to have Access-Control-Allow-Origin: * on there favicon for it to work. Usually this would be sidestep by a proxy in the backend but the goal of tinyfeed is to be a static page generator, not a full HTTP server. Sorry 😔.