TheBigRoomXXL

How the data is stored and persisted ? Is is just an index dumped to the filesystem?

You can add X-Clacks-Overhead as a custom header. Nice.

tinyfeed creator here, looks like it's already been a coople of days since this has been shared, but I am available if you have any questions.

It's always lovely to see tinyfeed appear randomly on the internet :-)

A fun hack to improve my workflow.

Very interesting concept. Im going to keep an eye open for a new project where I can test that.

I was about to comment there is some interesting intersection with residuality theory but then you mentioned it ^^

> Traditionally, lightning protection has relied heavily on lightning rods. However, their protective range is limited, and in some cases—such as wind turbines or outdoor event venues—it may not be feasible to install them. At NTT, we are exploring the use of rapidly advancing drone technology to create a new approach: "drone-triggered lightning"2.

I can't believe that's a practical solution. Surely just installing more lighting road is simpler et more effective. They just want to do something cool and try to justify it sideways.

I’m really curious to see how productive it actually is to use something like that. This combination of a framework, database, and infrastructure all in one package seems to simplify things, but I wonder if everything falls apart the moment you try something a little 'outside the box' or unusual.

One year ago i started to work on TinyFeed, I didn't like existing solutions for feeds reader. Many of them seemed overly complex, most of them require a database (and didn't event support sqlite). For a simple feed reader, it felt overkill. What I wanted was an easy to setup app and with a clear and minimal interface like HN. Now, I’m happy to announce that it has slowly improved since then. It’s now reaching its first stable release, version 1.0!

The latest release highlights:

- Daemon mode: Supports background operation for continuous feed updates, allowing TinyFeed to run as a service on a server or a laptop.

- Interface redesign: A simpler, more readable web page.

More generally it protects against anybody who has access to the database, including bad actors if it's leaked.

I don't think it protects against timing attack because the common way of doing it is just to use sha256 and use the resulting hash to do a lookup in the database. This is not a fixed time operation

I have been thinking about the sync-only-server model for sometime and providing a way to use application specific logic, like CRDT, while keeping the server generic has been a major headache for me.

This solution/pattern is the best I have seen so far. It does not require anything special server side, all the logic live on the client, which also make plugins way easier.

Thank you!

Look great. I am going to try it this afternoon!