As we integrate #OpenAlex data into the #Bonfire #OpenScience flavor, we're displaying familiar metrics: works count, citations, h-index, research topics, institutional affiliations...
These might be exactly what you need, or perhaps just a starting point.
What additional information would help you find collaborators or understand someone's work better?
We're opening this design process to the open science community. Share what works, what doesn't, what's missing.
@open_science
1/2
bonfire
🌊 Exciting news! Crowdinblue - a mission-led initiative bridging water solutions with funding - has chosen #Bonfire to build their federated community space!
Together, we're designing custom extensions to connect water projects with impact investors and crowdfunding opportunities. All in a federated environment that puts communities and projects first.
Welcome to the Bonfire ecosystem, crowdinblue! 💚
Read more about the project: https://crowdinblue.org
#CommonsEconomy #WaterJustice #Fediverse
Edited 1y ago
Hi #fediverse and #ActivityPub developers!
I'm currently working on interoperability testing for #Hollo and #Fedify, and I need a #Bonfire account to test federation with their implementation.
Since there aren't many open public Bonfire instances available, I was wondering if any Bonfire instance admins out there would be willing to grant me a test account? It would be a huge help for improving interop! Let me know if you can help. Thanks!
Here's another cool feature of Bonfire. One account, many profiles.
When you create an account, you can create multiple profiles, each with it's own unique followers, content and settings (and emojis!).
1 account. 1 password. Many profiles.
Ownership of profiles can be shared with others. A news publication can share posting responsibilities, for example.
Edited 1y ago
The recent Hollo 0.7.3 and 0.7.4 updates have improved interoperability with #Bonfire. The issue where sending/receiving DMs or mutual following with Bonfire wasn't working properly has been resolved.
A couple days ago, I got a DM from a #Bonfire user. I happily replied and senta follow request—but the Accept never came back, even though they hadn'tenabled manuallyApprovesFollowers. My DM reply probably never arrived either. Classic interop bug.
I checked out the Bonfire source and dug in. Turns out Bonfire hasn't implemented RFC 9421 yet, so it was silently discarding any activity signed with it. That alone would be workable, except for one more issue: Bonfire was responding 200 OK even when signature verification failed, instead of 401 Unauthorized.
This matters because Fedify implements a double-knocking mechanism—if a request signed with RFC 9421 fails, it retries with the older draft cavage signature. But since Bonfire returned 200 OK on the failed first knock, #Fedify had no reason to send a second one.
I filed two issues on the Bonfire #ActivityPub repo—one requesting RFC 9421 support, and one about returning 401 on invalid signatures. For the latter, I also sent a PR, which got merged pretty quickly: bonfire-networks/activity_pub#9.
That said, individual Bonfire instances won't pick up the fix until they actually deploy it. So in the meantime, I patched Hollo and Hackers' Pub to use draft-cavage-http-signatures-12 as the firstKnock, so Bonfire instances can at least understand the first request.
One last thing: Fedify caches whether a given server supports RFC 9421, and the Bonfire servers I'd already talked to were cached as “supports RFC 9421”—because they'd been returning 200 OK. I had to manually clear that cache on both hollo.social and hackers.pub before everything finally worked.
After all that, the mutual follow went through and my DM reply landed. Worth it.
Edited 259d ago
can anyone comment on how good, or not good, search (for posts) is between self-hosted fedi platform apps good for single-user servers, such as #Snac2, #Mitra, #GoToSocial, #Bonfire, etc?
I am looking for search which is actually usable by someone who wishes to find things and perhaps sort what's found, unlike that provided by e.g. Mastodon, Akkoma, etc.
One of our first experiments with curation and discovery in #Bonfire involves building public-facing actor collections, and then building custom feeds out of those.
In Bonfire, the data sources for custom feeds are Circles, which is a combination of a Collection plus Access Control List. These aren't custom feeds yet, but will be used to power community curation on the instance.
FediDevs:
fedizen.net/circle/01M49AFTC...
Fediverse Boosters:
@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. 🔥
Oooh, neat -- @Bonfire has officially released its #Communities module: https://bonfirenetworks.org/posts/bonfire-for-communities/
I backed the project, and I'm overjoyed to see it coming to fruition. The world *desperately* needs a good open-source, open-network, open-community alternative to enshittified monstrosities like Facebook, and #Bonfire is the first one I've seen that appears to check pretty much all the boxes of "how to do it right". It's impressively complete.
(Might force me to get off my ass and stand up my own server, so I can start hosting some of the communities I'm involved with.)
And yes, yes, Discord -- I use it a lot, but it's still corporate, still likely to enshittify, and really only covers a fraction of the Community use cases. This looks better.
So check it out -- I think it's an important project, that a lot of groups could probably benefit from...
Looking at hosting a #Bonfire or #Wafrn for my Drafty Writers Group. Anywhere that hosts these things for me? Actually, a blogging space would be vastly better, but #WriteFreely has so many accessibility problems I never want to use it again. What other new long form blogging things exist? Something where others can see the blogs and stuff but can never join our instance? #AskFedi #Fediverse