Salta al contenuto

Piero Bosio Social Web Site Personale Logo Fediverso

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

I'm seeing more and more platform-level activity over on ATproto: Slices is a Heroku-style platform for building apps, for example, and I'm seeing more and more cogs being developed

General Discussion
2 2 1

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votazioni
    2 Post
    0 Visualizzazioni
    fedigarden@social.growyourown.services I would like to submit ActivityPub.space to this list but I am unable to comply with Threads defederation. We are topic-focused around AP development and would not want to exclude those developers outright. There are occasionally discussions about Threads/AP interop that could be useful and on-topic. It'd be like closing off discussion about ATProto/AP discussion by blocking BridgyFed. I could consider something like an opt-in for that domain?
  • User identity and Activitypub

    General Discussion activitypub fediverse identity
    7
    0 Votazioni
    7 Post
    22 Visualizzazioni
    silverpill@mitra.social I think it's important to define a feature within ActivityPub that "allows users to freely move from one server to another without losing their identities and content." Obviously, the servers don't have to be part of the same platform.
  • 0 Votazioni
    4 Post
    14 Visualizzazioni
    @Nead @markwynerIf there's a revenue stream, there will be obstacles to the stream. Like self-hosting, other instances, other softwares using the same twisted Mastodon protocol. In the best case scenario those will be competitors to crush, sooner or later.In the worst case they could become the ideological enemy, while they actually ARE the Fediverse. The REAL one.
  • FEP 11dd: Context Ownership and Inheritance

    Spostato Fediverso fep activitypub
    9
    0 Votazioni
    9 Post
    38 Visualizzazioni
    trwnh@mastodon.social Yes you're right, some messiness is bound to happen. I'm not trying to force all implementations into a specific inheritance pattern, that's why it's a "should", not a "must". Even then one of my concerns is that while in an ideal scenario, everybody inheriting their parent context leads to an entire collection all referencing the same context... in reality a lot of messiness will occur, objects will reference other contexts all over the place, etc. At the end of the day it's best effort, and if we are able to handle all that and still get to a point where backfill is achievable, then that's a win in my books. > it depends on how much you embrace the idea of each publisher being allowed to make their own claims (and how much you allow "clean up" after the fact) Part of me would like this to not happen, but it is unavoidable.