D
your fedi year in review
you were one profane motherfucker this year, reaching for "fuck" 168 times, "bullshit" 124 times, "heck" 122 times, and "piss" an amazing 1,951 times.
have a great time tooting in the upcoming year and thank for reviewing your year with us, the fediverse.
firefox plugin that simply replaces the word "profit" with the phrase "unrestrained extraction and hoarding by the ultrawealthy" in every page it renders.
@trwnh I have not actually tried the *keys because I felt absolutely mummified as soon as I glanced. that and they all seem to be constantly on the brink of ceasing to exist.
can you imagine fedi with presence indicators? hahahaha
activitypub over xmpp with omemo
fedi server that literally just uses a mail server backend and message handling pipelines and static pages dropped into public_html
your fedi year in review
your most boosted toot:
can y'all boost this i am testing something thank
have a great time tooting in the upcoming year and thank for reviewing your year with us, the fediverse.
@alice I agree, batching it in one bulk transaction would be the way to go for sure. the rest is just implementation details haha
@alice I was thinking of the scale of notifying all servers with thread participants so they could update their references to the canonical locations of the newly moved posts, assuming their software cared enough to do so
@alice so well over twice as noisy on the network as deleting an account and all its posts with federated deletes, as it'd entail updating every participant server mentioned in every post or reply in the archive, yeah?
if a fediverse server allowed its users to upload a post archive
and created new backdated posts for each, but did not send them out via federation (although creating them in a way that if referenced they could be interacted with via federation where appropriate)
and possibly marked them as imported/archive content
what potential problems would arise?
@julian long live blobmoji and welcome to the emojoverse! 
@trwnh totally legit approach in my book! I'm most hopeful that if there's enough external pressure applied to the more reticent parties around more reasonable approaches to interop that eventually they'll cave rather than continue to deal with the barrage, but only time will tell ha
@trwnh it's not a decision I've made yet but I tend to think I'd lean towards acting on the Activities (I didn't go into it in the blog post, but I really think I want the client to actually implement AP C2S) and then catching them before delivery to nodes that are text mungers and make sure to send them the munged form that they need to make it easier for users not to think about? that's the balance beam I think I'd prefer to straddle, anyways, lol
@trwnh absolutely suspect there will/would end up being a number of "and now we need to handle this weirdness that these other folks insist on" scenarios, and some that I'd probably choose to push on and not support in more than the most cursory ways. I have a feeling that said looming pachyderm is going to have to start innovating in the space again or get left behind as folk build things that are closer to what people actually want. 
@trwnh agreed! I figure if enough folk start walking these paths we might see more flourishing in the space. Thank!
good morning fediverse. 
I went and did it. I blogged.
"What Would MyActivityRouterKit and MyActivityClientKit Be?"