tesseract

@tesseract@beehaw.org

• ⁨Comment⁩ on ⁨EU Watchdog Urged To Reject Meta 'Pay For Privacy' Scheme⁩ ⁨⁨8⁩ ⁨months⁩ ago⁩:

  Imagine the scenario where you have to bribe (disguised as a subscription) each megatech company to respect your privacy. How many times and how much will you be willing to pay for something that should be your fundamental right?

  Given Meta’s history, no one should misinterpret their intentions. They should be outright banned for these egregious transgressions.

• ⁨Comment⁩ on ⁨Australian privacy watchdog refuses to investigate employer that allegedly accessed worker’s personal emails⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  These companies dig up everything from a prospective employee’s past, starting from childhood. Things that you said come back to bite you, even if you got wiser and changed your stance. But companies get to pull shit like this without consequences.

  There should be a public blacklist database with every company and their dirty infractions like these. That way, at least very competent and desirable candidates can avoid them and look for better jobs.

• ⁨Comment⁩ on ⁨Switching to more privacy friendly alternatives⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  I don’t have anything to hide

  Great! Then I guess they don’t mind giving you their bank password, credit card pin, details of all the medicines they take, information from the work they do, their detailed weekly activity schedule, their browser history, their investment portfolio and assets, etc, etc… I’m salivating at the thought of the hundreds of different ways in which I can make money with all that info!

• ⁨Comment⁩ on ⁨Using email aliases (email alias services) with self-hosted email⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  Email hosting is hard for two reasons. The first is that there are too many parts to configure - MTA, MDA, DKIM, RDNS, spam filter, webmail, etc. The viable solution is to use a turnkey solution like mailinabox, mailcow or mailu.

  The second problem is deliverability. At the minimum, you will have to ‘warm up’ the server. You will have to send a few dozen mails to others and ask them to mark as not-spam. Even then, a lot of other factors come into play - like the IP address block (for example, mails from AWS always gets blocked), domain name and even the top-level domain - they all influence the spam filter score.

  Meanwhile, deliverability with Google and Microsoft (incl google workspace and ms 365) are lost causes. Google sends your mail to the spam folder irrespective of your spamassasin score. They provide no viable solution to this. MS on the other hand just drops mail silently. This isn’t a bug. Both of them are trying to destroy the federated nature of email and consolidate all email business to themselves.

  Meanwhile, the big players like fastmail and migadu get better treatment. Especially, migadu is a good choice if you want unlimited aliases.

  Finally, talking about aliases. Most services (except migadu) offer only a few aliases. That limitation is not there for selfhosted email. An alternative to aliases is to use + addresses (eg: mybox+bank@mydomain.com). The advantage of this method is that you can make up multiple addresses on the fly (without registering) using a single alias/address. You can use this in combination with a filter like sieve (server-side) or notmuch (client-side) to sort and filter incoming mail.