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

How do you make friends in the #Fediverse?

Fediverso
11 8 2

Gli ultimi otto messaggi ricevuti dalla Federazione
  • @julian

    I haven't seen anyone use Add and Remove activities to notify updates to the `outbox`. I don't think it would work; it's too recursive.

    I've done it for other feeds, like `replies` or `followers`, and it works pretty well.

    @smallcircles

    read more

  • @julian

    I might not understand what we're talking about.

    @smallcircles said that AP doesn't mention "timelines" or "feeds". We use a different term, collections. They are ordered in reverse chronological order, like what most people expect a "feed" to look like.

    read more

  • @evan@cosocial.ca gosh I can't imagine assigning Add and Remove activities for a "popular" collection. It changes so often that it seems a waste of resources to try to track it.

    Dynamic Collection?

    Or as @smallcircles@social.coop said, even just light algorithmic ordering in a timeline makes stuffing it into a collection unwieldy.

    read more

  • @evan @julian @deadsuperhero

    Except when they are called other names instead ;p

    A timeline is a different thing than a collection imho. And an AS collection has some very particular functionality, which if I model a timeline in my app may not supported (e.g. reverse ordering).

    Collection / 'timeline' is one of those words where sometimes they indicate an app domain, and sometimes a core protocol mechanism. Same is true with 'follow' which is sometimes a user action, sometimes indicates low-level publish/subscribe.

    For core capabilities that must be part of the specs, in 'protocol space' it may be better to use terminology that is more common in messaging architectures and all the various architecture patterns that are involved. Perhaps idk we deal with a time-ordered event log or something like that.

    read more

  • read more

  • @julian @deadsuperhero @evan

    Can't help but wonder about terminology use and abstractions they indicate. Nowhere in the specs is there mention of 'timeline' and neither of 'feed' (except as example use in AS).

    I feel we started with powerful specs to be able to model *any* social networking use case. But where the specs had blanks gradually the impls filled these in with leaky abstractions such that fedi is now hammered into a very narrow social media microblogging domain.

    If an app needs "Timeline" and "Feed" concepts, then it should model them. Given the actor-based nature of AP they might be actors, or whatever is best. These concept are about solution development, i.e. what is built on top of the protocol, and not indicative of core protocol capabilities.

    There's so much confusion on "where does the protocol end vs. where does my app design start".

    SDK's should offer "Addressable actors exchanging msgs with object payload", and hide all impl details for the solution developer.

    read more

  • @seiz Thank you. I’ve been working on it for a long time, the skeleton of the app has been there for more than 3 years. I’ve identified some points that were specific to iOS 26 and put them into a condition. I could make it work with less than 40 modified lines.

    read more

  • @stefano the bug is fixed and I can use the app. Unbelievable, what you achieved there in such short time.

    read more
Post suggeriti