we could also talk about the technical aspects of the nazi gas chambers, but maybe its only human if first we condemn this for what it is, a war crime. i for one am sick of the normalization of it
this. the uis for different apps have different needs - ex. keeping a video editor wide and narrow. and its not uncommon to want more apps open than would fit into their own tiles or having to move to another desktop workspace. i just wish there was a compositor or window manager for wayland that supported working this way, none really do. without a tiling wm, apps in gnome want to open right in the center of the screen, and don't remember their positions, its comically bad
mozilla used to have this smart guy, brendan something, as their cto. but he was chased out of mozilla and created a new browser called brave. it actually does what this current cto claims to be trying to do
got it, thanks. indeed looking again at the whois record, the registrant info is redacted, and the make offer link takes me to domain agents.
so i may have jumped to a conclusion here, but ultimately though my question remains: i searched a domain on namecheap, it was available, and then suddenly it is taken a couple days later. the domain itself appears unused and for auction, and the registrar is also, conveniently, namecheap. so if namecheap isn't the actual registrant holding it for ransom, are searches shared or sold to third parties looking for potentially valuable domains? whatever happened it's hugely suspect - so the net effect is that im hesitant to search with or use namecheap again for my next domain without some insight here
maybe i wasnt clear - its listed for sale by name cheap. i am open to other explanations, but im just sharing my experience of what happened. the whois record shows name cheap as the owner. thats the "basis" for my point here. why would they do it? well read about what happened with icann, lots has been written about the incentives and state of affairs today. if you could link to some policy that states this practise is not done (like how some companies privacy policy calls out if they sell your data or not), that would be great, but otherwise baseless comments like this are not helpful
thanks, will dm you. do you explicitly state its a practice you do not engage in anywhere other than the comments here? if so it would greatly help folks like myself if it was an error of some kind. the whois record showed it registered after my search, so i dont think a misreporting makes sense. if its a mistake that would be cool, obviously incredibly suspect which led me to read up on it and i found similar stories from others
how does a rainbow table crack "dog" with the salt "109231oijoasdfnaisdfabatteryhorse123"?
rainbow tables are as old as time and indeed still work on passwords with poor salting. for more complex (but not complex enough) passwords there are more modern approaches, like probabilistic candidate generation
i meant others commonly assume horseloverwhatever is more secure.
to be more clear,
1. dog is weak
2. horseloverwhatever is weak
3. 8randoms! is weak
4. therefore, dog is as good as horseloverwhatever or 8randoms!
5. most account compromises do not even require a brute force (shoddy practices on the backend) making the complexity requirements pointlessly burdensome on the user
6. in cases where you want a password to resist a legitimate brute force, we need to talk about passphrases (ie > 50 chars) or passwordless
i agree. but most sites that enforce a policy (8 chars, symbols, etc) are bruted just as easily. we need to take a step, away from passwords, to secure against brute force in 2022
if its that "dog" is a weak password, i thought that was evident. but many people seem confused that "horseloverwhatever" is more secure, similarly that "dog23!Wog" is more secure. my point is they are equally trash so leave the user alone
yep, most of the discussion about passwords completely miss the point. a random word, like "dog" or "pingpong" is fine if the pqsswords are salted and hashed appropriately. how often have your accounts been hacked this way? if an adversary is really banging on the hash, and they want it, any password under around 50 characters is as good as "dog", and no "complexity" meter is gona cut it. that xkcd comic that says 550 years? no, that password its owned a lot a faster than that. all this talk of entropy and security but so obviously clueless about modern brute force techniques
but this doesnt really explain what makes gpl superior to mit. in my experience, gpl is expensive, and i have seen plenty of fair contribution, ownership, and community making things better with mit. what i was trying to say was that code published in the open will inevitably be abused by humans and machines alike. the difference between gpl and mit, in my view, is that more permissive licenses are less at odds with this reality. with copyleft there will always be lawsuits
so? the gist of the mit license is, "use without restriction". without the license the default is that you have no right to the work, so the license is what makes it a gift. you're welcome
ive come to think that if you open source your code, u should only use MIT. ie. make it a gift. because once your code is just out there in the open, you cant pretend you still control it. suddenly you're dependent upon lawyers. thats icky. i mean anyone could be using this guy's code to do something against the license, and dude would never know. well, if you give a shit, maybe don't leave your code sitting in the open on a microsoft server? either set it free, or don't.