Hey 👋
We managed to get a #postgres setup working for #lauti
codeberg.org/Klasse-Methode/...
Most needed changes are small, but maintaining two database implementations can be a burden, are there more people interested in Postgres support?
Recent Activities
@Bonfire no response on my question about AI usage. Can you help me out here? A partial answer is also honest enough... "yes, we use AI but we are preparing a policy and a full update"?
Right now it's just awkward crickets.
@benjaoming@social.data.coop we've replied several times to the same question both on the fediverse and on our issue tracker: github.com/bonfire-networks/...
@bookstodon
Bonfire http://bonfirenetworks.org/ sounds like it could be great for the book community, though the name itself makes me a little nervous in this context. 🔥
We’re delighted that the Erlang Ecosystem Foundation is following Bonfire’s evolution with such interest.
The EEF supports the #Erlang, #Elixir, and wider #BEAM community, which is the ecosystem behind the technology Bonfire is built with. The foundation plans to deploy Bonfire and explore how it could serve that community. We’re excited to see what they discover and to collaborate with them.
Read the update from the EEF: com.erlef.org/wg/com/2026/08...
LAUTI will also benefit from the new server as hosting our CI runner will then be free and we probably can even add more capacity to it. So we would be thankful if you are able to contribute a small amount. 🤝
@ivan I joined the bonfire matrix room, but don't want to 'spam' it with things related to only one of the flavours.
I think it would make sense to have a more specialized room to discuss things related to openscience.network
What do you think?
@UlrikeHahn @Bonfire @jorgeluis @pierre @unif @fresseng @AvSchroeder
@lavaeolus @Bonfire @AvSchroeder @UlrikeHahn @jorgeluis @unif @pierre
No, not sure of that. My guess is that it would work seamlessly... but better ask @ivan
@fresseng@universites.social @lavaeolus@fedihum.org @UlrikeHahn@fediscience.org @Bonfire @jorgeluis@mastodon.pub.solar @pierre@universites.social @unif@universites.social @AvSchroeder@fedihum.org
we explain it in our FAQ openscience.network/faqs/
The flow is : when a publication is archived and gets a DOI, you can add co-authors to the metadata. If the instance has ORCID member API access, each co-author gets an ORCID notification to claim the work and link it to their ORCID record. They don’t need to already have an account on that Bonfire or Open Science instance, and depending on their ORCID settings, they may also get an email alert from ORCID. would love to get back to that work <3
@Bonfire hey there! A lot of old blog posts keep being posted to this fedi account. Is that on purpose?
@georges@dice.camp hi sorry for the noise, yes it's to enable federated comments underneath them (see our latest blog post), we did back-date the posts but unfortunately it seems Mastodon ignores that
@Bonfire A request of you please? When you link your blog posts here, it's great. I just wish I had a clue what they are about. I don't get the full link, and the card that gets displayed is always the same generic info card about the bonfire site. Give me a clue about what the post is so I can determine if I want to read it.
@pedersen@c.im that was a bug, thanks for notifying us!
@Bonfire
I would have liked to participate, as I am still unclear about what exactly Bonfire provides, and whether it'd be suitable for two potential communities I want to create. Sadly the registration is already closed 😢.
Is there anywhere else I can ask questions and get advice?
As a side note, I was surprised (and disappointed) to see that your chosen partner for conducting the interviews, uses Google Forms, rather than a privacy respecting alternative such as #Framaforms or #LiberaForms. They are a much better fit for a project that targets an audience that wants to get away from #bigtech
@aerion@nerdculture.de Thanks for your interest 😊 that post was from a couple years ago though (our blog is now automatically federating, we backdated old posts but looks like Mastodon ignores that).
@AvSchroeder @lavaeolus @UlrikeHahn @Bonfire
They do not want to, and I understand why : it is to keep it truly federated.
Furthermore, running such an instance has costs. My feeling is that it is the responsibility of the scientific community to host OSN servers.
We manage to do it for emails (SMTP protocol) : why not for OSN (ActivityPub protocol) ?
@fresseng@universites.social correct, and it's also responsibility of the scientific community to engage and codesign with us the exact features, user experience and goverance models that are needed for open science to thrive beyond capitalistic and closed platforms.
The goal of the Open Science Network has always been to give the scientific community a real opportunity to shape and govern not only its own servers, but also the software roadmap, rather than reproducing a top-down model in which yet another company builds features for others to adopt without meaningful participation :)
@AvSchroeder@fedihum.org @UlrikeHahn@fediscience.org @lavaeolus@fedihum.org @pierre@universites.social @unif@universites.social @jorgeluis@mastodon.pub.solar
@thenexusofprivacy @Bonfire When you say groups are currently local-only, does that mean everyone who wants to be a part of multiple groups/communities will have to create multiple accts?
@Sharksonaplane@mastodon.sandwich.net @thenexusofprivacy@gotosocial.thenexus.today Yes for now that's the biggest gap, and it's our biggest priority to sort out. Wiring groups up between Bonfire instances would be easy, but our goal is for groups to work across the whole open social web, where someone on Mastodon or any other fediverse app can join and take part. That's why we're contributing our implementation experience to the W3C groups task force, working towards a common standard. Anyone into fediverse protocols and software is invited to come join the task force: this only works if we design it together, in the open.
Would be interesting to, at some point, see these ideas tangibly connected and allow users to jump between the two 🤔
Definitely! Would be great to have you all involved in these discussions: github.com/swicg/groups/issu...
A lot of overlap of thinking between @blackskyweb.xyz@bsky.brid.gy's Acorn and what @Bonfire@bonfire.cafe is doing with communities 👀
Why Community Matters: Groups ...
@quillmatiq.com@bsky.brid.gy @blackskyweb.xyz@bsky.brid.gy
Yeah we love what Blacksky folks are doing ✊ We mentioned that and some of the differences with the likes of Bluesky in our eyes on this page: bonfirenetworks.org/about/
Also here's a blog post from today with what we've been building with communities over last few months: bonfirenetworks.org/posts/bo...
Today is announcement day 🔥
Bonfire is shifting its centre of gravity: from social features to community tools. Four things ship today, and the whole story is here: bonfirenetworks.org/posts/bo...
1. Bonfire for communities
Groups and topics, community rules, decision-making (from quick polls through structured consensus to weighted score voting, where an objection can count for more than an approval), events, shared organisation profiles, announcements.
A ready-to-use space you can then take apart: add what's missing, fork what almost fits, switch off what you don't need.
2. Our first Mosaic case study
Six months with Jacobin's German edition, building jacobin.social from the ground up: a home for 3,000+ readers, wired into their Ghost publication, in their language and their look and feel. Their readers crowdfunded the project, which included a reboot of the magazine and a new community space. Now every publisher can benefit. What one community funds, every community inherits. Details: bonfirenetworks.org/case-stu...
3. A deep Ghost integration
Keep publishing exactly as you do now, and Bonfire can become the home for everything that happens around the work: your archive imported, new articles followed, members and tiers synced, sign-in through Ghost, federated discussion under every piece. Details: bonfirenetworks.org/ghost/
4. The Telling
One script tag turns any web page into a federated conversation. Readers reply with an account they already have, on Bonfire, Mastodon, anywhere. The thread lives on your server, and you can take it with you. Details: bonfirenetworks.org/telling/
Being straight with you: this is a 1.0 beta. Groups work within a server and don't federate yet. We're designing that in the open with the W3C groups task force, because we'd rather it work across the whole fediverse than ship a dialect only Bonfire speaks.
Want to poke at it? Groups are live on the campground, our open test instance. Make an account and try it out: campground.bonfire.cafe
Finally, we've rebuilt the website to reflect the new direction: bonfirenetworks.org/
Now back to following up with crowdfunding backers to organise install parties, co-design workshops, and other rewards. Thank you for your patience 💛 #fediverse #ActivityPub
Some LAUTI instances have been facing extended DDoS attacks lately. For our own instance @eintopf@sueden.social we reduced the load by deploying @CrowdSec@infosec.exchange which seems to have stablized the situation. We'll keep monitoring and see how it goes. Any other instances having these issues?
![Laura Sophia [not main account]](https://social.queerit.org/images/avatar.png "Laura Sophia [not main account]"){kind=avatar}
Some point this year I tried to test the services queerit.org is offering including a Fediverse instance running on bonfire. This seems to be very buggy. My account there is @livho@social.queerit.org . When I log in into that account I can see most of my notifications I see here on my main account @livho . Basically all notifications with mentions of @livho regardless of the server. And the account mirrors parts of my main account as if it was sent by that account (Very visible from the public profile: https://social.queerit.org/@livho ). It also creates some other glitches where the account appears in the notifications of other people.
To me this sounds like a very bad bug that allows anyone to basically clone a profile of someone else and start interacting with followers of that profile.
@livho@social.queerit.org we fixed quite a lot of bugs in recent versions - 1.0.5 is much more stable nowadays
