Gli ultimi otto messaggi ricevuti dalla Federazione
-
Arriva il CARINT: Le auto connesse sono computer e di conseguenza sotto sorveglianza!
📌 Link all'articolo : https://www.redhotcyber.com/post/arriva-il-carint-le-auto-connesse-sono-computer-e-di-conseguenza-sotto-sorveglianza/
#redhotcyber #news #autoModerna #sicurezzainformatica #ecosistemaInterconnesso #sorveglianza #hackingAuto
-
@evan@cosocial.ca okay, I'll see you there!
-
@deadsuperhero @general @julian yeah, I think custom timelines are great. Some good issues in here on the topic:
-
@deadsuperhero imho, building out c2s will allow new projects to bootstrap the front end, and focus on new application domains, or support multiple activity/object types.
-
@deadsuperhero I don’t necessarily think we need the big players. Especially where those projects have stated their intent to stick to micro, or photo -blogging, with limited interop.
-
On the other hand, however... If the ActivityPub API were used in an S2S context, enabling something like NodeBB to send activities on behalf of a Mastodon user, then it wouldn't matter that there is no GET /timeline, because all you need is POST /outbox and the Mastodon API handles their end.
Vice versa, NodeBB would use its own API to render a /world feed.
-
@julian@activitypub.space @general@activitypub.space @evan@cosocial.ca Again, this is sort of why I'm advocating for supporting timelines as a concept in the ActivityPub API. Instead of repeatedly parsing the inbox, we could do exactly what you're saying with some kind of representation of a timeline. Even if it's just plain old algorithmic time-sort.
-
Does the inbox have to map to a timeline, specifically? Mastodon called this out as being difficult to do because you would have to real-time parse the inbox every time you wanted to load the timeline.
Of course one could always reduce the inbox into a single timeline and serve that instead, but then we're braching out with our own proprietary APIs again.
Is that ok?
