Live data from Hacker News

Ask HN: Should we own the free stuff we pay for?

news.ycombinator.com

21–30 of 309 posts

Re: Ask HN: Should we own the free stuff we pay for?

#23

> free stuff we pay for Did you actually pay for it? With money? Or was it free?

Either you think "paying with your data" is a valid argument, or you don't (but then the service needs to be free even without agreeing to the data stuff). Google can't have it both ways.

Re: Ask HN: Should we own the free stuff we pay for?

#24

Buy a domain (I bought lastname.contact) and subscribe to Fastmail or a similar paid-for service. You can then use anything@lastname.contact and if your email service provider drops you, you can switch to another and not care about your contacts trying to reach you or updating the email address of all your online accounts. I couldn't be happier with the switch (I was using Protonmail before, and Gmail a long time ago…

By doing this you are trusting the .contact gTLD provider. Do you have idea how reliable are they? Would they reclaim your domain for some reason?

Re: Ask HN: Should we own the free stuff we pay for?

#25
> what is an identity?

PGP is a good solution, and in general the crypto space has the right idea in my opinion. I like the idea of using cryptographic key pairs to sign messages and prove identity, but the learning curve makes it impractical for general use.

The best place to start is owning a domain you control, at least that way you can manage your own facade.

Re: Ask HN: Should we own the free stuff we pay for?

#26
One thing to consider is the possibility of using multiple separate e-mail accounts from different providers.

Currently i have about 10 different e-mail accounts:

  - one for development related things and communities
  - one for newsletters, various online platforms and so on
  - one for throwaway purposes, lower importance things like video game accounts
  - one for university related things (it stayed after graduation)
  - a few separate accounts (and corresponding Google account) for various phones or other devices, as necessary
  - some standby accounts if i ever need them, some from different providers to check mail denylisting
  - a personal address that's mostly for contacts through my website or my self-hosted automation messages
There are some others, as well as each platform for automation has a separate account as well (e.g. GitLab, Zabbix, Nextcloud, ...), though most of those are on the same self-hosted mail server. Of course, deciding how to structure everything is one's own choice, in my case it's just historical cruft and loosely defined boundaries of how much i care about any particular item.

That said, mail servers that are easy to set up are a godsend (for example: https://github.com/docker-mailserver/docker-mailserver), as long as you also have one of the larger walled garden alternatives for public communications, should there ever be delivery problems.

It's not like Google deciding to ban all of my accounts at once (though fingerprinting, or based on IP because i don't care to set up some sort of an advanced proxy to access all of them from different VPNs) wouldn't be problematic, but this way at least the impact would be minimized.

Plus, with software like Thunderbird and something like KeePass for strong randomly generated passwords, managing everything is really low effort. Of course, this also lends itself nicely to avoiding social logins and creating a separate e-mail based account wherever applicable, for a bit more control, rather than keeping all of your eggs in the same basket.

As for those who will inevitably say that this is too hard or complicated to be practical: i invite you to try setting up your own mail server with the help of the provided link on a 5$/month VPS, things have really improved in the last few years! Of course, creating new Google accounts (or for other platforms) might be a bit more cumbersome with modern verification steps etc., but it's not like it's impossible either.

Sometimes i wish we could do the same for personal identities, e.g. a list of aliases that could be issued through some government org. for particular purposes and revoked as necessary. For example, i wouldn't want a leak of some shopping site result in my personal data being compromised in regards to my online banking or my physical address, in any capacity whatsoever.

Re: Ask HN: Should we own the free stuff we pay for?

#28
post #2

No, you're not overreacting since it happened to you. On the other side, you are also overreacting. Take a walk. This being said, since you got a scare, maybe it's a good time you buy a 2nd domain from another registar and handle accordingly. PS: how does one find a good domain name?

> PS: how does one find a good domain name? brute force checking thousands of examples till you find one that isn't squatted.

Also, if you're planning to use it as your primary email domain - pick a "normal" TLD. Using something like .email/.xyz/.live etc can end up in spam (especially for newer domains).

Re: Ask HN: Should we own the free stuff we pay for?

#29

> free stuff we pay for Did you actually pay for it? With money? Or was it free?

The post mentions a few subscription services, Google One being one of them. That gives extra storage in Gmail and access to Google support. By then I would definitely say that you are a paying customer.

Re: Ask HN: Should we own the free stuff we pay for?

#30
When you put it this way, it's really quite remarkable how tenuous our hold is on even paid for digital services.

There is really nothing you could do with a car to prompt the car maker to take it from you. And the state will only take it if you break the law in particularly dangerous ways.

When it comes to other possessions it's even harder for anyone to take them away from you. If I take a kitchen knife and stab someone with it I will go to prison for sure, but I don't think they will take the knife away. They definitely won't ban me from buying knives.

But when it's a digital service, even something as crucial as a banking service, it's seen as normal that you can lose them for posting offensive things on twitter. Perhaps it's because we haven't had these digital services for long enough to consider them as really belonging to us, so we accept that they can be taken away at the slightest provocation.

Post reply on HN