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
  1. Home
  2. Categories
  3. Technical Discussion
  4. @evan hey, could this get merged?

@evan hey, could this get merged?

Technical Discussion
5 2 4
Log in to reply

Feed RSS
@evan hey, could this get merged?

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • douwe@waag.socialundefined

    Trying to better understand ATproto and Activitypub similarities and differences.

    Moved Technical Discussion fediverse eurosky bluesky activitypub atproto mastodon
    5
    0 Votes
    5 Posts
    22 Views
    evan@activitypub.spaceundefined
    @douwe@waag.social The protocol itself hasn't changed radically in the last 18 months. If you want to understand ActivityPub and ATProto's similarities and differences, you can't find a better analysis than Christine's. She is one of my co-authors on ActivityPub, and she really dug deep into both protocols.
  • mariusor@metalhead.clubundefined

    @silverpill previous/next are the properties of a Collection object.

    Technical Discussion
    1
    0 Votes
    1 Posts
    7 Views
    mariusor@metalhead.clubundefined
    @silverpill previous/next are the properties of a Collection object. And GoActivityPub uses "after" and "before" query parameters for configuring a keyset pagination cursor. Next is a collection IRI where ?after=IRI where IRI is the last object in the current collection.Previous is a collection IRI where ?before=IRI where IRI is the first object in the current collection.
  • soapdog@toot.cafeundefined

    I wish #ActivityPub was a "pull" protocol instead of a "push" protocol.

    Moved Technical Discussion activitypub
    18
    1 Votes
    18 Posts
    63 Views
    julian@activitypub.spaceundefined
    @soapdog@toot.cafe hmm... just thinking aloud here. You posit in another post that the network effects inflate exponentially: > Push models are resource hogs that approach exponential growth in a large network like the fediverse That's not true. If you post a message then it sends a copy to each follower. That's linear growth. If you collapse recipients via shared inboxes you can reduce that further. If you're referring to the torrent of requests that happen if your post is shared (the "thundering herd" problem) then that's actually a PULL happening from those requesting instances! Secondly, in a pull model of AP, you would need to continually poll servers of all your followers so as to approach a real-time effect. You'd be polling servers over and over again, and many of them would have nothing new, with so much wasted traffic. If your expectations include semi real-time updates, the push model is much more performant, in my humble opinion.
  • travisfw@fosstodon.orgundefined

    #FediDev is there a generic Android intent for sharing to the Fediverse?

    Technical Discussion fedidev
    6
    0 Votes
    6 Posts
    25 Views
    thisismissem@activitypub.spaceundefined
    There is the Web Share API, and the future Web Share Targets API, but I think we could also align Web Share with FedCM and be able to say "I want to share to this type of application"