I mean, just how many instances are gonna ping the URL? Several hundred, low thousands at worst?

Unless it happens to be some very large media content or a dynamic page with no caching, I’d think the automated federation hits shouldn’t be too bad.

The influx of users that might come after a viral post though, that’s rough…

Thanks for bringing this up. I think in general we need to work on optimisation of Activitypub and Threadiverse implementations of it.

Pick a classic car you would happily convert to electric.

1972 XA Falcon GT coupe.

A “Community Shrine” invites visitors to leave a photo of a loved one. Below it sits a chair with a sign: “Reserved. In memory of the millions of lives lost to genocide & violence by ICE & inhumane immigration policies.”

No one is allowed to sit there. https://www.texasobserver.org/houston-living-archive-of-migration/

#ICE #art #Houston #GulfCoast #photography

@mcc 😔

The same way you know the rest of the data hasn’t been tampered with - you don’t. And when you find untrustworthy instances, you defederate from them.

There are two proposed solutions I have seen. I do not claim that this is exhaustive, just only limited to the proposals that I have stumbled across.

FASP - Fediverse Auxiliary Service Provider

The idea that mastodon has is to have a third-party service that does something like generate a link preview once and then share that to fediverse instances that need it. They have a whole spec they wrote up about these kinds of services that can be run to help out fediverse instances with different things like this, search, or discoverability. They call these FASPs - the repo with the spec is here.

I don’t yet know of any FASP that is live and running, so it is kind of a paper spec at the moment. I don’t do too much on the microblogging side of the fediverse though, so I very well could be wrong.

Federate link metadata and the post at the same time

This comes from an issue on PieFed’s repo. It is basically just an idea at this point, but it is a pretty basic one; have the originating instance fetch the link preview information and simply federate it out alongside the post itself.

RE: https://mastodon.social/@gaza_verified_campaigns/117471016493155429

🚨Urgent help, please, my friends.🚨
The landlord has granted me an extension. Thanks to you, I have managed to raise $150. Thank you to everyone who contributed.
Please, do not leave me on my own.
I need another $150 so that I can pay the full amount.🙏
https://chuffed.org/project/161617
#Fediverse #FediForGaza
@HeatherMJ
@kathimmel
@simon_brooke
@marion_v
@afewbugs
@aral
@fabio

@fesshole Why the hell would anyone want photos of anything on their socks?!

Papyrix tracks a file listing the filepath, title, & author of all the ebooks you've recently read using it. This is managed using a singleton class.

It has inlined methods for calculating how many entries can be displayed onscreen, adding entries to an array & removing them, truncating that array, (de)serializing the array to bytes, & (de)serializing the constituent strings.

Wrappers around those (de)serialization methods carefully opens a hidden file stroring those bytes on the SD card.

1/2

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.

There's also a wrapper around that array-trimming method, & a helper for removing entries without a corresponding file present.

The primary add/remove methods loads the data if needed, prunes missing entries (for add), alters the array, & saves it. All using the previously described methods.

1.5/1.5 Fin for today! Tomorrow: Progress Manager!

Up or down.
#Graz, #Steiermark #Austria
#Shaft #slide #lift

#GazaVerified campaigns that raised less than $200.0 in the past 7 days:

240. @umyahya2026 ($100)
241. @rahafjomah05 ($114)
242. @mohshbair ($114)
243. @mohmad_ah ($121)
244. @mahmoudhamed ($122)
245. @mohammedhamada ($130)
246. @eessll_123 ($142)
247. @eslamradwan1_D_5@mastodon.social ($142)
248. @maram4 ($145)
249. @ruaa ($147)
250. @Magdy___K12 ($153)
251. @Khaledalwan ($167)

(20/21)