sivy (@sivy@hachyderm.io)
My favorite iOS client is @ivory which I happily paid for, and would pay a bit of a premium for these features.
Would you be more likely to pay for an activitypub/fedi client if it had improved #offline #activitypub features?
(please boost for reach!)
https://hachyderm.io/@sivy/115260200116479246
Show Original Post
nejimaki (@nejimaki@fedibird.com)
クイック理解 Fediverseを始めよう
https://chienomi.org/articles/technology/202509-fediverse.html #fediverse #activitypub #フェディバース
Akkomaとかもカバーしててとてもわかりやすい記事だった。
Show Original Post
display (@display@hub.azkware.net)
If anything, I suggest the one cishet founder member (to my knowledge) of the #ActivityPub protocol, @evan
Show Original Post
CartyBoston (@CartyBoston@mastodon.roundpond.net)
@morebento I know!
When I wanted to learn #activitypub I learned enough #ruby to put debug statements in mastodon, that's how I know #ruby sucks.
Show Original Post
pfefferle (@pfefferle@mastodon.social)
RE: https://notiz.blog/podcasts/exploring-wordpress-textcasting-and-open-web-standards/
If you have not listened yet :)
#ActivityPub #Fediverse #WordPress #textcasting
Show Original Post
podcasts (@podcasts@notiz.blog)
Exploring WordPress, Textcasting, and Open Web Standards
On Open Web Conversations on OpenChannels.fm
https://openchannels.fm/exploring-wordpress-textcasting-and-open-web-standards/
In this episode of the Fediverse Flows series, host Matthias Pfefferle sits down with pioneer technologist Dave Winer. The inventor of blogging, podcasting, RSS, and text casting. Together, they unpack the evolution of the open web, discussing why true interoperability and openness matter more than ever in an age of restrictive social media platforms.
Show Original Post
business (@business@fedi.jaenis.ch)
🍵
Oh, wait, that won't do it this time!
🫖
Hm, you know what?
🥂
Yeah, that feels right.
Another week after my last update on #Anvil. With two more days to go.
📝 Checking the milestones I can attest that the latest update to the demo instance made great progress.
After logging in I can now browse issues and pull requests (a special form of issues) as well as comment on them. Therefore the requirement to log in.
Oh, and you can now turn on and off issues and PRs. From what I understood, PRs are only available when there are files uploaded in the code tab (which makes sense when you think about it).
Since working alone can feel boring, I also implemented the ability to create teams and add people to it. You'll need to know the username of the collaborator. The teams have admin permissions when created this way because I learned that #ForgeFed treat teams as a means to deliver notes to the right people. Access Management was meant to be done through OCAP (object capabilities). Similar to what you can expect from Spritely Institute. ALAS that's not implemented.
So what's left are notification polling, desktop notifications and OAuth login with Vervis. Since Vervis' development was suspended this is effectively off the table.
I plan to write up documentation in the remaining time.
🎢 Of course this week was an adventure in itself. Let me share some learnings!
First, I wrote a small script that populated my user table on the local #Forgejo instance with those from the Big List I shared last time. Among them funsies such as „search” or „undefined”. Let me tell you that this brings debugging to a new level 
🔍️ On the upside I can now handle the pagination when searching for „search”. Yay.
⏲️ As I also run into some long running requests (because the backend was slightly overwhelmed by the number of incoming requests) I added a timeout for API requests (set to five seconds). Still long, but the majority of calls should make it through.
I played around with the team permissions in Forgejo. An area I rarely investigated in the past. As mentioned, by default I went with Admin permission as it is the least hassle. Best practice is following the principle of least privilege. I wasn't able to figure out the right knobs from the API alone so I looked at the web UI. For example, if you turn one privilege to „read”, several others change. Okay … What's the logic behind here? When reaching out to @pere I learned about the purpose of Teams. Okay … so I added a note to the implementation and left it there. It's defo a construction place to get back to. 🚧
Toggling TicketTracker and PatchTracker were easy enough (pendant to Issues and PRs in Forgejo).
💬 There's a rudimentary implementation of comments in Anvil now. It works. I can even show reactions! Speaking of: Svelte-Octicons lack some icons here (say, a laughing emoji). Reactions are underspecified in ForgeFed, but given that comments are #ActivityPub Notes I looked at #GoToSocial for informing myself how to describe a reaction. They're tags there that have an icon go along. But … Forgejo only has emojis for reactions. As in: Unicode. So … shall I use a MIME type of text/plain here? I sense that this could blow up other services …
Do we have a #FEP on the subject? (I haven't browsed …)
Since Pull Requests are Issues in disguise, commenting there was easy, too. I have a superficial understanding of the different pieces that make up a Patch in ForgeFed. So I'm displaying … something? The error handling here is not great. Forgejo is responding with meaningful information but since I long left design specs behind I felt lost on how to handle them. @mray Halp!
When you try it out, take a close look at the URL. I usually go with your profile but the work often happens in organisations. So a manual adjustment might be needed.
🗺️ Navigation is something that would go into an extension of the grant but we reached the end of the road here.
I'd argue it's time to celebrate!
🍻 Cheers!
Show Original Post
pepper0 (@pepper0@aus.social)
@openrisk
few my #ui #ux ideas for #mastodon #fediverse (I don't think those ideas are exclusively mine, and I believe they are shared among others) :
- follow topics, #hashtags not people
- there is feature of "Lists" of multiple people's feeds you follow. Enable to compile those "Lists" not only of few people, but of multiple #tags .
- participate in #piefed #lemmy threads, groups, boards based on your interests.
- allow to start #piefed #lemmy board with any #activitypub fediverse account outside of particular #lemmy #piefed instance.
- if you are interested in classic forums ui, have a look at #NodeBB
- if you are interested in #imageboard #4chan #anonymous ui - there is abandoned Fchan, which doesn't federate.
- #mastodon does need better Home/List digestion presets, to separate users who make 9000 posts per day and compile them in one section vs users who make 1 post per week. It is possible to make such UX separation automatic, but rn we have to create manual Lists for such cases. It could be represented/drawn/rendered in existing trello like, kanban like bars.
- here is my thought : Any sophisticated fediverse web client will end up trying to emulate Tiling Window Manager.
- use desktop & mobile apps, clients, do not hesitate to support good developers with money.
- still waiting for NonJS fedi webapp UI
Bonus question : I've heard there is concepts of groups, forums in #friendica #hubzilla , but haven't seen such, could anyone post a link to such thing, if there is any?
Show Original Post
folkerschamel (@folkerschamel@mastodon.social)
@danabra.mov This is a great technical write-up. But it lives in a nerd bubble that ignores the reality of the world out there. In the end, protocols don’t matter - they’re only tools that can be used in different ways. Much more important are stakeholder interests and intentions, resulting strategies, and how they play out within the reality of network effects.
https://arewedecentralizedyet.online/
#decentralization #decentralizationwashing #atproto #activitypub #bluesky #fediverse #mastodon
Show Original Post
jeffries (@jeffries@ieji.de)
Decent piece on #ATProto, but no mention of #ActivityPub:
https://overreacted.io/open-social/
Show Original Post
objects (@objects@social.t2arc.net)
There's currently no standard in the #Fediverse for determining whether a Unicode string can be used as an emoji reaction.
Currently, it seems to be different for #mitra, #pleroma, #misskey, etc.
For example, pleroma users can send unqualified emoji as reactions, but mitra(mitra-web) users can't.
#ActivityPub
Show Original Post
post (@post@piefed.social)
Episode 44 - Ben Goering - Wallet Storage, ActivityPub - Livestream 2025-09-26
https://piefed.social/post/1314825
Show Original Post