Discussion
@lauti It's okay, Lemmy and Friendica put a server actor there.
>activity delivery issues
My server drops your Accept activity because you don't sign the Digest header.
@silverpill@mitra.social yes, that was it! We succesfully federated the first event from lauti to mastodon (and maybe other fediverse software too) 🎉
If you want to receive random test events follow @events@lauti.sankara.klasse-methode.it 😆
Is it okay if the instance actor id is equivalent to the instance url? Does anyone know if most other implementaions support this?
Also if anyone can help with debugging some activity delivery issues that would be awesome 🙏 #activitypub #fedidev
@events@lauti.sankara.klasse-methode.it is our test server. But if you try to follow it the Accept is not being delivered properly
Is it okay if the instance actor id is equivalent to the instance url? Does anyone know if most other implementaions support this?
Also if anyone can help with debugging some activity delivery issues that would be awesome 🙏 #activitypub #fedidev
Cose difficili
Test from icecube 🥸
@Bonfire@bonfire.cafe Running it already!
Hmm. I seem to be having some issues with search. Do I need to change anything on the config side for 1.0.4? (Trying to tag somebody in the composer is showing me ActivityPub IDs, not tags, and trying to use the search box just starts a UI reload loop)
@mavnn@bonfire.mavnn.eu thanks for reporting! We can reproduce the autocomplete issue but not the search, could you please send us app logs of when it refreshes?
Checked if there was a @Bonfire@bonfire.cafe release for the first time in a few days and noticed there was, and then was puzzled when I couldn't download the container image.
On double checking the time stamps, turns out I had tried to pull the image less than 2 minutes after Mayel pushed the commit.
@mavnn@bonfire.mavnn.eu it's out now 😊
Thanks @erictapen@chaos.social for creating this need FEP-8a8e compliance checker. We already integrated it into our CI to support the development of #activitypub into #LAUTI.
@phanpy@hachyderm.io never stops surprising me with small but meaningful UX details... just saw how it shows alt descriptions as footnotes below uploaded media, and i want to do the same in bonfire... chapeau @cheeaun@mastodon.social 🎩
Finally reading Octavia butler
@Bonfire@bonfire.cafe Just as a heads up, this post renders as an audio file for me? Following the link to the source file takes me to the 1.0.3 release announcement
@mavnn@bonfire.mavnn.eu thanks for the heads up! we were testing a new feature, still a few rough edges 😊
We just released Bonfire Social 1.0.3 🔥
Blog post with all the details: bonfirenetworks.org/posts/bo...
It comes with dozens of bug fixes and UX improvements, plus:
#CalmEmpowerment: a new design pattern that starts with a few sensible defaults, offers a middle layer of common adjustments, and reveals the full options only when you need them. Boundaries and post permissions got this treatment first, more to follow...
Modular community rules: a first step in bringing research and co-design with students and researchers at @hci@micro.blogs.princeton.edu into Bonfire, so governance becomes something communities can better define and share, and that others can fork and adapt.
@csolisr@hub.azkware.net ah yeah it probably would have to built for (ideally on) your machine in this case
Terrible moment to learn that #Bonfire, the up-and-coming #ActivityPub implementation, apparently has a hard dependency on #AVX instructions that my home server's chipset physically lacks. I'd have to spend upwards of $400 just to replace my server in order to test it, sigh... @Bonfire
@csolisr@hub.azkware.net Which dependency did you see on AVX? our markdown renderer for example uses it when available but has a fallback which should be enabled automatically when not available (otherwise you can force it with `MDEX_USE_LEGACY_ARTIFACTS=true`. In any case please provide more info or open a bug report.
just discovered another super interesting and needed work done by @s0hw@hci.social and @andresmh@hci.social platform.coop/blog/toward-wo...
"Aiming to shift control of delivery work away from a single entity, OpenCourier is a protocol that defines data formatting and communication across a decentralized network of delivery platforms, couriers, and service requesters. Broadly, we aim to enable an ecosystem (Fig. 1) that centers community-owned delivery platforms, where workers — who we refer to as couriers, given their work providing delivery services — cooperatively manage the platform they are a part of. "
📄 here the full paper dl.acm.org/doi/pdf/10.1145/3...
cc @mayel @lynnfoster@social.coop @bhaugen@social.coop #bonfire #valueflows
is there any "code of conduct / use Protocol" out there ? (that serialise rules a bit like CC does with picto > articles with modularity) ... could it be used to help on federation mod ? (and also to ease users choose a server more easily than reading a long list of text on each) #moderation #mastodon #activitypub
@olm_e@tchafia.be students in the class led by @s0hw@hci.social and @andresmh@hci.social at hci.princeton.edu have worked on something like this which was previewed at the last #FediForum and will launch in the summer...
@evan @mayel I stand by my positions that an E2EE protocol:
a) should not allow a server to know who is in a conversation, so therefore server-level blocks cannot be applied (unless applied client-side)
b) if a conversation is reported to server admins/moderators, doing that report via E2EE really doesn't gain you anything over just TLS. Server will end up with that information in cleartext at some point. But you do want verifiability of the messages & their ordering and the actor IDs involved, probably a new object type to represent a Conversation.
I tried to address your first point here: github.com/swicg/activitypub...
Not sure I understand why you say "server will end up with that information in cleartext at some point" though?
watching the intro to @Bonfire Mosaic, its looking really good, and see they are making lots of progress with fediverse groups
https://videos.scanlines.xyz/w/hV9wzGzsXvNjgXtVg3uS2i
I really hope they don't introduce new handle semantics tho at I see from the demo they are using &groupname@instance.tld as opposed to !groupname@instance.tld that lemmy is already using and @groupname@instance.tld that most of the rest of the fediverse already supports to some extent
@liaizon@social.wake.st those are just placeholders, our goal is maximum interoperability while also extending what is possible, and we're participating in the W3C groups task force to define how things should work, please weigh in there if you have any suggestions: github.com/swicg/groups/issues
Install bonfire.cafe
Get the full app experience
