Discussion

I'm so psyched about @bonfire.bonfire.cafe.ap.brid.gy's work on making the open social internet good for real communities by putting in the culture work right from the very beginning. I'm a scavenger and a pragmatist *and also* I think the way we do things matters. www.wrecka.ge/sparks-fly-up/

Sparks fly up

"Today we're releasing Bonfire Social 1.0: a federated community‑first social network and the modular toolkit that powers it: a framework for building apps on the open social web beyond microblogging. We're pairing the launch with a crowdfund so communities drive what we build next. "

@Bonfire, Nov, 2025

https://bonfirenetworks.org/posts/bonfire-social-1-0-is-here-back-the-community-funded-roadmap/

#fediverse #Bonfire #crowdfunding

Harry says the entire network — the Fediverse — is an exercise in cooperation. True! #sfscon #fediverse #fediforum

I wrote about tensions and troubles for Bluesky on @techpolicypress.bsky.social and then I wrote about the TPP piece on wrecka.ge and now I am posting about it the post on Bluesky. Look at this cloud. www.wrecka.ge/clouded-skie...

Clouded Skies for Open Network...

🔥 More anti-enshittification features now live in Bonfire

✨ Complete data portability: Export/import now supports circles/lists, bookmarks, likes, and boosts alongside follows, blocks, and posts.

✨ Transparency by design: A dedicated real-time dashboard to monitor migration progress in detail and troubleshoot issues.

Read more about 1.0 RC3: https://bonfirenetworks.org/posts/bonfire-social-1-0rc3/
#enshittification #release

October 2025 community update

We’re delighted to share the latest and greatest from Co-op Cloud 🤘 It seems safe to say that *a lot* has happened! Grab a `$geographic_location_appropriate_temperature` beverage and enjoy 🎉

https://coopcloud.tech/blog/oct-2025-update

🫡

It's indeed quite easy to add settings in extensions:

Just this bit of code https://github.com/bonfire-networks/bonfire_geolocate/commit/fe76adcbfbdd306e966b993d15465d464566b1ca to add it to settings (see screenshot)

Ah yes forgot to include the link: https://github.com/bonfire-networks/bonfire-app/issues/1412

And you're right, that'd be the same as instance blocking.

@rancidrabbit@cuchaz@FediPact

That would be great to know.

Probably this requires blocking at every possible level to be sure (eg. robots.txt, user agent, IP ranges...) And if some bots are using ActivityPub for scraping we could also block their HTTP signature public keys?

We've prototyped a system that builds on Bonfire's circles/boundaries to define and enforce blocks at the instance, user, and post levels. Would love feedback and suggestions to make it stronger!

@rancidrabbit@cuchaz@FediPact

@cheeaun

@markwilliams thanks! what’s the rationale of using crossref vs zenodo for creating and archiving doi ? @crossref @openscience@a.gup.pe

@rmounce @openscience@a.gup.pe
An article in bonfire is the equivalent of federated long form content in Wordpress/ghosts.
As part of our open science network effort ( http://bonfirenetworks.org/posts/open-source-meets-open-science-announcing-the-open-science-network-initiative/ ) we are planning to create DOIs among other features we already provide ( https://indieweb.social/@bonfire/114931186558231122 )
Would love to get more feedback from you as well from
@mfenner and
@rogue_scholar