Shamar @Shamar@social.cleverlibre.org

@Libertux@liberdon.com

At a first look, @Tutanota is impressive: apparently, you got #privacy right.

At a second look...
Shit! You got #privacy right! 😂

Even the #Android permissions are minimal! 😍

Now, let's be picky, with the sincere hope to help to further improve your product.

Two issues remain open with your services:

1. #DoS / #Censorship
2. #DDoS
3. #Business

Theoretically, you could easily deny your service to a user. So could someone who provide or otherwise control users' connectivity (a State, a ISP or simply a #corporate firewall).

Also you could theoretically be blocked through a DDoS (do you remember the #Chinese attack to #GitHub?).

Finally you could be bought by #Google, #Facebook, #Microsoft, #Alibaba or somebody else for a tons of money. Or you could be otherwise run out of business.

All of these are potential long term threats to your customers and users and share a common root: server code isn't #free.

Are you considering the option to release your server code under a #FreeSoftware license?

I'd suggest a very strong #copyleft, obviously.

This would mitigate all of these potential threats.

I understand that your server code gives you an edge... and as far as I can understand, it doesn't reduce people privacy... as long as the system stay up and reachable. 😉

Let me know your take on this.

And by the way... great work.

Really.

@leodurruti

Non mi è molto chiara l'ironia. 🤣

Puoi spiegare cosa trovi divertente?

L'articolo mi sembra buttar lì molti numeri senza spiegarli, analizzarli o confrontarli fra loro.

For a few seconds I thought #Mozilla actually cares about people's #privacy.

Then I read the last line.

https://send.firefox.com/legal

@dataKnightmare

Brian #Kernighan is going to talk at Turin during the Festival della Tecnologia.

https://www.festivaltecnologia.it/sessioni/milioni-miliardi-fantastiliardi-come-difendersi-un-mondo-pieno-di-numeri

@alexcleac@mastodon.technology

It's like with kidnapping.

If you pay the ransom, you incentivize future ones.

@gnome

@natecull

#Communion is way more requesting than #Communism!

IOW, compared to #Jesus, #Marx was far-right! 😉

Gentile Professoressa... non posso autorizzare Edmodo a profilare psicologicamente mia figlia.

http://www.tesio.it/2019/10/22/gentile-professoressa-non-posso-autorizzare-edmodo-a-profilare-psicologicamente-mia-figlia.html

#Privacy #Istruzione #Edmodo #Sorveglianza #Sicurezza #ToS

@xj9

Ehm... no.

Usually forks are backwards compatible at the instant they are forked. So people using version 3 of X will be able to use version 0 of X' if X' is a fork of X.

Even if the GPL text was on a free license (and it's not), any project adopting GPLv3+ right now could NOT migrate to the "Stubborn Public Licence" that is a fork of it.

And no code under SPL could be linked to GPLv3+ code.

That's why it's so important to consider, for people using #GPLv3+ or #AGPLv3+ or #LGPLv3+ if they still trust #FSF!

Because if not, they should move to a GPLv3-only or whatever, before GPLv4 is out.

@grainloom

@xj9

Unfortunately, a fork of GNU GPL is unlikely to count as a new version of it.

So whatever is GPLv3+ when GPLv4 will be published will become GPLv4 too.

If it states "Big international corporation can do whatever they like with this code", there's nothing you can do about it.
(but obviously it won't be stated so clearly... they will just put a couple of new holes)

@grainloom