@csolisr@hub.azkware.net ah yeah it probably would have to built for (ideally on) your machine in this case

@csolisr@hub.azkware.net Which dependency did you see on AVX? our markdown renderer for example uses it when available but has a fallback which should be enabled automatically when not available (otherwise you can force it with `MDEX_USE_LEGACY_ARTIFACTS=true`. In any case please provide more info or open a bug report.

just discovered another super interesting and needed work done by @s0hw@hci.social and @andresmh@hci.social platform.coop/blog/toward-wo...

"Aiming to shift control of delivery work away from a single entity, OpenCourier is a protocol that defines data formatting and communication across a decentralized network of delivery platforms, couriers, and service requesters. Broadly, we aim to enable an ecosystem (Fig. 1) that centers community-owned delivery platforms, where workers — who we refer to as couriers, given their work providing delivery services — cooperatively manage the platform they are a part of. "

📄 here the full paper dl.acm.org/doi/pdf/10.1145/3...

cc @mayel @lynnfoster@social.coop @bhaugen@social.coop #bonfire #valueflows

@olm_e@tchafia.be students in the class led by @s0hw@hci.social and @andresmh@hci.social at hci.princeton.edu have worked on something like this which was previewed at the last #FediForum and will launch in the summer...

@thisismissem@hachyderm.io

I tried to address your first point here: github.com/swicg/activitypub...

Not sure I understand why you say "server will end up with that information in cleartext at some point" though?

@evan@cosocial.ca

@liaizon@social.wake.st those are just placeholders, our goal is maximum interoperability while also extending what is possible, and we're participating in the W3C groups task force to define how things should work, please weigh in there if you have any suggestions: github.com/swicg/groups/issues

You can read more about our work on groups in this previous blog post: bonfirenetworks.org/posts/wh...

And if you're an #ActivityPub developer who's interested, please join the W3C task force discussions: github.com/swicg/groups/issues

@reflex@retrogaming.social

Thanks for asking, it's something we're taking seriously. We're working on an AI policy for the project but want to do it thoughtfully and with care rather than rush something out, please bear with us.

@fediforum@mastodon.social

Our @fediforum@mastodon.social demo is up! 🔥

We showed off Bonfire Mosaic and our ongoing work on federated groups and new publisher tools we’ve been co-designing with jacobin.de, including federated discussion threads that can be embedded on their existing website.

Built on our modular framework for community-governed digital spaces.

Watch 👉 spectra.video/w/hV9wzGzsXvNj...

@julian@fietkau.social Thank you very much for the review and answering the Hashtag question 🙏

And yeah codeberg seems to have some troubles lately..

If you are up for another review, we have a rough implementation for the instance actor with a basic inbox that handles follow and unfollow: codeberg.org/Klasse-Methode/...

@lauti 🍻

We are a little bit late to the party, but on the 1. May we celebrated #lauti's first anniversary 🥳.
This year was crazy, we got in touch with so many amazing people a long the way. We did our first talk at the #39c3 self organized session of @techfrombelow@chaos.social
We visited #fosdem with our friends from @Bonfire where they announced our collaboration working on #events in the #fediverse.
We are just getting started, SSO is around the corner and we are working on #activitypub at the moment.
For more updates take a look at our last blog post
lauti.org/blog/lauti-updates...

a great article by @thisismissem@hachyderm.io on going beyond binary approach to federation...
" > However, we've been presented with a false dichotomy here: we don't need to operate in a world where we either allow everything until blocked, or block everything until we allow it. There are other ways that we can look at federation management. Some of these include Consent Based Federation, where a moderator or administrator has to review and approve a server before accepting federation (or denying it), or models that resemble a firewall on a computer or server: you'd don't just have to accept or deny federation, but you can also apply filters to the federation between your server and another."
writings.thisismissem.social...

@linos@graz.social We got a first version implemented at codeberg.org/Klasse-Methode/...

Reviews by anyone with #activitypub knowledge is highly appreciated 🙏

The paper Governing Together: Toward Infrastructure for Community-Run Social Media by @s0hw@hci.social @andresmh@hci.social and colleagues at hci.princeton.edu (which we will discuss at #FediForum today) takes on a tension at the heart of decentralised social media. The fediverse promises to empower communities to govern themselves and set norms in their own context, on their own terms. But communities can't actually govern in isolation. Their members talk across boundaries, bad actors hop between servers, and the rules one community sets can directly undermine another's. The authors call these "governance frictions."

Their argument is that we've spent a lot of design effort looking inside communities, like improving moderation tools and onboarding, but almost none on what they call inter-community governance: the infrastructure that lets communities coordinate, share information, and manage their relationships with each other.

To explore what that infrastructure could look like, they ran four design workshops with 24 Fediverse admins, moderators, and developers. Participants imagined ideal tools, and the authors synthesized those ideas into six concrete challenges, like making governance decisions visible, sharing nuanced information about issues, controlling who you share what with, and minimizing barriers to adoption.

The synthesis lands on three design principles:

Modularity: communities need a shared vocabulary, like a "Governance Nutrition Facts" label, so they can read each other parsimoniously.

Polycentricity: communities should sit in overlapping "trust bubbles," not one global network, so they can have nuanced, evolving relationships.

And forkability: communities should be able to copy and adapt each other's governance structure and rules, preserving autonomy while reducing labor.

The big takeaway: decentralisation alone isn't enough. If we want community-run social media to actually work, we need to design the connective tissue between communities, and the design principles here may apply well beyond the Fediverse, to any platform where multiple communities coexist.

bonfire.cafe/post/01KQETGFGP...

Today at #FediForum we'll have a discussion with some of the co-authors of the academic paper Governing Together: Toward Infrastructure for Community-Run Social Media. There's no better time to read this paper!

bonfire.cafe/post/01KQDCWGK0...

If you're attending #FediForum let's have a discussion tomorrow around this open access paper: Governing Together: Toward Infrastructure for Community-Run Social Media which argues that decentralized platforms like the Fediverse focus on governing within communities, but ignore the frictions between them. From workshops with 24 Fediverse community organisers, they identify six design challenges (visibility of governance decisions, collating issue information, controlling what's shared and with whom, enabling new inter-community relationships, customising governance, and minimizing adoption barriers) and propose three principles for "inter-community governance": modularity (shared vocabulary, like governance nutrition labels) and forkability (copy and adapt others' governance structure or rules), and polycentricity (overlapping trust bubbles instead of one global network, i.e. archipelagos).

Decentralisation and autonomy alone aren't enough, communities need connective tissues to interconnect them beyond just technical federation (a mycelium network if you like 😊)

If you're interested and are able to read or peruse it ahead of time that will help us have a more grounded and potentially productive discussion based on it...

@mrkslrnz@digitalcourage.social @henningtillmann@d-64.social

Du bist nicht alleine mit deinen Wünschen, wir hören sowas immer wieder in Gesprächen mit Communities. In die Richtung was du suchst könnte @Bonfire sein. Bonfire Social ist bisher nur Microblogging, aber das Community Flavor bekommt gerade ein Gruppen-Feature und die Roadmap sieht noch viel mehr vor. Außerdem arbeiten wir gerade an einer Integration von LAUTI in Bonfire, damit sind dann auch Veranstaltungen abgedeckt.

Wenn du interesse hast das Gruppen Feature auszuprobieren, sag Bescheid.

Hey @mariusor@metalhead.club,

we are looking into your #Go #Activitypub library to implement federation in #LAUTI

One thing we need to do is implement the #FEP 8a8e by @linos@graz.social

Do you have time for a quick call to get an overview?

@reflex@retrogaming.social ah blogposts have date at the end of the page, we'll move at the top for clarity, but we're alive and thriving... will share more of our ongoing work at the next @fediforum@mastodon.social if you are interested 😊

@reclaimthetech@mastodon.uno