Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

Fediverse wide cross-instance / cross-platform link substitution [UX improvement thoughts]

Fediverse
9 6 31
  • I recently asked for some PeerTube recommendation and it made me realize how disjointed the URL system can seem to the median, not technically-inclined, not-motivated, user.

    The first user UX issue was the link to the lemmy.wtf post. You get transported to the lemmy.wtf webUI client, so you're not logged in and the interface is different (arguably a median user would expect to view the post via their own instance/platform, piefed.social in my case).

    But then we have the issue of PeerTube channel links in the lemmy.wtf post. I wanted to check out the Open Source_gaming channel which is referenced via the following URL:

    https://peertube.wtf/c/opensource_gaming@video.hardlimit.com

    My peertube instance/WebUI client is Spectra Video, so again you encounter another UX issue.

    To add to that, if you paste the URL verbatim (major UX issue in of itself for the median user) into the Specra Video webUI, you won't actually find the opensource_gaming channel:

    sBbwbw4pYXH7WAM.jpg

    fT7HgiPVgHP6GZc.jpg

    You would need to use the following search prompt in the Spectra Video webUI:

    opensource_gaming@video.hardlimit.com

    The upcoming version of Piefed actually addresses this issue on the Threadi side.

    For logged in users, Piefed 1.4 will turn the following URL:

    https://lemmy.world/post/39832275

    into

    https://piefed.social/c/news/p/1544770/national-parks-ordered-to-check-gift-shops-for-dei-type-items

    This issue is unresolved in Lemmy, but the Lemmy brand is permanently tainted among users who are looking for alternatives to American oligarchic technology services. The low moral standards of the Lemmy devs' (support for the brutal North Korean regime, promotion of russian propaganda narratives that they know are false) is a massive turn off for the exact target market of the Fediverse. It's a fact that many Europeans looking for alternatives instinctively recognize the demagoguery of the Lemmy devs and their fans.

    But even with Piefed 1.4, the PeerTube linking UX (same for Mastodon and I am assuming Pixelfed, Loops and other Fedi services) is a nightmare for the median user.

    What would be helpful is to have a system where the first time a user encounters a Fedi link, they would be prompted to select their instance for a given Fedi service.

    So clicking on a peertube.wtf (terrible name if their goal is to go beyond a "niche within a niche" userbase) for the first time when logged in would give you a notice similar to:

    Enjoy a user focused video platform! Sign up | Login into Peertube

    There are clearly some UX issues with this, but I still think it would be better than the current system.

    Would would be even better is if some of the major Fedi instances in a given service could somehow automate the discovery of existing user accounts for other Fedi services.

    This would either need to be done in a whitelist only manner (i.e. discovery only works between say piefed.social (or piefed.world) and mastodon.social and/or some sort of client side system, if that's even possible. You don't want sketchy instances or spammers to be able to poll all of a user's accounts across Fedi services.

    I am assuming this is a client-side issue and it cannot be solved at the protocol level (ActivityPub), but in a way this makes it easier to experiment as Fedi clients can try out things without modifying the ActivityPub protocol.

    Just wanted to share my thoughts. If one wants Fedi to become a viable alternative to corrupt American monopolists, then you must look at the UX from perspective and expectations of a median user.

  • I recently asked for some PeerTube recommendation and it made me realize how disjointed the URL system can seem to the median, not technically-inclined, not-motivated, user.

    The first user UX issue was the link to the lemmy.wtf post. You get transported to the lemmy.wtf webUI client, so you're not logged in and the interface is different (arguably a median user would expect to view the post via their own instance/platform, piefed.social in my case).

    But then we have the issue of PeerTube channel links in the lemmy.wtf post. I wanted to check out the Open Source_gaming channel which is referenced via the following URL:

    https://peertube.wtf/c/opensource_gaming@video.hardlimit.com

    My peertube instance/WebUI client is Spectra Video, so again you encounter another UX issue.

    To add to that, if you paste the URL verbatim (major UX issue in of itself for the median user) into the Specra Video webUI, you won't actually find the opensource_gaming channel:

    sBbwbw4pYXH7WAM.jpg

    fT7HgiPVgHP6GZc.jpg

    You would need to use the following search prompt in the Spectra Video webUI:

    opensource_gaming@video.hardlimit.com

    The upcoming version of Piefed actually addresses this issue on the Threadi side.

    For logged in users, Piefed 1.4 will turn the following URL:

    https://lemmy.world/post/39832275

    into

    https://piefed.social/c/news/p/1544770/national-parks-ordered-to-check-gift-shops-for-dei-type-items

    This issue is unresolved in Lemmy, but the Lemmy brand is permanently tainted among users who are looking for alternatives to American oligarchic technology services. The low moral standards of the Lemmy devs' (support for the brutal North Korean regime, promotion of russian propaganda narratives that they know are false) is a massive turn off for the exact target market of the Fediverse. It's a fact that many Europeans looking for alternatives instinctively recognize the demagoguery of the Lemmy devs and their fans.

    But even with Piefed 1.4, the PeerTube linking UX (same for Mastodon and I am assuming Pixelfed, Loops and other Fedi services) is a nightmare for the median user.

    What would be helpful is to have a system where the first time a user encounters a Fedi link, they would be prompted to select their instance for a given Fedi service.

    So clicking on a peertube.wtf (terrible name if their goal is to go beyond a "niche within a niche" userbase) for the first time when logged in would give you a notice similar to:

    Enjoy a user focused video platform! Sign up | Login into Peertube

    There are clearly some UX issues with this, but I still think it would be better than the current system.

    Would would be even better is if some of the major Fedi instances in a given service could somehow automate the discovery of existing user accounts for other Fedi services.

    This would either need to be done in a whitelist only manner (i.e. discovery only works between say piefed.social (or piefed.world) and mastodon.social and/or some sort of client side system, if that's even possible. You don't want sketchy instances or spammers to be able to poll all of a user's accounts across Fedi services.

    I am assuming this is a client-side issue and it cannot be solved at the protocol level (ActivityPub), but in a way this makes it easier to experiment as Fedi clients can try out things without modifying the ActivityPub protocol.

    Just wanted to share my thoughts. If one wants Fedi to become a viable alternative to corrupt American monopolists, then you must look at the UX from perspective and expectations of a median user.

    Well; atleast for lemmy, there's https://lemmyverse.link/ ; which fixes exactly what you mention. You send that link, other people choose their instance in the redirect, and boom!

  • Well; atleast for lemmy, there's https://lemmyverse.link/ ; which fixes exactly what you mention. You send that link, other people choose their instance in the redirect, and boom!

    It's a temporary workaround but the experience is still clunky

  • I recently asked for some PeerTube recommendation and it made me realize how disjointed the URL system can seem to the median, not technically-inclined, not-motivated, user.

    The first user UX issue was the link to the lemmy.wtf post. You get transported to the lemmy.wtf webUI client, so you're not logged in and the interface is different (arguably a median user would expect to view the post via their own instance/platform, piefed.social in my case).

    But then we have the issue of PeerTube channel links in the lemmy.wtf post. I wanted to check out the Open Source_gaming channel which is referenced via the following URL:

    https://peertube.wtf/c/opensource_gaming@video.hardlimit.com

    My peertube instance/WebUI client is Spectra Video, so again you encounter another UX issue.

    To add to that, if you paste the URL verbatim (major UX issue in of itself for the median user) into the Specra Video webUI, you won't actually find the opensource_gaming channel:

    sBbwbw4pYXH7WAM.jpg

    fT7HgiPVgHP6GZc.jpg

    You would need to use the following search prompt in the Spectra Video webUI:

    opensource_gaming@video.hardlimit.com

    The upcoming version of Piefed actually addresses this issue on the Threadi side.

    For logged in users, Piefed 1.4 will turn the following URL:

    https://lemmy.world/post/39832275

    into

    https://piefed.social/c/news/p/1544770/national-parks-ordered-to-check-gift-shops-for-dei-type-items

    This issue is unresolved in Lemmy, but the Lemmy brand is permanently tainted among users who are looking for alternatives to American oligarchic technology services. The low moral standards of the Lemmy devs' (support for the brutal North Korean regime, promotion of russian propaganda narratives that they know are false) is a massive turn off for the exact target market of the Fediverse. It's a fact that many Europeans looking for alternatives instinctively recognize the demagoguery of the Lemmy devs and their fans.

    But even with Piefed 1.4, the PeerTube linking UX (same for Mastodon and I am assuming Pixelfed, Loops and other Fedi services) is a nightmare for the median user.

    What would be helpful is to have a system where the first time a user encounters a Fedi link, they would be prompted to select their instance for a given Fedi service.

    So clicking on a peertube.wtf (terrible name if their goal is to go beyond a "niche within a niche" userbase) for the first time when logged in would give you a notice similar to:

    Enjoy a user focused video platform! Sign up | Login into Peertube

    There are clearly some UX issues with this, but I still think it would be better than the current system.

    Would would be even better is if some of the major Fedi instances in a given service could somehow automate the discovery of existing user accounts for other Fedi services.

    This would either need to be done in a whitelist only manner (i.e. discovery only works between say piefed.social (or piefed.world) and mastodon.social and/or some sort of client side system, if that's even possible. You don't want sketchy instances or spammers to be able to poll all of a user's accounts across Fedi services.

    I am assuming this is a client-side issue and it cannot be solved at the protocol level (ActivityPub), but in a way this makes it easier to experiment as Fedi clients can try out things without modifying the ActivityPub protocol.

    Just wanted to share my thoughts. If one wants Fedi to become a viable alternative to corrupt American monopolists, then you must look at the UX from perspective and expectations of a median user.

    Mbin has had that feature for a while too

  • Well; atleast for lemmy, there's https://lemmyverse.link/ ; which fixes exactly what you mention. You send that link, other people choose their instance in the redirect, and boom!

    I've seen that being used. It works fine for more technical users, but it's just an extra pain point.

    • If you make links, you need to apply the service
    • Different UI from whatever instance/client/platform that you are using.

    I much prefer Piefed's soon to be released link substitution feature.

  • I recently asked for some PeerTube recommendation and it made me realize how disjointed the URL system can seem to the median, not technically-inclined, not-motivated, user.

    The first user UX issue was the link to the lemmy.wtf post. You get transported to the lemmy.wtf webUI client, so you're not logged in and the interface is different (arguably a median user would expect to view the post via their own instance/platform, piefed.social in my case).

    But then we have the issue of PeerTube channel links in the lemmy.wtf post. I wanted to check out the Open Source_gaming channel which is referenced via the following URL:

    https://peertube.wtf/c/opensource_gaming@video.hardlimit.com

    My peertube instance/WebUI client is Spectra Video, so again you encounter another UX issue.

    To add to that, if you paste the URL verbatim (major UX issue in of itself for the median user) into the Specra Video webUI, you won't actually find the opensource_gaming channel:

    sBbwbw4pYXH7WAM.jpg

    fT7HgiPVgHP6GZc.jpg

    You would need to use the following search prompt in the Spectra Video webUI:

    opensource_gaming@video.hardlimit.com

    The upcoming version of Piefed actually addresses this issue on the Threadi side.

    For logged in users, Piefed 1.4 will turn the following URL:

    https://lemmy.world/post/39832275

    into

    https://piefed.social/c/news/p/1544770/national-parks-ordered-to-check-gift-shops-for-dei-type-items

    This issue is unresolved in Lemmy, but the Lemmy brand is permanently tainted among users who are looking for alternatives to American oligarchic technology services. The low moral standards of the Lemmy devs' (support for the brutal North Korean regime, promotion of russian propaganda narratives that they know are false) is a massive turn off for the exact target market of the Fediverse. It's a fact that many Europeans looking for alternatives instinctively recognize the demagoguery of the Lemmy devs and their fans.

    But even with Piefed 1.4, the PeerTube linking UX (same for Mastodon and I am assuming Pixelfed, Loops and other Fedi services) is a nightmare for the median user.

    What would be helpful is to have a system where the first time a user encounters a Fedi link, they would be prompted to select their instance for a given Fedi service.

    So clicking on a peertube.wtf (terrible name if their goal is to go beyond a "niche within a niche" userbase) for the first time when logged in would give you a notice similar to:

    Enjoy a user focused video platform! Sign up | Login into Peertube

    There are clearly some UX issues with this, but I still think it would be better than the current system.

    Would would be even better is if some of the major Fedi instances in a given service could somehow automate the discovery of existing user accounts for other Fedi services.

    This would either need to be done in a whitelist only manner (i.e. discovery only works between say piefed.social (or piefed.world) and mastodon.social and/or some sort of client side system, if that's even possible. You don't want sketchy instances or spammers to be able to poll all of a user's accounts across Fedi services.

    I am assuming this is a client-side issue and it cannot be solved at the protocol level (ActivityPub), but in a way this makes it easier to experiment as Fedi clients can try out things without modifying the ActivityPub protocol.

    Just wanted to share my thoughts. If one wants Fedi to become a viable alternative to corrupt American monopolists, then you must look at the UX from perspective and expectations of a median user.

    How the links act is different from client to client. If you click the link in the Lemmy web UI, it will take you directly to Lemmy.wtf, but if you used Voyager (iOS client), it will automatically redirect to your own instance.

    This is something that should be built into the Lemmy web UI.

    You can also use browser addons. I have an addon that redirects me to my own instance, if I click on a link in my browser. I also have an addon that takes me from YouTube to Peertube, if the video also exist in PeerTube or if I click a PeerTube link, it takes me to my instance.

    Also how dare you criticise the awesome TLD .wtf, which is clearly an abbreviation of “What The Fediverse”?!

  • I recently asked for some PeerTube recommendation and it made me realize how disjointed the URL system can seem to the median, not technically-inclined, not-motivated, user.

    The first user UX issue was the link to the lemmy.wtf post. You get transported to the lemmy.wtf webUI client, so you're not logged in and the interface is different (arguably a median user would expect to view the post via their own instance/platform, piefed.social in my case).

    But then we have the issue of PeerTube channel links in the lemmy.wtf post. I wanted to check out the Open Source_gaming channel which is referenced via the following URL:

    https://peertube.wtf/c/opensource_gaming@video.hardlimit.com

    My peertube instance/WebUI client is Spectra Video, so again you encounter another UX issue.

    To add to that, if you paste the URL verbatim (major UX issue in of itself for the median user) into the Specra Video webUI, you won't actually find the opensource_gaming channel:

    sBbwbw4pYXH7WAM.jpg

    fT7HgiPVgHP6GZc.jpg

    You would need to use the following search prompt in the Spectra Video webUI:

    opensource_gaming@video.hardlimit.com

    The upcoming version of Piefed actually addresses this issue on the Threadi side.

    For logged in users, Piefed 1.4 will turn the following URL:

    https://lemmy.world/post/39832275

    into

    https://piefed.social/c/news/p/1544770/national-parks-ordered-to-check-gift-shops-for-dei-type-items

    This issue is unresolved in Lemmy, but the Lemmy brand is permanently tainted among users who are looking for alternatives to American oligarchic technology services. The low moral standards of the Lemmy devs' (support for the brutal North Korean regime, promotion of russian propaganda narratives that they know are false) is a massive turn off for the exact target market of the Fediverse. It's a fact that many Europeans looking for alternatives instinctively recognize the demagoguery of the Lemmy devs and their fans.

    But even with Piefed 1.4, the PeerTube linking UX (same for Mastodon and I am assuming Pixelfed, Loops and other Fedi services) is a nightmare for the median user.

    What would be helpful is to have a system where the first time a user encounters a Fedi link, they would be prompted to select their instance for a given Fedi service.

    So clicking on a peertube.wtf (terrible name if their goal is to go beyond a "niche within a niche" userbase) for the first time when logged in would give you a notice similar to:

    Enjoy a user focused video platform! Sign up | Login into Peertube

    There are clearly some UX issues with this, but I still think it would be better than the current system.

    Would would be even better is if some of the major Fedi instances in a given service could somehow automate the discovery of existing user accounts for other Fedi services.

    This would either need to be done in a whitelist only manner (i.e. discovery only works between say piefed.social (or piefed.world) and mastodon.social and/or some sort of client side system, if that's even possible. You don't want sketchy instances or spammers to be able to poll all of a user's accounts across Fedi services.

    I am assuming this is a client-side issue and it cannot be solved at the protocol level (ActivityPub), but in a way this makes it easier to experiment as Fedi clients can try out things without modifying the ActivityPub protocol.

    Just wanted to share my thoughts. If one wants Fedi to become a viable alternative to corrupt American monopolists, then you must look at the UX from perspective and expectations of a median user.

    @rekall_incorporated@piefed.social said in [Fediverse wide cross-instance / cross-platform link substitution [UX improvement thoughts]](/post/https%3A%2F%2Fpiefed.social%2Fc%2Ffediverse%2Fp%2F1568622%2Ffediverse-wide-cross-instance-cross-platform-link-substitution-ux-improvement-thoughts):
    > This issue is unresolved in Lemmy, but the Lemmy brand is permanently tainted among users who are looking for alternatives to American oligarchic technology services. The low moral standards of the Lemmy devs' (support for the brutal North Korean regime, promotion of russian propaganda narratives that they know are false) is a massive turn off for the exact target market of the Fediverse. It's a fact that many Europeans looking for alternatives instinctively recognize the demagoguery of the Lemmy devs and their fans.

    I don't think this is true at all.

    The average user doesn't know what Lemmy is, let alone the political views of their core development team.

    But don't worry, it's like that joke about vegans:

    How do you know the Lemmy devs are politically dubious? Don't worry, someone on the threadiverse will tell you.

  • Not sure if you're already aware, but that relative link there is broken in Lemmy, Mbin, and Piefed.

    If you used it manually, I'd suggest not using relative links in posts targeted at users from software that hasn't implemented them yet.

    If it's some automated feature, I don't think it should be in the source property of the federated JSON in the first place.

  • Not sure if you're already aware, but that relative link there is broken in Lemmy, Mbin, and Piefed.

    If you used it manually, I'd suggest not using relative links in posts targeted at users from software that hasn't implemented them yet.

    If it's some automated feature, I don't think it should be in the source property of the federated JSON in the first place.

    > If it's some automated feature, I don't think it should be in the source property of the federated JSON in the first place.

    Thanks, it's this.

    Edit: oh interesting, I looked into it. We serve the absolute URL in HTML but not in markdown. I had no idea threadiverse apps read the markdown. Neat!


Gli ultimi otto messaggi ricevuti dalla Federazione
Post suggeriti
  • 0 Votes
    1 Posts
    9 Views
    A big thank you to those who contributed to making this release, translating, writing documentation, providing emotional support and promoting PieFed! None of this would happen without you all. New hotness Pronouns - when you put pronouns into Extra Fields on your profile that is used as a flair in all communities where you haven't set a flair yet Private communities - no federation, only certain roles (depends on the community) can invite new people. Posts inside are only visible to members. Mastodon can now quote-boost PieFed posts Plain http web UI (no SSL required) with SSL used during federation - see http://retro.piefed.com Downvotes can be turned off completely in a community, not just instance-wide Admins can sticky a post on the home page, not just mods in their communities Auto-delete of replies on remote instances when reply author has been blocked by parent content author (only works in PieFed communities due to a ActivityPub limitation) On home page when showing number of replies a post has, calculate the sum of the replies on all cross-posts and display that New users can only do 3 posts in their first 24h, to reduce floods of posts by that guy who keeps deleting his accounts and making new ones More good stuff Improve emoji federation compatibility Change order of emoji in picker to present most-used ones first Daily time limit on usage to help people use PieFed less (released in 1.5.2) A way to report posts that need to be tagged as AI generated Better accessibility Improved handling of bold and italics in markdown parsing Don't accept votes from people the author has blocked Admins can resend email address verification email Admins can add notes to instances to keep track of defederation reasons, etc Search form has been simplified Option for admins to disable the em-dash detector Multiple minor bugfixes and security enhancements To upgrade from 1.5.x git pull git checkout v1.6.x At this point you might see an error message about a merge conflict with compose.yaml. To preserve your custom compose.yaml you will need to copy it somewhere else, then git checkout compose.yaml then git pull again. This time the pull will succeed so after that copy your custom compose.yaml it back, overwriting the one from git. Then, ./deploy.sh or ./deploy-docker.sh If you had to do the compose.yaml fix up earlier then you might want to compare what you have with https://codeberg.org/rimu/pyfedi/src/branch/main/compose.yaml and manually copy and paste some improvements in particular the command: part of the db container which tunes postgresql for performance. Adjust the numbers for your system. This time the database migrations will not take long. Donations PieFed is free and open-source software while operating without any advertising, monetization, or reliance on venture capital. Your donations are vital in supporting the PieFed development effort, allowing us to expand and enhance PieFed with new features. Donations can be made via Patreon, Liberapay or Ko-fi.
  • 0 Votes
    78 Posts
    82 Views
    Oh so it is, I wasn't seeing it yesterday when I checked. Perhaps unpinning and re-pinning, or removing and re-allowing the ability to show on popular fixed it and I didn't notice it. Nonetheless, thank you for all the help!
  • 0 Votes
    13 Posts
    25 Views
    @trwnh@mastodon.social that's ridiculous. Why does every other AP service have to create activity handlers just to get a baseline permissive behaviour? I understand the consent respecting aspect, but if the behaviour is "allow all", it should be as simple as a flag. Too bad I didn't pay enough attention to the FEP draft. @silverpill@mitra.social @liaizon@social.wake.st
  • 0 Votes
    13 Posts
    46 Views
    @julian no, mastodon doesn't use salmon anymore, not since a long time ago. they switched to websub then activitypub direct delivery.on the indieweb side, salmention is an extension to webmention, where upon receiving a webmention where someone replied to you, you add that reply to your html then send a webmention up the reply chain to whoever you replied to, and they will fetch your html and find the new downstream reply, add it to *their* html, send a webmention upstream, and so on.