Searching We Love Privacy Club

Twts matching #cache
Sort by: Newest, Oldest, Most Relevant
lyse
lyse.isobeef.org
 (1y ago)
↳ In-reply-to » This was a bit of a challenge. Wanted to see if I can make a small version, combining the best/most interesting parts, of the previous ones. Like the black lines separating each colour, an interesting pose, more anatomically correct legs... something of a best of the 2025, profile picture. Media

@thecanine@twtxt.net Woof woof! That’s a nice one. For a split second, the posture and the back legs reminded me of

Image

that I never had, but always wanted as a child.

⤋ Read More
bender
twtxt.net
 (1y ago)
↳ In-reply-to » The most infuriating 3 seconds of using this Mac every day are the first time I run man and it calls home to see if I'm allowed to do that.

Because OP twtxt seems to be a cross-post from the Fediverse, I am bringing some context here. It refers to this GitHub issue. This comment explains why the issue described is happening:

This is usually due to notarization checks. E.g. the binaries are checked by the notarization service (‘XProtect’) which phones home to Apple. Depending on your network environment, this can take a long time. Once the executable has been run the results are usually cached, so any subsequent startup should be fast.

OP network must be running on 1,200 Baud modem, or less. 🤭 I have never, ever, experienced any distinguishable delays.

⤋ Read More
lobste_rs
feeds.twtxt.net
 (1y ago)

Streaming live video as a macOS screensaver using AVFoundation and yt-dlp
I built this to play live HLS streams as a screensaver on macOS. It supports both direct .m3u8 URLs and YouTube
links (via yt-dlp extraction with caching).

The interesting bits:

  • Cross-screen synchronization: All displays show the same frame of the video by syncing to a shared timestamp,
    making it feel like one continuous stream across monitors
  • Handles the unreliable macOS screensaver lifecycle (stopAnimation doesn’t always get called when … ⌘ Read more

⤋ Read More
lyse
lyse.isobeef.org
 (1y ago)
↳ In-reply-to » @lyse Thanks, I think I fixed it now. Sorry for the spam.

@itsericwoodward@itsericwoodward.com No worries, all good, mate! We all have to start somewhere. Other software requests my feed several orders of magnitude more often.

I can confirm, the User-Agent header appears to be fixed. \o/

Two other things I noticed, though:

  1. There’s now an OPTIONS request for my feed coming from something that claims to be Firefox, pointing to your feed URL in the query. No clue what this is about. In any case, it’s rejected with a 405 Method Not Allowed.

  2. Not that these few requests bother me at all, but you might wanna implement caching next with either the If-Modified-Since or If-None-Match request headers. This way, if the feed hasn’t changed, the web server can reply with a 304 Not Modified and no body at all, saving unnecessary traffic. But again, this is really not an issue for me at all. I just wanted to make sure you’re aware of it, that’s all. It might be even already on your agenda. Or you might decide to never do anything about it, which is also fine for me. :-)

⤋ Read More
itsericwoodward
itsericwoodward.com
 (1y ago)

I finally solved the loading issue in my WIP reader, TwtStrm (and apologies again to anyone that got spammed while I was diagnosing the issue).

After another round of coding this weekend, I’m happy to report that it now renders all the twts (with markdown parsing), complete with localstorage and server-based file caching.

⤋ Read More