Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

User identity and Activitypub

General Discussion
9 4 36

Gli ultimi otto messaggi ricevuti dalla Federazione
  • evan Yes, the domain name can be an excellent solution. However I am looking for a solution where a federated platform, e.g. Mastodon, can recognize an account from another federated platform such as NodeBB or Friendica and vice versa. At the moment if I want to reply to a mastodon user, Mastodon asks me what my mastodon account is. If I give it my NodeBB or Friendica account, Mastodon rejects it. I think that the ActivityPub protocol should solve this problem.

    read more

  • phi maybe this is a social layer problem rather than a technical problem.

    Your issue means a lot in a world where we have amateur hobbyists setting up social network servers and allowing the general public to join. Those hobbyists get overwhelmed or bored after a while, or they do a bad job and your server gets defederated.

    In this case, it makes a lot of sense to move from one server to another. But this is not the only way we could organize the Fediverse.

    Email isn't like that. You (probably?) don't use an email address from a server you found on a list on joinemail.org. You probably, instead, have an email address from your employer or university, and maybe a personal one from a well-known and reliable cloud service. If you're very clever, you may use your own domain for email, and share it with your household or family.

    In those cases, you rarely change email addresses. We have some ad hoc ways to move from one to the other, but they aren't built into the SMTP or IMAP specs. And yet we have a lot of email going around, even after 50 years.

    I think we should be putting our efforts into getting Fediverse services from organizations we have a lot of affinity with, like employers or universities or the city you live in or the post office.

    Another option is using the extremely portable identity system we already have -- domain names. It should be a lot easier to bring your own domain name to a Fediverse server, and to move your data between servers by backing up and restoring and then repointing your domain name to the new server, like you do for blogs. This is really hard right now.

    I think LOLA is doing a good job with online moves, but we should also be encouraging more server developers to support BYOD, and we should encourage Fediverse users to get a domain.

    read more

  • @johnefrancis I have a collection of my favourite smarty-pants comments that would fit that description, so yes.

    read more

  • @konstantin I don’t know of any current flagship instance but I have a test account on plasmatrsp.com

    read more

  • @fedicat is there a "reference" or already updated sharkey instance one can use to test against? I'd like to make sure we support this in TootSDK

    read more

  • @evan can AP handle empty directories?

    read more

  • ActivityPub doesn't represent state; it represents changes in state.

    Git does the same thing (for the most part; there are exceptions). It represents a repository as a series of deltas from state to state.

    read more

  • seems like a lot of mastodon api stuff got fixed over the past year, I'm enabling them in now

    read more
Post suggeriti
  • 0 Votes
    5 Posts
    4 Views
    @blainsmith @rimu @jwildeboer there is a forthcoming FEP from the AP T&S taskforce that introduces the idea of a Moderation Actor for Actors, so like "Moderated By", which would be a Group or Service actor probably, but it would not be required to disclose it's members.
  • 0 Votes
    1 Posts
    2 Views
    Checking out Bonfire's latest release. This Federation Status dashboard is pretty cool. And get this - it's not just visible to admins - end users can see the same, just filtered to their OWN processes.That's really helpful if you're trying to debug an issue with another platform development team.#ActivityPub #Bonfire
  • 0 Votes
    1 Posts
    5 Views
    Just thought you Fedi folk would like to see what they're saying at the other place, now that Bsky's CEO had a public crash out.#Mastodon #FediVerse #BlueSky
  • 0 Votes
    1 Posts
    5 Views
    Apologies in advance if I misrepresented anybody or missed any crucial bits of information. Jesse Karmani (jesseplusplus@mastodon.social), Ted Thibodeau Jr. (tallted@mastodon.social, and Julian Lam (julian@activitypub.space) in attendance Julian provided an update on adoption of FEP 7888 Both Piefed and Lemmy have adopted 7888, and will begin publishing resolvable context collections in their next release Jesse opened a PR to Mastodon, which received preliminary approval from Gargron@mastodon.social (ed. it was later merged, rolled back, updated, a new PR opened, which was then merged) This PR is the first of two planned pull requests. The first generates the outgoing context (the same as what Lemmy/Piefed have done recently) The seconds handles incoming contexts and backfills Jesse was asked whether it would conflict with existing reply-tree crawling methods, but the two are complementary. She expects additional discussion before the PR is opened. Julian noted that it would be helpful if statistics/analytics were gathered by the Mastodon team to see how conversation contexts and backfill works at scale; admits that existing implementations and testing has been small scale and may not reflect real-world usage. Julian noted that Lemmy's implementation (nutomic@lemmy.ml) does not paginate their resolvable context implementation. All objects are listed in one OrderedCollection Jesse noted that she followed Mastodon's pagination convention for collections. Context inheritance Julian asked for opinions on whether contexts were inherited in existing implementations. Notes that NodeBB inherits parent context, but checks further up the known parent chain for further contexts Julian admits that not everybody can and should do this, is also not sure anymore whether NodeBB actually does this. Julian notes the ideal implementation would be every object referencing their immediate parent, which would lead to the entire collection referring to the same context collection. Jesse: Decodon inherits immediate parent context only Ted: notes that this is a reinvention of inReplyTo Julian and Jesse note that there are marked differences between crawling the reply chain. A short discussion about how netnews and usenet handled reply chains was had. Julian notes that Lemmy will not inherit context. Every object will point back to its own server's context collection. This was a conscious decision by Nutomic as each instance is meant to consider its own representation of remote content as the canonical representation ActivityPub.Space Julian made a short shout-out to a new site called ActivityPub.Space, meant to be a hub for AP development discussions ("A federated space for ActivityPub discussions so that they don’t just get lost in ephemeral replies") A short double-back to NNTP and how they approach "eventual consistency" Ted: “Cloud of NNTP servers are all hosts of articles and replies.” Strictly speaking it’s not a reply tree as replies can be inReplyTo multiple parents