Kierunkowy74

Blorp is one of these. and Photon plans to support PieFed in the future.

a Lemmy (and now PieFed too) client

All of these will blend with each other and all these vertical shorts. Linear TV is already legacy technology, which does not allow targeted advertising, etc..

And of course GenAI everywhere because it's cheaper.

The distribution format based on single app files is actually called AppImage. Flatpaks still need to download several libraries.

You would love kbin.social.

It combined posts from Lemmy and Mastodon, allowing to browse and sort both of these like on Reddit. Mastodon toots were matched to respective magazines (like Lemmy/Piefed communities) based on their hashtags. And multireddit-like feature (called Collections there, and recently reimplemented in federated form by PieFed as Feeds) allowed any user to combine several magazines, Lemmy communities and Guppe groups in a single view.

All of these has been inherited by Mbin (a /kbin fork), outside of Collections/Feeds.

Largest instances are https://fedia.io/ and https://kbin.earth/. There are much smaller, than flagship /kbin instance have been, though, so both will be aware of less posts...

OP wants to sort posts by popularity and unfortunately Mastodon does not allow that :( Trending posts exist but only instance-wide

Brutalinks (HN/Lobsters clone, one-community per instance), lotide (minimalist, RIP), Prismo (RIP)

This probably won't help you, but there was Flockingbird. However its attempt to index Mastodon's job offers ended up in drama as Mastodon generally does not like being indexed...

Just use Mastodon.

relevant meme

You probably want to use another Lemmy instance to search for this content.

(and actually Sepia Search is simply a search engine for PeerTube and that's it. You are still getting the video only after you visit the instance...)

Updated, thanks!

I blame this on an UX blunder.

Bluesky users are taught not to enter their Bluesky passwords to enter different apps, but rather create a different "app password" for each one. Then Frontpage went OAuth which directs users to Bluesky login page. Bluesky brings us a different login page for OAuth use :/ and obviously does not remember that we are already logged in in the same browser.

This of course means that we have to enter a Bluesky password to a slightly different-looking website - a somewhat fishy way to authenticate a user...