You accidentally double posted this.
You accidentally double posted this.
Happening is a word my autocorrupt gets right 6% of the time.
Looks like you’ve got the upvotes backing you. I’ll keep on using as is. Thank you!
When your mission is to create a safe and private web and you squandered your organization’s money to give huge payouts to your executives for not achieving their stated goals, that’s a form of corruption. Their relationship with Google was always viewed with skeptic eyes too. There are more. Nothing people can prove, but looks suspicious. Like I said, at best incompetence.
IANAL, but AFAIK that’s incorrect. If you’re the only copyright holder, you can issue multiple licenses for your work. GPL doesn’t allow you to rescind previous issues, so anyone in possession of your GPL code can still modify and release it under the GPL freely. But it doesn’t prevent you from issuing your own work under a different license.
There isn’t usually much economic sense for most applications to do that because anyone can fork the project and distribute it for free. For Proton, since they still hold the server as closed source, they could simply introduce a breaking protocol change and all the forks would be useless.
English isn’t my first language. I share your opinion regarding the license. Which connector would you use instead of “but” to indicate that you succeeded in your efforts even though it was harder you thought it would be?
I’d argue that’s improving internet. They’re about the only ones trying to come up with an actual solution.
There’s plenty, PLENTY of other examples to criticize Mozilla on not focusing on Firefox. This isn’t one.
I love Firefox, I’ve even spent money to support it in the past. The Mozilla organization seems at best incompetent and at worst willfully corrupt. There’s no love lost here.
It took me going to their GitHub to find out, but it’s GPL 3.
I’m pulling the lever as hard as I can, I swear!
In trying to keep generic enough, they proposed concepts of a roadmap
I only trade in the finest, unadulterated, originals.
I scanned the API calls to get all the details I needed. I did my thing and I was in.
Jesus came, broke my fridge, and didn’t even leave a note. Asshole.
I remember the analog days where a few keystrokes on an Ericson phone were all you needed to start listening to private conversations on the cell tower you were connected to.
You always had the option to send frames over the net using VNC and such. But for many use cases, X over SSH was absolutely fantastic.
I remember using it on a very basic DSL connection to work remotely back in 2005, and it was almost like running local. You don’t get anywhere near the same performance with VNC or RDP.
Yeah, to send it naked over the wire would be nuts, which is why everybody uses SSH. But unless there’s insecurity within the computer, that’s a moot point.
Covfefe
How so? Is there a way for malicious code to start injecting itself into calls to 127.0.0.1?
Because who wants to do this every time they upgrade kernels, let alone once?