Salta al contenuto

Piero Bosio Social Web Site Personale

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

#Smithereen 0.11 is out

Senza categoria
14 3 0

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votazioni
    5 Post
    2 Visualizzazioni
    @julian @grishkaHere's en example:{ "type": "Create", "actor": "https://social.example/alice" "object": { "type": "Note", "attributedTo": "https://social.example/alice", "attachment": { "type": "Note", "attributedTo": "https://social.example/bob" } } } It contains an embedded Note that is attributed to another actor. There are many possible ways to embed an object, and malicious embedding could be difficult to detect for the origin server.
  • 0 Votazioni
    2 Post
    1 Visualizzazioni
    @activitypub.blog this is the best pluginokay maybe after askimet but OTHER THAN THAT xD
  • 0 Votazioni
    1 Post
    1 Visualizzazioni
    Nessuno ha risposto
  • FEP 11dd: Context Ownership and Inheritance

    Spostato Fediverso fep activitypub
    9
    0 Votazioni
    9 Post
    8 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.