"The reason that ATProto and ActivityPub developers don't collaborate is that ActivityPub developers are rude."
-
@evan A poll would be irrelevant, it should be asked to the ATproto developers
-
@evan differnt AP platforms don't really collaborate.
I doubt rudness is a factor, you seem nice
lol -
@evan A poll would be irrelevant, it should be asked to the ATproto developers
@liilliil Why's that?
-
@liilliil Why's that?
@evan Because on our end, the result will be predictable
-
@evan Because on our end, the result will be predictable
@liilliil you should definitely run that poll, then.
-
@evan differnt AP platforms don't really collaborate.
I doubt rudness is a factor, you seem nice
lol@ozzy Thank you!
-
undefined Evan Prodromou ha condiviso questa discussione
-
@evan seems like this particular poll might be just slightly biased
-
@bkardell how so?
-
Thanks to everyone who replied. I agree with the vast majority on this.
-
Thanks to everyone who replied. I agree with the vast majority on this.
There are many opportunities for ActivityPub and ATProto developers and operators to collaborate: at standards bodies like IETF and W3C, in conferences, and in advocacy. I think it's a good idea to continue that process.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Good question โ in my opinion, 7888 serves as a gentle introduction into the entire concept of conversational contexts. It's meant to be descriptive in order to capture the variety of existing implementations of context that are found in the wild (e.g. Pleroma context which doesn't resolve, contexts that are not URLs, etc.)
Each subsequent FEP "down the tree" (or up, depending on how you look at it) narrows the scope and upgrades verbiage in order to enable additional functionality.
Specifically pertaining to 11dd:
Ownership is explicitly defined and is now a requirement, 7888 mentioned attributedTo and context ownership as examples only. This upgrade was done to set the stage for subsequent FEPs for forking, merging, moving, etc. Activities should be sent to the context owner. This is identical to 7888, but re-stated as a reminder. A specific recommendation for inheritance is included (adopt the immediate parent's context, more if able), while 7888 allows for one to drop context altogether, inherit, or create your own.This is not to say that 7888 is deficient in any manner. On the contrary, it's working entirely as intended!
In practice, Lemmy has adopted 7888, but at this time will not adopt 11dd. nutomic@lemmy.ml creates a context local to the instance, for each post because each instance is expected to be the canonical representation of the context, even if they are cached representations of remote federated content.
It means it would preclude Lemmy from adopting further upgrades like forking/merging/moving/locking, but it doesn't mean they are wrong in doing so.
-
There are many opportunities for ActivityPub and ATProto developers and operators to collaborate: at standards bodies like IETF and W3C, in conferences, and in advocacy. I think it's a good idea to continue that process.
-
Thanks to everyone who replied. I agree with the vast majority on this.
-
@max@poliverso.org
Non credo che i i post scritti da una istanza raggiungano le altre istanze se non c'รจ un server relay che prende i post provenienti da tutte le istanze e li ridistribuisca a tutte le altre istanze in una timeline globale. Si porrebbe il problema di chi mantiene il server relay. I tuoi post raggiungono le istanze di chi in quelle istanze ti segue. Comunque gli amministratori di istanza possono collegare la propria istanza a specifici relay che prendono e rilanciano i messaggi di altre specifiche istanze. Io nella mia istanza Mastodon, come in foto, ho attivato alcuni ripetitori da altre istanze che mi interessano e vedo i messaggi degli utenti di quelle istanze nella mia timeline federata. Ma i miei messaggi non raggiungono tutti gli utenti di quelle istanze, raggiungono solo quelli che in qualche modo mi seguono.
-
@notizie @FediTips @max Forse per la timeline "locale" valgono anche le risposte (come questa stessa risposta, ad esempio), ma non ne sono tanto sicuro, perchรฉ ogni tanto mi appare il messaggino "Alcune risposte dell'istanza XY potrebbero non essere visibili".
-
@notizie @FediTips @max Alcuni programmi distinguono tra "locale" (post locali + post di altre istanze ripostati da utenti della tua istanza) e "federazione" (post locali + tutti i post delle istanze federate). Per essere visibile in quella "locale" ti devi far ribloggare da qualcuno dell'altra istanza.
-
@piero Infatti anch'io quando ho capito come funzionava il fediverso, la prima cosa che ho pensato รจ "questo รจ l'uovo di colombo"; esattamente come l'app Be My Eyes -volontariato a distanza- non รจ chi sa che tecnologia, sono videochiamate; รจ che una startup danese ha pensato bene di creare un server dove si collegano assistenti e assistiti da tutto il mondo, 24/7 o almeno durante il giorno e sera.
Comunque anche Facebook usa gli rss se no da dove prenderebbe i link che si autopostano?
-
@julian i am still kind of confused what this fep adds over 7888 which already describes ownership and inheritance. i guess upgrading some SHOULDs to MUSTs? which i don't think are actually MUSTs in practice... any missing info can be skipped over.
