projek01.neocities.org

Hi I kinda started a project like this bsky.app/profile/love...

I thought this was a really weird tweet

Unfortunately, the For You timeline here that everyone uses is just hosted by one person and not officially supported, so it understandably has relatively frequent downtime. I wish Bluesky itself had a good algorithm to start with.

It's actually working out quite well!!

There are many places where the old Twitter API, on the other hand, would actually request the same information again. I'm bound by the same interfaces that they originally designed, mostly because I just do not want to unnecessarily deviate.

The thing that I'm seeking to cache in question are network response contents in order to avoid making repeated requests that will be reused in the immediate future, say the next half hour.

With Twitter, I want to avoid this, because the API has a rate limit.

Perhaps in the future I'll write a native service for Windows, since the principle is the same, but then again, it would probably be better to add support for a common PHP extension that augments the webserver itself with memory caching.

It feels very improper (first and foremost, I would prefer to write a native Windows service, but that is out of the question here...), but I find it to be an advantageous design simply to avoid killing users' SSDs.

On the off chance that a user's environment cannot do this, or if the user prefers to not run a daemon, on disk cache can be used instead. I just prefer not to for very short time caches, because it wastes precious limited write cycles to a SSD.

I came up with a "simple" solution. Basically every PHP installation comes with sockets and can spawn processes on the user's system, including our primary target environment, XAMPP. Thus, in PHP alone, you can achieve persistent storage by writing a daemon script and using sockets to facilitate IPC

It's kinda funny because I wrote the code for this, but I really didn't expect it to come together first try.