Either publishing server should serve the metadata - although it would be prone to bad actors, so a refetch in the next 0-180 seconds would be appropriate. Or just add a random 0-60 second delay before fetching the data.

Absolutely LOVE this idea but I feel like a solid implementation would be a pain in the fanny (and it also requires other peers to be online). I dip in and out over the day myself but I don’t know what others use case is.

Also it is far less trustworthy and harder to block bad actors (V’s removing a known bad actor from a relatively small peer group).

I’ve always been a supporter of your work, but I’m tired of all the fake promises, the “soon” you always say without shipping anything, how you often say “it’s released” when it’s just in the code so no, it’s not release for the people actualy using the software because you didn’t make a new release yet. I know software development takes time and love, especially when working solo, but not a reason to create fake promises or hopes.

Also, you used a framework that was clearly AI assisted itself : github.com/nuxt/nuxt So this is the reason why I thought the new fedidb was AI assisted, I was talking more about the UI (not the content itself).

Anyway sorry for calling something wrong on my part in my last comment.

I really want you to build cool stuff, and I want to like you for it, but for now I don’t see the cool stuff that much anymore…

forgot that in ~2002 i had rrdtool graphs of all my shit just sitting on the open internet intentionally. and nowadays i mostly don't want packets at all unless they're signed by a key i know.

@davidgerard
The need for AI agents is due t the enshittification of online services. They won't provide a sensible, stable API that could reasonably be automated because they want to do thigs like upselling. Hence the need for an indeterminate interface like a slop engine.

@lightweight Yes working for me too, now. Odd. Cheers :)

I shared a link from NPR Tiny Desk but there was no image preview or video embed. After investigating this I learned that when you do that, each instance picks up the link and individually retrieves the link preview nearly simultaneously. For gargantuan sites like YT or Reddit, this is a trivial amount of traffic and not a problem, but for smaller sites like NPR this results in a sort of botnet DDOS attack on the site’s servers. More here. Another example here . For that reason, NPR has blocked Fediverse servers like Mastodon.

I have experienced this on my personal server as well (DDOS), but at the time didn’t know why, exactly.

This isn’t the end of the world, but certainly is not great and hurts engagement with the content. Is there a solution for this? Perhaps using some sort of webtorrent service like PeerTube where they just fetch the information from another fediverse server instead of the source server? Maybe fetching embeds client-side? At least that would stagger the requests.

New on our blog: The Trouble With Post Tracks by Mirlo

https://mirlo.space/team/posts/800

Support Mirlo: https://mirlo.space/team/tip ❤️🐦‍⬛

#Music #Mirlo #Blog #Blogs #MusicNews #FediMusic #Fediverse #Musicians

The day started with a major Google Cloud outage in Europe, proceeded swiftly to the eMudhra root cert dumpsterfuck, and now the critical PHP vulns are starting to hit.

Cool, cool.

#InfoSec

@djsundog FOUR DID NOTHING WRONG

@arrjay @djsundog 4 was not valued.

everybody’s shitting on using 4 because it’s supposed to be hard to guess but if everybody’s surprised then no one would have guessed 4 really so it fit the bill. it’s not 4’s fault.

@RickiTarr

Advertising my new service for certificate authorities: Key Checker Secure™

Upload your certificate, including private key, to our web site (secured with a highly trusted eMudhra intermediate certificate) and we will perform numerous checks on it, including:
• Too many 0 bits
• Not enough 0 bits
• Key looks suspiciously like ASCII
• Key contains a song lyric
• Someone else already uses this key

Upload your key now!