Tootfinder

This week on #ProFed: I was away for most of the week, so less progress than usual. But I used the time I had for some backend groundwork in preparation of the next steps on the web client.
https://codeberg.org/ProFed/ProFed

This week on #ProFed: the web client has its first non-public page: the settings page, complete with login. It's also the first page that doesn't just display data but saves it too. Small step, but it means the full web client stack is now tested end to end.

I have finished the outward architecture of #ProFed as a base for discussion. I've used AI to help me put my braindump into a more consistently readable text. be prepared to see a free AI-isms, though it isn't terrible, I think.

This week on #ProFed: I've documented the outward-facing architecture – ActivityPub extensions, federated search, and how other systems can integrate with ProFed.
This is aimed at developers of other projects who want to build on or cooperate with ProFed.

This week on #ProFed: I implemented the media repository – the foundation for exchanging anything beyond plain text. The Profile Importer now uses it to import and serve avatar and header images.
All #Mastodon API endpoints are also in place – some implemented, the rest as stubs. Next step: …

This week on #ProFed: first full round trip through the web client.
I followed my Mastodon account from the ProFed web client, published a test post that showed up in Mastodon. Then I wrote a reply back in Mastodon that appeared in the ProFed timeline.
Now the ProFed web client can do these tricks, not only the Desktop Mastodon client, where I did the first round trip a while ago.

Here ist the next week in #ProFed. This week I took a break. So there's nothing new to report. I'm back to it already, and next week we'll have some news again.
https://joinprofed.social

This week on #ProFed: security review.
I found a minor issue and took it as an opportunity to systematically check for more security issues. A few small things have been addressed already, more to follow.
The fixes also clean up the architecture in a few places – so the end result is both more secure and cleaner.

This week on #ProFed: federation works in both directions. 🎉 My ProFed account can follow my #Mastodon account, and vice versa. Unfollow works in both directions as well.
HTTP signatures are not only generated for outgoing requests but also verified for incoming ones.

This week on #ProFed: I switched the web client from Svelte to HTMX Jinja2 templates. Svelte would have made small installations unnecessarily complex.
The web client uses exclusively the same API that other clients can use too, to make sure the API actually covers everything it needs to.
1/3

This week on #ProFed: federation is working – in one direction.
I can follow the ProFed test account from my #Mastodon account. The Follow request is accepted, the Accept is sent back, and the account shows up in the following list on Mastodon.
The other direction has all the pieces in …

This week on #ProFed: backend refactoring done, and the basic structure of the web client is in place.
I'm now working on the first pages – which also require new backend endpoints. Client and server are being developed in lockstep, as planned.
https://

This week on #ProFed: mostly refactoring and strengthening the foundations. Next week I expect to have the beginnings of a web client.
https://joinprofed.social

This week on #ProFed: I fixed the bug in the message bus.
Finding the bug was less of a problem. But the solution, that meets all the requirements at this foundational level, was the real challenge.
As a bonus, the message bus is now slightly more efficient and uses fewer resources in most situations. Not a game changer, but still good.