Look, I think AI can hypothetically be "useful" in certain specific limited contexts, but relying wholly on AI-generated code for a project is profoundly stupid. I think it's fine for rubber-ducking ideas or exploring a pool of information, but some people use it wholesale without knowing basic fundamentals. I know learning to code can seem difficult. There's a lot of trial and error, a lot of failure, and sometimes the problem you're trying to solve is way more difficult than you thought it was. This is normal, and part of learning. It's okay if it takes longer, or if you have to struggle with certain stumbling blocks. That's how you get good! Not everything has to be about maximizing output for productivity, especially if that output has issues that you have no insight or capability of fixing. It is in fact okay to go at a gradual pace.

Nice! There's still a fair amount of jank, that jump animation is appalling, and part of his hair does culling at random camera angles. But, I took my custom character and made him move! #GameDev #Godot

If I were to make a small game about the Fediverse, it would probably be about project management. It might look like Civilization or another political management game, but also have an insane amount of WarioWare-like mini games. If you fail them, your approval ratings go down.

A question for #Fediverse devs: I'm thinking about better ways to document development of the #ActivityPub stack. This would include explanations, demo code, example snippets, and various sections explaining how to build a fully working Fediverse server, with consideration for all of the FEP documents as well. What do you, as a developer, feel is currently missing? What information would make your life a lot easier?

This is a really great read by the @npub1lzdq...urpr team. As someone who has done all kinds of experiments with long-form articles and publishing directly on the #Fediverse, there are a number of headaches and hurdles we still need to figure out. My overall philosophy is this: rather than adapting existing content management systems to use ActivityPub federation, it's preferable to build a CMS for the Fediverse, with explicit considerations for how the instance and the network should interact with each other. Everything, from the dashboard to side-effects of interaction, should be designed with federation considerations in mind.

bonfire.cafe

Long-form content in Bonfire: Part 1

A space for Bonfire maintainers and contributors to communicate

I've been writing a long, long response to the excellent article by @npub1vag7...mjkp about the Seven Deadly Sins of Fediverse UX design. It's taken me almost a month, and I'm just trying to get through the last few sections. Hopefully, I'll be able to post it tonight. 😅

I'm kind of tempted to try setting up a @npub1h3fv...6sq8 instance for We Distribute. Could be interesting to have a bunch of little badges for exploring the network or learning about it? 🤔

In case you're just tuning in, we're covering Day 2 of #FediForum. @npub1urx3...v0z4 giving the opening keynote about Spritely, and it's great. https://wedistribute.org/2025/06/fediforum-june-2025/

Hey, go check out our latest episode of Decentered! @damon and I are really excited to be making this again. View quoted note →

Hey, listen. #Codeberg is being spammed with LLM bots right now. They started like an hour ago. Each bot is opening up one issue in a random tracker every minute. I have no idea what the spread is, but each individual bot has like seven pages full of issues now. PieFed and FEP are both starting to see issues piling up because of this. View quoted note →