It says in the article they employed a commercial data set that is not composed of widely available public data in creating this app. Also, it lists a lot more information about people than whether or not they are christians.

I made an extremely half-hearted attempt at it at some point, but couldn’t immediately find any cli commands to toggle that option so I gave up pretty quickly.

Yeah this is really annoying for me as well. I found that if you go into the system tray and click on ‘power management’ and then tick the box for ‘manually block sleep and screen locking’ it’ll solve the issue. Unfortunately it means that your display won’t go dark when the system is idle, so I have to remember to untick that box after I’m done gaming in order to keep that behaviour.

You’re making the assumption that Meta will give a single shit about the GNU license at all. Does the fediverse have the means to fight one of the largest companies on the planet in court?

Then we shouldn’t even be considering our federation until they are willing to properly join the community.

Except that Threads is not going to engage mutually so this argument is moot. If we federate with Threads but they do not federate with us, what exactly to we have to gain from this besides Meta’s rage algorithms?

My objection with federating with Threads has nothing to do with privacy or data access, it has to do with keeping the ActivityPub protocol alive. Embrace, extend, extinguish is a much more legitimate threat to the fediverse than data scraping ever will be. No, the danger is that Meta will begin to contribute to the protocol. At first, contribution by a corporate actor would seem like a fantastic boon to an open standard that we wish to see grow, that’s the embrace phase. But it would not be long before Meta began adding features that are exclusive to a Threads user - they’ll extend the protocol to better accomplish their ends. In this way, they seek to bring more and more users into their platform in order to take advantage of these exclusive features while maintaining compatibility with the larger Fediverse. The end goal is to have enough users that when they decide to break that compatibility, they will make off with the majority of the users from the open community; that’s the extinguish part.

This is a well-established strategy that large tech companies have employed with open standards in the past (see XMPP). I strongly believe it is in the Fediverse’s long term interests to remain defederated from Threads, and any other large corporate player. Better to have fewer users and grow organically than to federate with Meta; we may see a short term boost to the fediverse, but the long term risks outweigh any benefit.

That being said, the nice thing about the fediverse is that I can just leave this instance for another if I disagree with the admin’s decisions.

I also returned totally accurate results using the exact same query. I would really like to know what is going on here. This is a common complaint with some people using DDG, that the results are poor, but I consistently have as good if not better results than using Google.

Unironically, the terminal.

As much as I want this to be true, it’s simply patently false.

It certainly has it’s ups and downs. It’s nice having smaller communities as it really helps having more congenial conversations, but I do miss the larger user base sometimes, since it ensures more coverage of a given topic.