Testing file sharing
Great to see so much development @ivan !
I have a qustion for a specific use case (could also ask this somewhere else, but why not here):
Say, I set up a rather local-focused bonfire instance, for example, inviting all people from my small village to have an account. I would like to be able to:
1) Post my opinion about, say, synthesizers to be read by people from all known instances. (and of course let all villager post about whatever they find interesting)
2) Allow villagers to post stuff about our village that is only visible for people in the village. For example, I could invite people for helping organizing a cleanup day in the village hall. If I understand correctly, this would be done by setting the boundary to local on my village instance.
3) On my instance, I would like to offer all accounts a default custom feed that only shows local stuff (as posted under point 2). Most villagers don't care about my opinion about synthesizers, they just wanna see what's going on in the village. (so, that is different from the current default "local" feed)
I would really love it when this third option would be possible. The literal example given here would be a serious use case, but I can think of many more.
@gilles thanks again for the suggestion, this feed is now available: campground.bonfire.cafe/feed... (which you can pin to your sidebar in feed settings)
I've had multiple bugs while trying to create a user from Android phone. Similar to @Sabrina's post, but perhaps worse...
I managed to sign up my email and verify it. In the "create user" page, the "Create" button was hidden by the notification with the green V at the bottom (something like "Welcome back"). I could scroll a bit to a specific spot where the text was visible. I could tap the button, but then it was only replaced by another one, this time I didn't manage to see what was written. The main bug here is that the "Welcome back" message should have disappeare I believe after a few seconds or upon scrolling.
The worse thing then was that if I tried to go back, or open another tab of campground.bonfire.cafe, I got the non-logged in front page, and tapping Login or Sign up just reopened the same page! So I was basically stuck in a loop.
I created the user from desktop, but to stop the loop I had to clear the cookies, after which I did manage to login on the mobile.
Specs: Fairphone 4, android 15, Firefox 153.0.2
Hello hello, came in to check Bonfire out aftera reading the latest release about groups, as this was definitely the main thing I felt missing on Mastodon - being able to talk to only a known select group of people, so that I could share more personal stuff; and also to have groups about a specific subject that wouldn't drown in the endless feed.
Hey! Hoping I'm not just creating noise by sharing this, but on mobile (iOS) I wasn't able to do a full sign up flow because the "create profile" button was hidden behind the "Login/Sign up" default bar. I'll mostly be accessing bonfire on mobile, so it was a tad frustrating to only partially sign up. I'm here now though!
hello, trying out bonfire because i am legally required to have an account on every fedi platform i think
Geophonodesic heterotopia
©JeanVoguet2017
I see that Bonfire uses the ampersand for its group notation
@LiquidParasyte that's a placeholder, it might end up being @ or ! or whatever...
I see that Bonfire uses the ampersand for its group notation
Testar hur det funkar att publicera något här.
Hi
@spirit welcome!
Still just kind of messing around, but....
I noticed CORS wasn't open on Bonfire (or at least not this Archipelago version of Bonfire) and since we're using javascript for logging in to remote instances on Pelago (pelago.1sland.social) I needed to build a proper proxy, in cases where an instance requires same-origin for wellknown, nodeinfo and other discovery endpoints.
But here it is. You can log into Pelago with Bonfire now. 😊
Proper support subscribing as an island admin will likely require Bonfire opening up the Mastodon admin API, notably the 'domain_allows' api for reading purpuposes only, at least.
To explain: For island admins where everyone is in allowlist mode, unless you have mutual federation going on, in other words, unless both sides have the other on their allowlist, it's not going to work. Pelago essentially checks all the members of an archipelago and confirms that all members have each other on their allowlists (and thus have full federation through the archipelago).
Additionally, for this to truly integrate properly with Bonfire, this instance would need to allowlist pelago.1sland.social so it could send notifications to the admin of the instance.
