It was founded without Aaron Swartz. He was brought in later as part of a YC merger. Next you’re going to say that Elon Musk was a Tesla founder.

Currency transaction reports and suspicious transaction reports, do they not sound like something the Stasi would demand in communist East Germany?

No. Not in the slightest. They’re a response to crimes of capitalism committed by capitalists governed by capitalists. If making sure everyone gets equity means people moving about 20% of the median American yearly salary have to be transparent, I’m okay with that.

I see where you’re going! There are a class of people like me that always overpack to prevent that from happening. If I got lost in the wilderness I would certainly eventually run out. The amount of reading material I put in my backpack is way more than I would hit in a given time out with my backpack.

I just employed the same tactic you did. It seems you didn’t appreciate that. Perhaps your original tack wasn’t the right one to make your point?

Before phones I used to carry a book or a notebook with a couple of problems I was working on. Would you also ban those to force me into boredom?

So you’re suggesting people are only allowed to use the optimal method for everything?

Personally I’m not attempting to deeply study Lemmy in the three minutes I’m sitting in a reception area but YMMV.

From a conspiracy standpoint, so what?

• Numbers for the console that tracks these things go up, making the security features trend higher internally. Net win for user security.
• Total logins goes up. This is a meaningless metric that doesn’t affect value to anyone but the most ignorant shareholder. Nothing changes for Twitter.
• Links clicked through Twitter’s tracker goes up. Since the target and originator is a single user, this increases nothing. From a shareholder perspective, again, a worthless metric.
• Twitter gains session data. Unless the user deletes Twitter while logging in, this is an intentional choice by the user to use the platform and give that data. Possible win for Twitter but it’s a win the user agreed to because their data is the product.

“Numbers go up” doesn’t really work here. Fidelity isn’t going to upgrade Twitter’s value from any of this. Even if we assume it’s a drummed up attempt, it gains Twitter nothing we don’t agree to give Twitter by using the platform.

Speaking as a security professional, this is pretty standard practice for a solid user experience. I’m rather surprised someone in a privacy community would take umbrage at this because security and privacy are closely linked. When someone attempts to steal your account, do you not want an alert?

The easiest way to get rid of this email is to delete your Twitter account.

It’s also offered as part of the installation process at least for Ubuntu server. If you don’t know better it bites you real quick.

The issue here is that Canonical pushed the snap install without warning about its reduced functionality. I don’t think highlighting a wildly different experience between a snap install and the Docker experience people are used to from the standard package install is “bashing it just because it’s popular to hate on snap.” For example, if you take a fresh Ubuntu server 22 install and use the snap package, not realizing that snaps have serious limitations which are not explicitly called out when the snap is offered in the installation process, you’re going to be confused unless you already have that knowledge. It also very helpfully masks everything so debugging is incredibly difficult if you are not already aware of the snap limitations.

This is really dependent on whether or not you want to interact with mounted volumes. In a production setting, containers are ephemeral and should essentially never be touched. Data is abstracted into stores like a database or object storage. If you’re interacting with mounted volumes, it’s usually through a different layer of abstraction like Kibana reading Elastic indices. In a self-hosted setting, you might be sidestepping dependency hell on a local system by containerizing. Data is often tightly coupled to the local filesystem. It is much easier to match the container user to the desired local user to avoid constant sudo calls.

I had to check the community before responding. Since we’re talking self-hosted, your advice is largely overkill.

Do I use an aliasing service that allows me to change the account emails point to? Yes. Can I access those accounts with access to my email? Yes.

The issue here is that if you lose access to social network that logs you into those things, you lose the account. If you have an actual account, not delegated access, you can still access the account with the social account.

I’m struggling to find some good article examples because Google is rolling out inactive account deletion and that’s polluting my search results. So go test this out yourself: go try to change the account name/email, password, or MFA for any of those accounts you use social auth for. Try figure out how you would log into without that social account. Next do the same thing with an account you don’t use social auth for.

The biggest reason not to use a single account like this is that you lose everything if you lose the owning account. It’s bad advice to say you should absolutely do one or the other. It’s good advice to consider the risks.