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

Bonfire shared inbox usage

Technical Discussion
5 3 20

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    6 Posts
    30 Views
    @naturzukunft2026 @julian @saskia https://swicg.github.io/miscellany/#Hashtag
  • 0 Votes
    5 Posts
    21 Views
    @atarifrosch @activitypub.blog @about.iftas.org There’s no intention to exclude ClassicPress. Our resources are limited, so we don’t actively test with it, but I’m happy to fix issues when possible... or, even better, merge PRs that resolve them.
  • 0 Votes
    1 Posts
    5 Views
    Release v3.2.3 of Ktistec includes two big features:FEP-1b12 Group federationImproved federation with Lemmy and other forum-type servers. Ktistec supports community and thread follow/unfollow, as well as up-vote/like (down-vote/dislike is supported but there is no visual affordance for that yet).FEP-9098 Custom emojisSupport for viewing custom emoji in posts and on actor profiles. Ktistec does not yet support custom emoji creation and management.The full changelog:AddedSupport for viewing custom emoji in posts and on actor profiles.Actor type (Person, Group, etc.) overlay badges on actor panels.Colored fallback avatars for actors without icons.Support for robots.txt.FixedFederation with Lemmy and other servers that support FEP-1b12.Shared inbox support for local actors.Serialization of Undo includes the undone activity.Serialization of Like and Dislike does not.Notify only once for an object's first received activity.ChangedAccumulate metrics by hour for finer granularity.Clean up presentation of public followers/following pages.The next release will include support for Mastodon polls (FEP-9967).#ktistec #crystallang #activitypub #fediverse
  • 0 Votes
    13 Posts
    73 Views
    silverpill@mitra.social I have been reflecting on the use of Remove/Move vs Update and I am thinking that Update isn't explicit enough. If I am removing a topic from a category, I'd be sending an Update with the group actor removed from the audience property. However recipients wouldn't know which audience was removed, merely the new state of that context's audience.