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

This is how the new Loops app Notifications screen looks like.

General Discussion
8 3 0

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 1 Votes
    3 Posts
    1 Views
    I'm looking into federating out deletion of contexts because in NodeBB the concept of a topic is a discrete entity, not tied to the posts contained within. Deleting the top-level post would not alter the topic in any way, except perhaps that the next oldest reply is suddenly promoted to top-level, which is odd. Conversely, in ActivityPub, there either is no concept of a context (threaded objects only), or merely the suggestion of one as a view (current implementations of resolvable contexts). I'm hoping to move this more towards contexts as discrete entities with their own activities.
  • 0 Votes
    7 Posts
    6 Views
    @box464 if approved on Bonfire's side, Mastodon should recognize itโ€ฆ probably takes time? ๐Ÿ™ˆThere's no approve/deny UI/flow/API on Mastodon's side. I've asked & got this response "we included support for it in case someday another software wants it" and "(but we think it's not a good idea, as it means your quote can be displayed as pending for a long time, which is not ideal in a timeline-based network)" โ€” which I think make sense. By the time it's approved, it's probably too old to be read
  • 0 Votes
    1 Posts
    4 Views
    Stando al Segretario al Tesoro Bessent, USA e Cina hanno raggiunto un accordo quadro per mantenere #TikTok operativo negli Stati Uniti. Trump dovrebbe finalizzare l'intesa con il leader cinese Xi Jinping venerdรฌ, durante una colloquio telefonico.https://edition.cnn.com/2025/09/15/tech/trump-tiktok-china-deal
  • 0 Votes
    9 Posts
    47 Views
    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.