naturzukunft@mastodon.social Let's try for a second take of this blurry photo at FediCon 2025

jdt@enigmatick.social could it be a mistake in the reply?

For example, if the reply had all of the mentions removed I would think Mastodon would send out an object with empty to and cc.

Theoretically, it shouldn't matter.

In the ideal case every connected server should host a full and complete copy of the data from the originating server (as xkdrxodrixkr@feddit.org says, that's B)

Reality is a bit different, but not enough to warrant always picking B. Just share whichever you'd like, but B is the most right.

silverpill@mitra.social said in Against fragmentation: unifying dev discussions with forum federation:
> I wonder what they meant by this. There are lots of projects that support long form content.

I think what johnonolan@mastodon.xyz was trying to say was that given the relative size of the ActivityPub developer community, it's a little (or a lot) surprising that our developer discussions are as fractured as they are.

That's probably why I push so hard for discussions about fedi to take place on fedi.

I do get the appeal of smaller back channels, but they shouldn't be where the main business is conducted if possible...

j12t@j12t.social awesome, see you there!

Hey casey@sharetron.com! Congrats? Bittersweet perhaps?

Hopefully you'll make it out to FediCon in Canada, it'd be nice to reconnect without having to go all the way to Europe haha

douginamug@mastodon.xyz this entire series right here

Understanding ActivityPub - Part 1: Protocol Fundamentals

Understanding ActivityPub - Part 1: Protocol Fundamentals

(seb.jambor.dev)

Can't imagine any situation where a high-stakes championship would be better off with subjectivity.

Aside — it ain't "AI" making line calls, it's just the same bog standard electronic line calling in place at other tournaments. Thoroughly boring and reliable technology.

efi@chitter.xyz ben@mastodon.lubar.me thanks, we're aware! We'll add in controls to limit chat access for new users.

Threadiverse

silverpill@mitra.social I wasn't aware that there were sections pertaining to context. I'll have to review more closely.

benpate@mastodon.social Emissary interested? Har Har Har

steve@social.technoetic.com the idea here is it would be a step towards resolving the account fragmentation issue.

steve@social.technoetic.com I'm interested in potentially using the C2S API as a way to have someone log in via another instance, and have it act on behalf of the second instance.

e.g. User on Mastodon instance A logs into Bookwyrm instance B and starts reading a book. Bookwyrm B uses C2S API to instruct Mastodon A to post "I am now reading book xyz"

So yes, a verified subset of C2S would be the path here.

dfyx@social.helios42.de because followers and outbox collections can be faked.

benpate@mastodon.social agreed! It's a great document that is paving the way toward better long form text support on fedi. That it has buy-in from Mastodon is the missing piece that other attempts lack.

I think if you run into issues with it we can usually update it as needed.

You should come! Canada's a beautiful country and BC in particular is quite nice.

The conference is shaping up nicely! I'm hoping to attend and present.

It'll be very interesting to see Canadian AP devs and users!