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.

E: Many people have replied comparing this to the Reddit “hug of death” or “The Slashdot effect”. This is not the same at all. Those are legitimate site visits from humans that happen over the course of several hours. This is the result of several thousand servers all automatically fetching the same image simultaneously , and without any human involvement, and potentially next to zero human traffic to the site, which is why I compared it to a botnet or DDOS attack.

@Oam_Gui @mediapart @MarieTurcan

#Racisme & #spécisme s'accordent et se renforcent mutuellement. Il serait temps de le mettre davantage en lumière.

Merci @MarieTurcan d'en parler, c'est bien trop rare.

Pour aller + loin, je conseille cette excellente fiche du @PMeduses : https://projet-meduses.com/boite-a-outils/fiches-pratiques/racisme-et-specisme/

#antispécisme #suprémacisme #égalité #LuttesSociales

#rusmeme #мем

@gamingonlinux EA the company bought by the son in law of the orange rapist? No thanks to give him any cents.

I had to edit some text in a Word document for work. This task lackedl a firm deadline so I literally put it off for weeks before I checked in with myself and identified—as I often do—a barely perceptible, difficult to justify sense of dread that kept me from acting.

So reading what @olivia has to say about writing was validating. Here in the Fediverse it seems like all of us are at home composing documents with text editors. But in my decades of professional work—with highly technical people—I've yet to collaborate with someone who shares this disposition.

Anyway, once I guessed that Word itself was the blocker, I took a deep breath and edited the document right in that tool anyway. I think it took two hours. It was on my todo list for weeks!

Here's what Prof. Guest has to say: https://critical.computer/writing/

“Stranded (Modified)” by WiL/Zenith Nadir (2007)
[!STRNDED.ZZT] - “Fishfood”
View World: https://museumofzzt.com/file/view/24stranded/?file=%21STRNDED.ZZT&board=6
Play Online: https://museumofzzt.com/file/play/24stranded/ #bot

Tällaiset avaukset on aina vähän kuumottavia, koska tekoäly jakaa mielipiteitä todella rankasti. Nyt kun olen siirtynyt täysipäiväisesti Linuxilla ajelevaksi, niin törmäsin ongelmaan. DaVinci Resolve toimii Linuxilla, mutta AAC äänikoodekkia se ei ymmärrä, kiitos jonkun lisensointi rajoituksen. Käytän jopa yllättävän paljon puhelimella kuvattua sisältöä videoissani ja siellä tuo äänikoodekki on mobiilivideoissa tiukasti mukana. Lataan videot Google kuvista, jolloin ne tärähtävät zip tiedostona koneelle. Työnkulku on siis selkeä.

Teetätin Claudella tällaisen graafisen kikkareen johon tiputetaan zip tiedosto ja se avaa sen, käy läpi videot ja muuttaa äänet sellaiseen muotoon videolla mitä Resolve ymmärtää ja puskee ne haluamaani kansioon. Piruuttani heitin vielä valmiin koodin Gemini Argonille joka sieltä muutaman tökön hoksasi ja Claude sitten korjaili ja heitti omat testinsä ja lopulliset analyysit. Nyt mulla on siis toimiva työkalu arkiseen käyttöön, joka myötäilee käyttöliittymän visuaalista ilmettä. Ehkä vähän yliampuva tällaiseen pikkuhommaan, mutta tulipa kokeiltua tällainenkin.

Helpompaa olisi tietysti käyttää Windows tai MacOS ympäristössä Resolvea, mutta eihän se olisi yhtään näin hauskaa. 😃

The origin and purpose of the traffic is not the same. That’s why they block one and not the other.

Assuming we spend an average of 4 hours per vuln report, we just yesterday got ourselves **four weeks** of full-time work.

But what OP is talking about is a technical detail that can be fixed.

That’s not at all the same thing. That’s just the inability to handle large amounts of unexpected normal user traffic.

This is essentially bot traffic driven by servers all independently but simultaneously fetching the same image, without even a single human necessarily looking at it.

From server’s perspective the only difference between those is the user-agent. Traffic is the same

@nyanpasu64 It's not just Doms and Subs, it's basically every type I'm exposing to the runtime. (It just happens that at the time of tooting, only two such types existed)

@EUCommission but I don't like travelling...

https://en.wikipedia.org/wiki/Slashdot_effect but people were going in, looking at the link, sometimes overwhelming the server

I remember reading the same thing about reddit, slashdot, fark, and other sites. But I like the FASP idea as a way to relieve this.

You’re right, neither of them are known for providing thousands and thousands of distributed network connections to the same destination resulting in that same destination server running out of resources. They’re clearly not the same thing at all, no, definitely not at all.