Mastodon Feed
Reblogged by jeffsonstein ("Jeff Sonstein"):
tchambers@indieweb.social ("Tim Chambers") wrote:
@mastodonmigration Your advice of wait and see feels more wise every day.
The public WC3 working group mailing lists on ActivityPub does give some windows into the state of work, however...
From the Meta exec there:
cc: @atomicpoet
Attachments:
- > > The Threads team is hard at work on a bunch of different features > requested by the community, so it’s difficult to estimate when support for > ActivityPub will ship. That said, a fair bit of progress has been made on > this front, so I can share with you all our current thinking about some of > these things. Again, it’s possible things could change between now and when > it ships, but this is at least a snapshot of our current plan: > > > — Identifier format: @user@threads.net > — Webfinger: Yes. This would be the first step when someone asks to > follow a fully—qualified identifier from another instance > — HTTP Signatures: Current plan is to implement HTTP Signatures and > not LD signatures. This is what mastodon uses when secure mode is turned on. > — https://datatracker.ietf.org/doc/html/draft—cavage-http-signatures > — https://docs.joinmastodon.org/spec/security/#http > — Which of the activity types: Most of the core formats, still > scoping out the feasibility of all of them. > - Mastodon doesn’t support quote posts (yet, it’s coming), so we'd > like to discuss how to model those when we send them outbound. > — Rich text or not?: No current plans for rich text > — Hyperlinks?: Yes > — HTML Markup?: No plans for this right now > (remote)
