@mayel@playground.bonfire.cafe
Admin

A bonfire builder. They/them.

We've updated the playground to run the new "community" flavour of Bonfire, which includes the new groups and topics extensions (which are work in progress).
+groups_topics

Hey friends! Please join the new test instance at <a href="https://campground.bonfire.cafe" target="_blank">https://campground.bonfire.cafe</a><p><br/></p><p>We also updated the website at <a href="https://bonfirenetworks.org" target="_blank"><a href="https://bonfirenetworks.org">bonfirenetworks.org</a></a> which hopefully explains the project a bit better </p><p><br/></p><p>While the playground was about experimenting with the UX and all the different features and extensions in the works, the campground only has the core and social extensions enabled while we focus on stabilising them (incl. federation) before a v1.0 release.</p><p><br/></p><p>(We'll come back on the playground and the other features soon, don't worry!)</p><p><br/></p><p><a href="https://indieweb.social/@bonfire/109809198596802420">indieweb.social/<span class="h-card"><a class="u-url mention" data-user="@bonfire" href="https://playground.bonfire.cafe/pub/actors/bonfire" rel="ugc">@bonfire</a></span>/109...</a></p>

on misskey when I close the compose window it brings my draft back when I re-open it. idk if I prefer this behavior but I'm definitely not used to pop-up notifs

Somebody was working on a PR for saving drafts... In the meantime in the next release your draft will stay in place while you navigate between pages at least.

This sounded like an interesting idea, simple, but i'm not sure Ive come across it before.<p><br/></p><p>I havent thought it through much and possibly activitypub wouldn't play nice? Still thought bonfire folks may be interested</p><p><br/></p><blockquote>you should be able to delete their replies. Maybe the toot would still exist on their profile, but it’d be completely severed from your original toot so your followers don’t have to see it.</blockquote><p><br/></p><p>https://social.coop/@yerald/109407348453747373</p><p><br/></p><p>#bonfire_feedback</p><p>+safety </p>

@Dazinism Interesting... ActivityPub would likely not allow actually deleting other people's comments once they've federated, but there's some things could do along these lines:
  • Delete your instance's copy of a comment in a thread you started, so that people who read the canonical thread will not see that comment.
  • Block someone from participating in a thread so their comments will only spread to the followers of the commenter (and other users of their instance) but won't be accepted by your instance and won't be forwarded to your followers.
  • Lock a thread you started so that any further replies will be treated the same as in the previous point.


Most of this should be pretty easy to implement using existing functionality such as boundaries, and would be usuful both for thread starters and Topic curators. But anything we can do with those will be limited compared to we'll be able to do when implementing proper Groups.

Eventually an entire extension would be ideal, just like I could reply to tasks, I’d like to be able to reply (if the instance policy lets me do it) to instance block announcements, if possible directly, as a mod, from the social extension; I’d like as well to be able to share these instance blocks to different circles by boundary, as usual, and for example to let a large circle of instance roles follow my instance blocks, and a smaller circle of instance roles comment or interact with these instance blocks (otherwise than by clicking on the "block" button).<p><br/></p><p>The main difference would be, I suppose, that these boundaries would be set by a specific role on behalf of the instance and that you wouldn’t manage the permissions user by user, but instance role by instance role, e.g. if you have moderators and new_followers_monitors on instance A and B, then you let all the moderators on instance A follow the instance blocks, but you’re free to assign different permissions to the moderators on instance B.</p>

We've talked about doing something like this in the past. Of course it would be much more useful if we can agree with other fediverse apps on a standardised way to do it.