What a smarmy cunt, doing this "do you know who I am" spiel. They might know who you are, but that doesn't mean shit and you don't matter either, because you left the company. Your co-founder feels differently on this issue as well, having an entire browser built on the base of ad blocking and crypto.
And because the rare earth minerals in that brand new iPhone they buy every year are obtained both by slave labor and by absolutely annihilating the environment.
There's also a shitton of energy pissed away using humans to handle our financial infrastructure right now. All those bankers hanging out in skyscrapers in Manhattan need to be kept chilly in the middle of the summer and all that gold and paper that needs to be trucked around by armed guards.
Not to mention the ridiculous amount of resources invested in getting a .00000000000001 second faster transaction in high frequency trading.
I swear the only reason this troon considers MikroTik to not be a "real router" is because MikroTik is a Latvian company, and that's like near Russia so it's basically Russia and they murder trans people, while Cisco routers are from California and they personally suck the tranny dick so only Cisco routers are real routers. That and maybe because it has the same mental attitude that the more you pay for something the better it is. Cisco routers are much more expensive than MikroTik routers, even though MikroTik routers can do about as much as Cisco ones.
They might not have even thought about that, just the usual tranny 'but but it's not BRAND' thinking. Simping for Cisco. Sad!
)
According to the official MikroTik statement, the botnet attack was due to a security hole in WinBox from 2018 that was quickly patched, but barely anyone bothered to change their password or even update RouterOS after that, or even check if something was wrong. So you cannot place all blame on MikroTik for that, it's mainly because of the sysadmins who are too lazy to update their shit and periodically change their passwords.They might not have even thought about that, just the usual tranny 'but but it's not BRAND' thinking. Simping for Cisco. Sad!
Also Mikrotik is pretty notorious in security circles for being botnettable, but that is (mostly) down to retards implementing it and not changing the default password.
(we had a great time at work recently where a security researcher called Mikrotik 'Romanian or something' and there was a Latvian in the room
Yeah. I knew there was -a- bug in winbox. Our researcher feels there's two 'groups' of compromised hosts, the other being ones who literally have never changed off default passwords, which is fully on the admins.
Heh, reminds me of how when I got my MikroTik for home usage and opened up the console I noticed a whole bunch of random IP addresses trying to get into the router with default credentials and no passwords, since I'm opened up on BitTorrent. I even added firewall rules to automatically block these people, but I think after I added some other rules to block anyone not from a local network or something it no longer finds any brute force attackers. Basically I have no idea what I'm doing in WinBox and I did something that blocked the attackers but I don't know what it was exactly.
A company that uses phpBB for official tech support and announcements?!
Get ready to do router configuration on hard mode then. But it's worth for what it can do. It's essentially server-grade router software that's also available on simpler home routers.
Watch out which JS dev you call a weak soyboy, fellow Kiwis. Or you just might end up with a small but heavy package sitting on your office desk.
"Wtf coding for free and licensing under a permissive license means other people get to use my code for free?! Fuck that I quit."
That's really the best part of the regularly scheduled NPM drama. Everyone involved deserves what he gets, and they never learn from it either so it's infinitely repeatable.
He should have left the package as-is, but relicensed it under AGPL. Watching FAANG legal depts scramble as a bunch of their products because infected would have been more entertaining than his bizarre schizo-activism (schizotism?)
Why do the boring thing when you can use a corpo license for years, let them become dependent, and then pull out the rug from under them?
Wouldn't that only apply to future versions and not retroactively?
A lot of these companies didn't have the version pinned so install defaults to the latest automatically. Google is especially anal about not allowing AGPL software even in dev setups so it could've been entertaining.
The company would just fork your project, which costs it very little - especially if the company is FAANG and your project is a terminal output colorizer. Even if they don't notice the license change and end up violating the new license, this has happened before and accomplished approximately nothing outside of a bit of social media noise. Laws are for the plebs, sadly.
Rust did, they've reimplemented it with cargo, and the culture again is to use a mile deep tree of tiny crates of which you personally picked only 3-4 of.
