This one time, at band camp, I violated the GPL with my rock flute and sheet music for a crappy, post-Burton Metallica song. (it/it/its, gender true neutral)
Smash tyranny! Reimplement something only available as proprietary or copyleft software and give it the COIL.
All original text in tweets and threads licensed under the COIL. Use and abuse with abandon.
https://t.co/5vkKLqtnL3
@antranigv 1. People are even more united in hating COBOL than in hating PHP or VisualBasic.
2. People don't want diversity. They just want their choices to "win" -- even when they talk about "diversity".
I don't know how many of each profession are corrupt, but the corrupt have advantages in gaining power within their professions, because while the honest are spending their time trying to do a good job the corrupt are spending their time accumulating power.
This is what happens when "professional" standards are determined by the "professionals" instead of by the people who have to live with their "professionalism". Corrupt cosmetologists want to shut out competition. Corrupt police want to protect their buddies from justice.
In Minnesota a cosmetology license requires 1550 hours (39 weeks) of training. It takes 16 weeks (640 hours) to become a cop. So, basically oppressive ignorant people are enforcing laws.
@eneko @ninomelon @slava_pestov . . . so yeah, I was talking about HTML emails when I mentioned the actual address being hidden behind link text that says it's a "trusted" address.
@eneko @ninomelon @slava_pestov Ideally, emails should be plaintext for exactly the reason you state, but for extra care view (Latin alphabet) URLs without Unicode support so you can be sure there aren't look-alike characters to fool you.
@eneko @ninomelon @slava_pestov The URL for the link in a . . . link . . . is also (potentially) hidden. You have to look for the actual target address, and you also have to "trust" that the text of that target address isn't using Unicode look-alike characters.
Review all links by pasting into ASCII.
@eneko @ninomelon @slava_pestov The URL for the link in a . . . link . . . is also (potentially) hidden. You have to look for the actual target address, and you also have to "trust" that the text of that target address isn't using Unicode look-alike characters.
Review all links by pasting into ASCII.
There are always mitigations. Often, the mitigation involves using someone else's software. This is the real reason vendors want "responsible disclosure" as commonly defined: they don't want to lose business, but they don't want to have to work to keep it, either.
responsible disclosure:
You discover an exploit. You tell the vendor. The vendor sits on it for a month, then finally starts looking at it. God only knows when it might get "fixed".
During that time, only the vendor and the exploiters know about it. Thousands get owned.
This entire "debate" is pointless and silly.
I shred speedmetal Ruby dev (and some of what that image says about dynamic languages is true).
I also lay down some solid grooves with my static language favorites.
different != competing