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

something cool to add to #activitypub woulöd be a global shoutbox

General Discussion
2 2 1

Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    3 Views
    Experimental support for multiple users landed with Ktistec release v2.4.15. "Experimental" means that it works for me, but hasn't seen enough testing for me to call it "ready for production". With that said, it's unlikely you'll lose your data.There are lots of intentional design decisions that fit my vision for Ktistec but may surprise you. Here they are:Every user is an administrator. That doesn't mean users have access to each other's posts and data, but it does mean all users have access to the shared parts of the site—they can change the site description, for example—and they can add new users. So only add people you trust.If you want to add another user, create an account for them and give them their username and password.  There is no self-registration. There are no invitations.Beyond adding a user, there is no support for user management. You can't even boot a user from your site. Users can delete themselves, however.There is no support for content moderation. Only add people you trust.TL;DR Multi-user support in Ktistec is suitable for small teams, families (biological or chosen), and your personal avatars. There are better tools for online communities.Here's the full set of changes:AddedAdd support for multiple user accounts.FixedHide attachments behind the summary. (fixes #125)Mark actors as up after refreshing their profile.#ktistec #fediverse #activitypub #crystallang
  • 0 Votes
    1 Posts
    10 Views
    Week in Fediverse 2025-09-19Servers- Gush! v0.0.22- ActivityPub for WordPress v7.4.0- Mastodon v4.4.4- Mitra v4.10.0- Hollo v0.6.11- Manyfold v0.123.0- Ktistec v2.4.13- Smithereen v0.11- snac v2.83- PieFed v1.2- tootik v0.19.2- kmyblue v20.0- Wanderer v0.18.3Clients- Pachli v2.16.1- Fedilab v3.35.0- IceCubesApp v2.0.4- Aria v1.3.10- NeoDB You v1.0.2- PeerTube Mobile v1.1.0- Blorp v1.9.23- Phanpy changelogTools and Plugins- Poduptime v5.5.1For developers- fediverse-pasture-inputs v0.3.3- Granary v9.0- roboherd v0.1.9Protocol- FEP-8967: Generating link previews for attached linksArticles- How to Build a Simple ActivityPub Reminder Bot in Python- Fediverse Report – #134-----#WeekInFediverse #Fediverse #ActivityPubPrevious edition: https://mitra.social/objects/01993fe3-2dac-3533-6a81-9e653c9d94e0
  • 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.
  • 0 Votes
    3 Posts
    17 Views
    rimu@piefed.social that's surprising, isn't aguppe just a standard 1b12 community? What integration did you have to add?