Is privilege a driver of #privacy invasion? We think so.
With that said, desperation can be a factor. Not everyone that invades our privacy is doing so maliciously. Sometimes, their business is struggling to survive, and the idea that "we can stay afloat" if we learn everything about our customers seems like a no-brainer.
Marketeers tout this as the only way to win, and those desperate to stay in business fall prey to that philosophy.
It's as much on "us" to create new & ethical ways to win.
Of course, coronaviruses existed long before SARS-CoV-2. 😃
The point here is to say they have been really forward-looking by reserving a domain name for such a generic term.
notovirus.com, rotavirus.com, adenovirus.com… have also been existing for more than 10 years. Maybe one of them will become a familiar term one day.
coronavirus.com redirects to a page by the WHO. Fine!
According to WHOIS, the domain name was created… back in 2002.
Domain Name: CORONAVIRUS.COM
Registrar URL: uniregistry.com
Creation Date: 2002-08-13-T02:31:44Z
Got this on one of my domains:
From: <complicated address with @gwart.xyz>
This email is a harmless security check to your email system. It does not attempt to penetrate or circumvent your security measures.
To opt-out of these security checks please visit the opt-out link.
<link with a token ID containing my domain>
I suspect they want to see whether the mailbox is monitored, in case I would open their link.
What is the trick here exactly?
If everything is fine with this RC, you can expect the final 0.21 release by the end of the week 🎉
Failed exploit against our Mastodon server. SQL injection attempt, obviously.
@tux They seem to be interested in you. 😉
Why are we flooding your feed today? Because we feel we are entering into a perfect storm of privacy issues.
We believe that engaging in and out of our personal networks can help us correct course.
1. We have an unprecedented attack on #encryption, in the US with the EARN-IT act, and beyond.
2. Pervasive widespread person-tracking is being embraced by governments and the public, often unwittingly.
3. Fear may prompt the public to cling to ideologies that are injurious to #privacy.
The mobile app for #Jitsi Meet has been updated to 20.1 this week.
They fixed an annoying bug in the settings dialog. Entering a custom URL for the server was a real pain. Now it’s quite easy.
This is very good news. There are lots of Jitsi Meet instances around, and this setting is really useful. (And I had some friends about to give up only because of that poor usability problem.)
Some people might say: "I want a restrictive #licence to the software I’m writing, to prevent 'bad guys'—e.g. the military, the Mafia—from using it."
Bad idea: if people are killing other people, software licences are probably not something they would really care about.
Better stick with licences that do not impose personal views about who and what purposes. (Copyleft is important, though.)
It is interesting to see how attacks are quickly mutating.
Today, hundreds of "GET /.aws/credentials" requests started popping up.
In the past hours, I have seen a large number of requests in my #nginx log.
"GET /.env HTTP/2.0" 403 146 "-" "curl/7.58.0"
Hundreds of bots looking for the file, then going away. Most addresses resolve in compute.amazonaws.com
They are very obviously trying to get a config file. Is it still that old Laravel #exploit?
Helping the Free Software Movement since 1997
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!