undefined
oh, I think we would be perfect for that actually! we recently (like, 2 days ago) pushed the relevant code and deployed it to app.wafrn.net
we implemented GoToSocial's spec de-facto, in addition to Bluesky's (due to us federating over both AP and AT), but we think there's things to be improved here (like gating a whole thread instead of per-post) that have found some interest from GTS' team too, from what I've heard from gabbo at least.
ps: also funny you mention bites, we have that literally
honestly, that is fair enough. I guess it makes sense that visibility for projects is better where there is the capacity to visit events and such.
and sorry if it sounded a bit condescending, I guess I am just a bit sad that things seem to be 'going so well' over in AT land.
the primary backend developer here is @gabboman, I mostly dabble in frontend stuff; To my knowledge we already handle incoming Article activities but actually support a larger set of HTML tags than what is described in the relevant FEP published by the SWF. like this here red text
most importantly, thank you for reaching out.
Yeah I know that long-form content was one of the SWF's first projects (or at least, that's what I remember), but standard.site is just one example of many, and a more prominent one as making long-form content on protocols seems to be especially popular.
I guess I am just frustrated that often it feels like the coordination only exists within a smaller bubble of "larger" projects, mostly Mastodon and perhaps things like GoToSocial. Looking at ourselves, projects like Sharkey or Akkoma, to my knowledge none of these were contacted about anything over the past year or so, despite having similar priorities -- we've wanted to ship an "Article" post type for a while now for longer form posts, but for now we've only ended up using it for /about and other such internal pages, in part due to time, and in part due to the semantics between how this is displayed differing so much between software.
We already have code to handle specific deficiencies between say, "old quotes" and "new quotes" a-la what Mastodon does now, versus what everyone else did before, like inserting a mention to posts we quote to work around the fact that Mastodon doesn't receive them otherwise (which is, to be clear, a workaround that stuck from before Mastodon got quotes)
How far did that go? I know that GoToSocial was contacted, but I have not heard anything from Sharkey, upstream Misskey, nor Akkoma or Pleroma, and we of course heard of what's happening but AFAIK haven't been contacted either.
Though, mind you, I was moreso talking about how I believe the SWF should be the coordinator here, as they are the foundation that is supposed to consolidate and coordinate work in the space, after all. Not so much Mastodon gGmbH themselves. Sorry if that wasn't quite clear in the post
ironically this has lead to other software out there (won't say who :3) being interested in ATProto.
good job to me for writing "size" instead of "site" for the TLD
sorry atproto enjoyers you're not getting the edit 
edit: pls check the replies and such, I've been a bit disingenuous tbh
I've been saying this
the SWF is just kinda there but to my knowledge doesn't really do much outside of like wordpress and mastodon. and working with meta i guess.
I for one have never heard of anyone from the SWF or Mastodon reaching out to other implementations to coordinate on, say, quotes with authorization.
meanwhile on the ATProto end, there is groups like https://standard.site just to standardize long-form content.
Regular reminder for people in Germany:
FIGHT CHAT CONTROL.
Germany is NO LONGER AGAINST IT and if they sway to being in favour then we are, effectively, FUCKED.