Tootfinder

This week on #ProFed: access control overhaul done. And I'm working on turning the post editors into full-featured Fediverse editors with content warnings, image uploads, visibility settings, and more. But first, something to look at:
1/3

This week on #ProFed: the heatwave is taking its toll, so progress is slow.
I've finally consolidated the data structures for ActivityPub objects and activities. But I haven't managed to push through with these changes to the web client. Again nothing visibly, sorry.
Next week I promise - maybe I shouldn't.

This week on #ProFed: access control is largely done.
What used to be ad-hoc decisions scattered across the codebase is now a consistent concept. A few endpoints still to migrate, then it's done.
https://codeberg.org/ProFed/ProFed

This week on #ProFed: out of the WebFinger rabbit hole, and quite a lot done.
Profile links in post headers now point to the ProFed profile page - for local and remote accounts alike. For remote accounts there is a "view on ..." link to the original profile. And boosts are fully working now too. The latter was a rabbit hole of its own.
1/3

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: backend work only, no screenshots.
ProFed no longer sends HTTP requests to itself - everything that can go to the local database now does. The only exception is the web client, which talks to the API like any other client.
Currently working on access control, followed by some counter cleanup. After that, back to visible changes.

This week on #ProFed: the web client now has RSS feeds. Not everywhere yet – authenticated feeds are a harder problem. Every approach I've considered so far is either tooc unsafe, too complicated for regular users, or not supported by most RSS readers.
Ideas very welcome. Are you maybe aware, how other applications do that? Are there any other applications at all, that do that?

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.

This week on #ProFed I just have a few UI improvements.
1. Post timestamps are shown in human-readable form: "now", "5 days ago", with the exact time to the minute on hover.
2. Posts have an action menu with the permalink and delete option for the moment.
3. The reply button now works.
The bigger topic this week: trying to improve the

This week on #ProFed: two new developments in the web client.
ProFed is not a microblogging system. The web client is optimized for professional social networking - which means some things work differently than in Mastodon or similar systems.

This week on #ProFed: emoji reactions are done. By far the biggest rabbit hole yet - the kind with Monty Python killer rabbits and three dragons inside: FEP-c0e0, Pleroma and Misskey, all disagreeing with each other.
1/4

A quick note: recent posts have been in German by mistake. Back to English from now on - sorry for any confusion.
This week on #ProFed: down the emoji reactions rabbit hole. Reactions federate compatibly with both Misskey and Pleroma, including their derivatives. Misskey allows multiple reactions per user per post - ProFed doesn't, to keep things predictable for everyone else.
1/…

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: visible progress again after weeks of backend work.
The immediate trigger was getting timeline entries to render differently by type - but the restructuring opens up much more. Like e.g. moving away from the traditional microblogging view towards something that better fits professional use.