I'm just gonna throw this out here, but maybe, just maybe, we should be focused on fixing the protocol and plugging the glaring issues in it, instead of throwing stones from within our glass house.

Emelia 👸🏻

Emelia 👸🏻

So much was underspecified and undefined in ActivityPub that we've virtually not ended up with ActivityPub but instead the Mastodon profile of ActivityPub+Webfinger+HTTP Message signatures.

Common side-effects weren't defined, common interactions weren't either. Trust & Safety and Security were all but dropped from the spec, and now 8 years later a new generation of folks is trying to clean up that mess.

Emelia 👸🏻

In fact, something I co-authored that was designed for ActivityPub servers was actually first adopted and validated by AT Protocol and Bluesky.

That allowed us to keep moving forwards because we could show real world adoption.

James Smith 💾

@thisismissem Feels like this is something that the W3C group on this *should* be working on for an ActivityPub 2.0. Is that a thing? I've not been paying a huge amount of attention on that front...

Emelia 👸🏻

@Floppy at best we’re currently working towards ActivityPub 1.1, if we get the working group reconvened. Most of the innovation is happening through specs.

@thisismissem Im trying to make it worse!

#just-in-case #this-is-a-joke

James Smith 💾

@thisismissem well, this reminded me to join up to https://www.w3.org/community/socialcg/ at least.

Emelia 👸🏻

@gabboman I still haven't really followed too closely what you're doing, do you have any FEPs or something describing how you federate?

Emelia 👸🏻

@Floppy please do, if you've experience that’d be worth contributing.

Edit: ooops, didn't realise you were the manyfold guy Of course you have something to contribute!

@thisismissem truth be told, most of the time I just try to make something that "just works" with mastodon, *oma, and key. Also with gts and some lemmy hacks.

The first feature I am trying to push to some people is the ![media-1] thing I am doing for inline images, and I just published the feature a few days ago (and I am still fixing some frontend bugs on that)

Wafrn started as a small project I did because I was angry at tumblr for a bunch of reasons . This happened 3 years ago. I made wafrn just as a tumblr clone. Then I see the twitter thing by elon musk and decided to look into "conecting wafrn with mastodon". After a few months I got a first version working (almost two years ago at this point)

A lot of the features I do myself, like asks or the ![media-666] are done in ways that can be described as a compromise:

Sending a DM with the format should make it an ask (BUGGY AT THE MOMENT, SOMETHING SOMETHING MYSQL TO POSTGRES MIGRATION). It would make more sense to make it another way, but then a mastodon user could not send me an ask. So I do it this way, a compromise.

Same with inline images. Akkoma sends the image as html itself. Thats a problem because mastodon and any good software will sanitize it and remove it completely. With the media tag, a human could say "oh I see, I think this is referencing the first picture". Also, tecnicaly you could attach an image to a post of yours and you could use the format. Your instance wont show it but in wafrn it will be shown (buggy, I have reimplemented it and Ill fix it after work today)

I can do stuff because wafn doesnt have that many users, and a mistake in my software "wont affect too much to too many people". But if mastodon has a typo, oh my god millions will see it

#yeah-i-may-be-moving-fast-and-breaking-stuff-a-bit #I-am-aware-of-that

Emelia 👸🏻

@gabboman ah, yeah, well, I think inline images in post text could definitely be something to raise with the long-form content…”taskforce" (it doesn't really exist yet)

The main thing I'm interesting in is how the “User A said ... User B said ... You said …” threading style on posts.