We had a great gathering for I ❤️ Free Software Day #ilovefs in Amsterdam! We had a simultaneous Dutch and English reading of a
Ada & Zangemann by @kirschner of @fsfe. Afterwards we had a discussion with @tommi and @mayel of @Bonfire . It was such a pleasure to work with @nicorikken and @Holly . Thank you to everyone who came for the afternoon and brought their kids! Great to read to the next generation.
Mayel
Tending to @bonfire@bonfire.cafe 🔥
We are ready for I ❤️ Free Software Day #ilovefs in Amsterdam! Looking forward to a wonderful double event with FSFE and Bonfire. @tommi @nicorikken @mayel
If you're in Amsterdam this Saturday join us for reading of Ada & Zangemann by @kirschner@mastodon.social & Sandra Brandstätter in English and in Dutch, followed by a conversation about Free Software maintenance as care work, together with @mayel from Bonfire, at the @internetarchiveeurope@toot.community, Oudeschans 16, Amsterdam on Saturday Feb 14th at 14:00. More information and RSVP here.
💕 I Love Free Software Day 2026 💕
For this year’s I Love Free Software Day I am co-organising two special events, and I am super excited about them!
- 🧶 Knitting Our Internet at Snackbar Frieda, Rotterdam, on Friday Feb 13th at 18:00. All information here.
- 🛹 A reading of @kirschner’s Ada & Zangemann in English and in Dutch. After that, a conversation about Free Software maintenance as care work, together with @mayel from @Bonfire ❤️🔥 at the @internetarchiveeurope, Oudeschans 16, Amsterdam on Saturday Feb 14th at 14:00. All information here. Info about the super cool poster in the post below.
#FreeSoftware #SoftwareFreedom #ILoveFS #ILoveFreeSoftware #ILoveFS #IloveFS26 #ournet #KnittingOurInternet #SnackbarFrieda #Rotterdam #Amsterdam #InternetArchive #InternetArchiveEurope #AZbook #Ada #AdaZangemann #reading #event #decentralizaion #InternetHistory #Internet
Anyone know the next place to look for what might be requesting these, or force them to be generated in turn rather than (it appears) concurrently?
Context: I don't know elixir, but for reasons I'm running my own @bonfire@indieweb.social instance on bare metal and I'm happy to mess in source code if needed.
@mavnn@bonfire.mavnn.eu how did you try disabling locales?
Bonfire shared inbox usage
Hi @mayel@sunbeam.city, does Bonfire utilise the sharedInbox value?
I noticed this come through my nginx logs today:
128.140.127.206 - - [21/Jan/2026:19:58:04 +0000] "POST /uid/1/inbox HTTP/1.1" 500 128 "-" "https://btfree.social - Bonfire ActivityPub federation" "-"
/uid/1/inbox is an endpoint specified in my user's inbox, but that actor also sends "endpoints":{"sharedInbox":"https://activitypub.space/inbox"}, so wanted to double-check that Bonfire uses it.
Hi @mayel@sunbeam.city, does Bonfire utilise the sharedInbox value?
I noticed this come through my nginx logs today:
128.140.127.206 - - [21/Jan/2026:19:58:04 +0000] "POST /uid/1/inbox HTTP/1.1" 500 128 "-" "https://btfree.social - Bonfire ActivityPub federation" "-"
/uid/1/inbox is an endpoint specified in my user's inbox, but that actor also sends "endpoints":{"sharedInbox":"https://activitypub.space/inbox"}, so wanted to double-check that Bonfire uses it. It should, it helps reduce the number of requests to send if multiple users belong to the same server 
@julian@activitypub.space Hi yes we send to sharedInbox when there's more than one recipient on that instance, otherwise direct to to the user's inbox.
“Nothing is yours. It is to use. It is to share. If you will not share it, you cannot use it.” ― Ursula K. Le Guin
Love this quote! mastodon.social/@mayel/11522...
“To learn which questions are unanswerable, and not to answer them: this skill is most needful in times of stress and darkness.” ― Ursula K. Le Guin
“Do nothing because it is righteous or praiseworthy or noble to do so; do nothing because it seems good to do so; do only that which you must do and which you cannot do in any other way.” ― Ursula K. LeGuin
“To learn which questions are unanswerable, and not to answer them: this skill is most needful in times of stress and darkness.” ― Ursula K. Le Guin
Don't the captcha people understand that by now we're not selecting motorbikes or fire hydrants but what we think the algorithm thinks other people think they are?
@ozoned@social.ozoned.net Thanks for sharing! That was very useful to watch even if painful at times (mostly because I wanted to jump in with pointers but it was prerecorded :D). I took many notes of things to improve with the documentation and tooling.
Overall, the docs and tooling for deploying directly with docker (compared to those using @coopcloud@social.coop which is the recommended and simpler approach) are out of date and too complex mostly because they've been adapted from the dev ones, and we're thinking about how to offer an alternative method with only a compose file and a .env (though I'd welcome advice about how to do so in a simple way, as the just commands are mostly there to reduce the guide to a handful of steps/commands instead of having to copy paste a lot more, and they also set some variables used in the compose file to make it more flexible, but maybe that's not worth it, or there are some other ways to simplify?)
Here's some hints on the main blockers you encountered:
- you first entered
MIX_ENV=emberwhen you wantedFLAVOUR=ember - if you enter
ctrl+c iniex it pauses the app so it wouldn't respond unless you unpause it (by pressing c for continue) - we recently closed port 4000 which now not open outside of docker's internal network by default (for security since you usually want people to connect through the web proxy in prod) and need to update the docs
- we need to better document that it's also running a web proxy by default on ports 80/443, and point to where the caddy config is
- at one point you were looking at
docker-compose.ymlinstead of the release onedocker-compose.release.yml - during of the following attempts where you tried to run dev you were still following the prod guide instead of the dev guide which uses different just commands and env vars
I'm not sure why you weren't able to connect on port 80 during the first attempt though, as the elixir app logs didn't show anything, and caddy's error log was pretty cryptic, I'd be curious what you'd see on port 4000 if you opened it in docker-compose.release.yml
ah thinking about it more, one of your viewers may have guessed the issue, saying you had to set up a domain and set the hostname. As port 80 redirects to port 443 and that one couldn't work without those.
Attempted to set up @bonfire a couple of times and didn't have success. But hopefully someone can find this valuable and/or tell me what I did wrong to help me learn as well.
https://video.firesidefedi.live/w/sXNGDdqurg59cE3syZ3svU
#peertube #vod #tech #bonfire #fedi #fediverse #it #install
@ozoned@social.ozoned.net Thanks for sharing! That was very useful to watch even if painful at times (mostly because I wanted to jump in with pointers but it was prerecorded :D). I took many notes of things to improve with the documentation and tooling.
Overall, the docs and tooling for deploying directly with docker (compared to those using @coopcloud@social.coop which is the recommended and simpler approach) are out of date and too complex mostly because they've been adapted from the dev ones, and we're thinking about how to offer an alternative method with only a compose file and a .env (though I'd welcome advice about how to do so in a simple way, as the just commands are mostly there to reduce the guide to a handful of steps/commands instead of having to copy paste a lot more, and they also set some variables used in the compose file to make it more flexible, but maybe that's not worth it, or there are some other ways to simplify?)
Here's some hints on the main blockers you encountered:
- you first entered
MIX_ENV=emberwhen you wantedFLAVOUR=ember - if you enter
ctrl+c iniex it pauses the app so it wouldn't respond unless you unpause it (by pressing c for continue) - we recently closed port 4000 which now not open outside of docker's internal network by default (for security since you usually want people to connect through the web proxy in prod) and need to update the docs
- we need to better document that it's also running a web proxy by default on ports 80/443, and point to where the caddy config is
- at one point you were looking at
docker-compose.ymlinstead of the release onedocker-compose.release.yml - during of the following attempts where you tried to run dev you were still following the prod guide instead of the dev guide which uses different just commands and env vars
I'm not sure why you weren't able to connect on port 80 during the first attempt though, as the elixir app logs didn't show anything, and caddy's error log was pretty cryptic, I'd be curious what you'd see on port 4000 if you opened it in docker-compose.release.yml
Are you still on #Spotify?
Spotify’s CEO Daniel Ek has raised €600M for his new startup, which is developing AI TECH FOR WAR. Ek still owns 9% of Spotify, but has 37% voting control. His net worth went from $2.5B to $10B in the last two years alone, on the back of paying musicians a pittance in royalties.
And don’t forget:
• Spotify spent $250M of your subscription dollars to invite Joe Rogan to spew his disinformation on their platform.
• They’re still trying to embrace and extinguish Podcasts.
• They’re developing in-house, AI-generated “music” so users will play them (royalty-free) instead of music created by humans (who demand royalty).
And now, he’s using his wealth, created by your subscriptions, to fund tech that will use AI to literally murder humans in war.
Stop funding him. Quit Spotify now.
#QuitSpotify #music #ai#militaryTech #techbro
“Spotify’s CEO invests $1 billion into an AI military start-up — and musicians are fuming”
"Men who sell machines that mimic people want us to become people who mimic machines. They want techno feudal subjects who will believe and do what they’re told. We, as people, are being strategically simplified. This is a fascist process."
https://organizingmythoughts.org/some-thoughts-on-techno-fascism-from-socialism-2025/
Well, it’s official: I have been released from my employer and I am now looking for new employment.
I am an Elixir and Ruby on Rails software engineer with a penchant for learning new languages and technologies quickly. I am a keen problem solver and an excellent communicator. I am passionate about building tools with open source software for the good of mankind. I also have a background in electronics and RF mesh networking.
I prefer remote, but would be open to a hybrid position in the Fort Worth, Texas area.
Bonfire's progressive web app is getting cool 🤟
Like, looking at what my hypothetical person 2 thought they were doing -- there is no need for them to assume that is a clean or perfect block, or that there is no way for it to get exposed. Most people who have used blocks in any sort of social platform know that with alt-accounts or friends, or just normal social dynamics, the person they block can find out. That capacity even with that limitation is nevertheless /enough/ for them to want it.
In this case, that still-CAN-be-revealed requires either active testing of each possible block, or very engaged social surveillance.
Which is often discussed, and which people seem to discuss and understand Bluesky's block issue as being qualitatively different than.
@gaditb@icosahedron.website oh yeah they're definitely different! maybe enough that each (or something in between, like showing what boundaries you applied to people who you give permission to) may be desired in different situations or use cases?