- 23 Posts
- 3 Comments
debanqued@beehaw.orgOPto
Self Hosted•📧 Email self hosters can use the GDPR fight big mail hosters who block youEnglish
1·5 months agoIt means that for more than 30 days, you’ll be unable to send or receive emails that have to do with that email provider.
I’m not sure how you arrive at that. Whether you file a GDPR Art.77 complaint is independent of how you ultimately decide to reach the other party.
This is not what I would do but this is what most activists would do:
- Use a residential dynamic IP address to attempt to send an email to a recipient whose data processor (email provider) is Microsoft.
- Keep the logs of the MS server refusing you.
- File an Art.77 GDPR complaint against MS.
- In parallel, use a different webmail account to email your correspondent. Ideally wait a week or two after filing the GDPR complaint.
The fact that your webmail provider can reach MS does not obviate your Art.77 complaint.
Personally, I have indeed quit sending email. When I need to reach an MS recipient, I use fax or snail mail and I do not give them an email address, thus forcing them to respond by snail mail. Most people will not elevate ethics above convenience like that, but to each his own.
but not being able to receive them gets really problematic.
That’s a separate matter and it depends on what email address you supply. You can attempt to send from your own server using any email address you want, even an @gmail.com address if that’s your thing. The email address you share with the other party need not be one that associates to your mail server.
I personally do not even share an email address with MS users, so those users can only reach me by postal mail. But of course this move requires a higher level of discipline on your part.
debanqued@beehaw.orgOPto
Self Hosted•📧 Email self hosters can use the GDPR fight big mail hosters who block youEnglish
1·7 months agoFighting for your rights… with gdpr, yeah, I’m sometimes doing it, but the problem is, sometimes tcompanies fail to respond … and if they take 30 days… or longer to give a response you’re really at a huge loss
Not sure what you mean by being at a huge loss. Filing a GDPR complaint is gratis, by law. It’s indeed typical that data controllers ignore complaints. After 30 days of ignoring your request, you have a sound case for an art.77 complaint. The DPA will also likely do nothing, but you’re not at a loss for complaining. If the DPA decides to simply contact the data controller, they will dance. The case will still go nowhere, but the data controller will respond to the DPAs inquiry, if they make one.



I’m surprised no one mentioned emacs. I’ve not done much with version control lately but back when I was coding at a day job, emacs was king. All the important version control functions are mapped to key bindings and macros.
Emacs functions graphically with a mouse for novices, which makes it good for starting off. Then as you get more advanced you memorise bindings for frequent functions so the mouse slows you down less and less. The default keybindings in emacs have become ubiquitous so e.g. many of the emacs bindings work in BASH and other apps. So when you learn emacs, your knowledge becomes portable outside of emacs.
A lot of the same can be said for vi variants. But that’s mostly it. Editors other than emacs and vi are isolated and less powerful – though I’ve not really looked hard outside of emacs lately so things may have changed.