What’s the number of Threads users compared to Lemmy? If the number of Threads users greatly outweigh the number of Lemmy users, then we’d simply be drowned out by all the Threads posts. That’s part one of Embrace, Extend, Extinguish.

Extend adds functionality to Threads that Lemmy either can’t support or won’t support for a while due to development time. People migrate to Threads because Lemmy is “missing” functionality. Plus, though I’m not clear on the exact legal specifications, proprietary code can be added to open-source code, and the proprietary code would be copyrighted. In other words, Lemmy devs would have to figure out a way to interact with and mimic Threads’ proprietary code using open-source code.

Extinguish is when Threads’ support of Lemmy is eventually dropped. The users left on Lemmy have suddenly lost a huge amount of content, and they’re left with fewer users than before Threads enabled federation.

I’ve come across a few projects over the years where the ownership is transferred and it’s then loaded up with malware

See: The Great Suspender

The original developer sold the repo to a new, anonymous maintainer. The new maintainer abandoned the repo but continued updating the Chrome Web Store version of the addon. That version eventually got delisted by Google for including malware.

And I believe it’s being developed by some of the same people, too.

Chai tea

I actually don’t have a problem tying everything together. I think the fact that Mastodon and Lemmy can communicate with each other (even though it’s not really intentionally designed that way) is pretty neat.

What I do have a problem with is the corporations that are trying to do it. I don’t trust any corporation to do it responsibly, especially not Facebook.

You’ve basically got it. To use the “Google XMPP” example some others have:

XMPP users existed, and its userbase was growing (similar to Lemmy). Google made Google Talk, a desktop chat application they used to have, compatible with XMPP (which was the “ActivityPub” of chat applications) (embrace).

After a bit, Google started adding their own proprietary stuff to XMPP. (It’s similar to how Apple/ Google added proprietary stuff in their respective text message applications, like reacting to a text with an emote.) The XMPP devs, for whatever reason, couldn’t or didn’t make Google’s own proprietary Google Talk features compatible with XMPP, so XMPP users might’ve started feeling left out (extend).

After a while, Google Talk got rid of its XMPP support, and, as a result, many XMPP users could no longer communicate with many of the friends they had made on the platform. (Since Google Talk users outnumbered XMPP users, there was a very high chance that people you communicated with on there were using Google Talk.) Google Talk users, on the other hand, simply noticed maybe one or two people on their list had gone offline permanently (extinguish).

But they would still be unable to embrace (and, by extension, extend and extinguish) because users from Threads would be unable to interact with users from other instances. Basically, they’d be unable to get rid of a potential competitor using the EEE method.

Have you followed the instructions in the devs’ Reddit thread? (At the bottom of the thread, they also have a section of instructions for people who’ve already gone through the process of purging their filters before.)

Also, make sure nothing else (ex. another adblocker, including your browser’s built-in adblocker) is causing issues.

Same here. I tried loading the same 13-second video on Piped and YouTube. YouTube played it instantly. Piped took several seconds (probably longer than the video lasted) to start playing.

You’re linking to one instance where it partially fixed the issue amidst a sea of people saying updating filters did work for them (or saying that they didn’t have to do anything at all).

Or just use uBlock Origin? It blocks YouTube’s ads (and their adblocker-blockers) right out of the gate. It’s also available on Firefox for Android.

Looks like you may be right. Most requests came from api.twitter.com (and variations of that, such as api-33-0-0.twitter.com). The only different one was from global.albtls.t.co, and it was already blocked thanks to Peter Lowe’s Blocklist.

Any idea how to block ads in the Twitter Android app? Or, rather, which sites to block? I’m using AdGuard to block ads on all apps, but it doesn’t seem to affect the Twitter app. Either the Twitter app runs ads differently or the ads aren’t part of any of the blocklists.

Because there’s no viable replacement.

Before you or someone else mentions Mastodon (and probably compare it to the Reddit migration to Lemmy; I’ve been through this conversation before): Both Twitter and Mastodon are built on the concept of following people. If those people don’t migrate to another platform, then the people following them won’t migrate, either.

But Reddit and Lemmy are built on the concept of following ideas. It doesn’t matter if one person who, for example, enjoys anime, only stays on Reddit. Others who who enjoy anime may move to Lemmy and become part of one or more of the anime communities on Lemmy instead.

Basically, the comparison isn’t 1-to-1.

But then I’d have that terrible X logo on my phone instead of the much-less-terrible bird logo.

I have yet to update to any version of the app that uses that logo.

Mine has one. It’s part of the touchscreen. You put your finger/ thumb on that part of the screen whenever it asks for your fingerprint.

No, the instructions must be followed or it won’t work. /j

And probably the intranet, too, just to be safe.

My brain honestly just skipped over it until I saw your comment.