Conversation

Notices

1. Embed this notice
   Tim Chambers (tchambers@indieweb.social)'s status on Monday, 02-Jun-2025 07:48:41 JST Tim Chambers

   • dansup
   • Scott Jenson
   • Mark Jardine :misc_mtb:
   • Thomas Ricouard
   • Elk
   • Mona app
   • Chee Aun 🤔
   • sam henri gold

   I’m working on a blog post “The 7 Deadly Sins of the (Current) Fedeiverse Web #UX” … a quick readable but thorough listing of the top 7 things many on the #Federerse have been trying to fix for a long time, making some gains on - but that everyone knows needs to be fixed. Not specific to any one Fedi platform. Only abt Web UX. What would you add? cc: @scottjenson @cheeaun @elk @dimillian @MonaApp @dansup @mark @samhenrigold

   • Embed this notice
     Dr. Matt Lee (mattl@social.coop)'s status on Monday, 02-Jun-2025 08:23:14 JST Dr. Matt Lee

     in reply to

     @tchambers Following other people on other servers is awful.

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Monday, 02-Jun-2025 08:28:22 JST Tim Chambers

     in reply to

     • Dr. Matt Lee

     @mattl #spoilers that will be sin #2…

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Monday, 02-Jun-2025 08:30:22 JST Tim Chambers

     in reply to

     • Dr. Matt Lee

     @mattl And if the first blog post on this is well received in the constructive spirit I will give it I might do a sequel just for Bluesky.

   • Embed this notice
     Dr. Matt Lee (mattl@social.coop)'s status on Monday, 02-Jun-2025 08:47:54 JST Dr. Matt Lee

     in reply to

     @tchambers It's the reason I use Mastodon so differently to Bluesky, but also Bluesky is where I post about my hobby stuff, not here. Here I try and talk about technology stuff when I can.

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Monday, 02-Jun-2025 08:55:44 JST Tim Chambers

     in reply to

     • Pavel A. Samsonov

     @PavelASamsonov D’oh! Fixed it. Thanks..

   • Embed this notice
     Pavel A. Samsonov (pavelasamsonov@mastodon.social)'s status on Monday, 02-Jun-2025 08:55:45 JST Pavel A. Samsonov

     in reply to

     @tchambers the uh, which verse?

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Monday, 02-Jun-2025 10:19:30 JST Tim Chambers

     in reply to

     • Pavel A. Samsonov

     @PavelASamsonov Double-D’oh! Fixed it too! Thanks!

   • Embed this notice
     Pavel A. Samsonov (pavelasamsonov@mastodon.social)'s status on Monday, 02-Jun-2025 10:19:31 JST Pavel A. Samsonov

     in reply to

     @tchambers you still missed one 😅

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Monday, 02-Jun-2025 17:18:28 JST Tim Chambers

     in reply to

     • tsk

     @tasket all points I agree with and will point out possible solutions and work arounds for this Sin #2 in my post. If you have seen constructive fixes too lmk.

   • Embed this notice
     tsk (tasket@infosec.exchange)'s status on Monday, 02-Jun-2025 17:18:29 JST tsk

     in reply to

     @tchambers Not having a protocol handler for ActivityPub content is the reason users end up on "foreign" instance pages. And that bandaid, where a foreign instance is prompting you to login to your home server, is very very bad. No user base should ever be conditioned to accept that kind of interaction (a phisher's dream).

     This is also the reason why news, blog, etc. sites avoid putting "Share with fedi" buttons on their pages.

     Having a protocol handler registered for AP would whisk the user to their preferred fedi app or website to handle whichever kind of request they're initiating. Yes, fedi should be that much like email.

   • Embed this notice
     tsk (tasket@infosec.exchange)'s status on Monday, 02-Jun-2025 17:21:46 JST tsk

     in reply to

     @tchambers I would add having zero algorithmic mitigations for TL annoyances, the most glaring being that popular posts re-appear frequently. And if I follow someone, I will see every single message in the threads they start... maybe I only want to see the first two until I click on the thread?

     I would like to see what popular posters are talking about instead of having to temp. mute them over and over to keep my TL readable.

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Monday, 02-Jun-2025 17:21:46 JST Tim Chambers

     in reply to

     • tsk

     @tasket That will be Sin number six I think. Fully agree. And will point out some fediverse friendly solutions.

   • Embed this notice
     Scott Jenson (scottjenson@social.coop)'s status on Monday, 02-Jun-2025 17:35:33 JST Scott Jenson

     in reply to

     • dansup
     • Mark Jardine :misc_mtb:
     • Fediverse News
     • sam henri gold

     @tchambers @dansup @mark @samhenrigold @fediversenews

     There are really two classes of problems:
     1. Simple things that should be fixed ASAP (e.g. Better onboarding)
     2. Hard things because federation just makes everything harder but nobody really understands that (e.g. the "can't see all replies" problem (which is being worked on!))

     I'm so happy you're making this list! Let me know if I can help.

   • Embed this notice
     Tim Chambers (tchambers@indieweb.social)'s status on Monday, 02-Jun-2025 20:16:19 JST Tim Chambers

     in reply to

     • Osma A 🇫🇮🇺🇦
     • Fediverse News

     @osma @fediversenews that’s a biggie but a fix almost ready to launch soon on Mastodon….

   • Embed this notice
     Osma A 🇫🇮🇺🇦 (osma@mas.to)'s status on Monday, 02-Jun-2025 20:16:20 JST Osma A 🇫🇮🇺🇦

     in reply to

     • Fediverse News

     No facility to moderate/manage/promote replies from others. Ie, not delegating the ownership of replies collection including its post order to the OP server. This is an ActivityPub/Streams sin, but it creates havoc everywhere including Web UX.
     @tchambers
     @fediversenews

   • Embed this notice
     tsk (tasket@infosec.exchange)'s status on Tuesday, 03-Jun-2025 18:58:49 JST tsk

     in reply to

     @tchambers Protocol handlers are basically just definitions. The ActivityPub spec at W3C should be revised to include such a definition.... choose a handler prefix such as 'apub://' and include some commentary on which server names (or "bottom-level domain") typically serve what kind of content (for example, if infosec.exchange wanted to do an images service, it could be apub://pix.infosec.exchange). I can't imagine this would take up more than 3 paragraphs. Also, this is "User-friendly Internet 101" stuff from the 90s.