Holos Social @HolosSocial@mastodon.social
Public

We've optimized data loading so feels fast and seamless despite running its own server.

What's next:
- Interaction controls (#GoToSocial approach) to manage who can reply/boost/like your posts
- Keywords filtering on the public timeline to reduce noise and show what matters to you
- Community domain blocklist subscriptions with auto-sync

Tim Chambers @tchambers@indieweb.social
Public

@HolosSocial Question: since you control the client and the server, can you also sand off some long held rough edges of the fedierse? See my list of top issues to fix here and it seems to me you might be able to do some of these more directly in your model than fediverse clients and serers operating separately can...

You already fix server choice, and to some degree discovery.... but what about
item 3 here, remote server interactions...?

timothychambers.net/2025/06/18

The Seven Deadly UX Sins of the Fediverse Web Experience (To Fix)

So, confession time: I was recently helping a new client get set up on the Fediverse—guiding them through their first steps into our glorious decentralized galaxy. And seeing it all again through fresh eyes? Reader, it was brutal. So much of what should be table stakes for any social media UX in the year of our Lord 2025 still is missing or deeply broken still. I know progress has been made and a good fight, fought.

www.timothychambers.net · Tim Chambers

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://indieweb.social/users/tchambers/statuses/116223070361413657 on your instance and quote it. (Note that quoting is not supported in Mastodon.)