So we can write Macro viruses in two languages now?
So we can write Macro viruses in two languages now?
But you went the extra mile and set up your own instance to do this, right?
Nice bio btw.
Lemmy does not support karma, but account age if I’m not mistaken. Maybe add a rule to require a certain account age before accepting a post. The main idea is to prevent astroturfing, spam accounts and socket puppets for ban evasion.
Not sure how effective this is since violators could setup an own instance which lies about the account age. Still quite the investment for ban evasion IMHO.
I would go nowhere near a drenched feline since the most common version of them is likely in a very bad mood due to being drenched.
clickops
I think I will steal this.
Ah, the horcrux technique.
A reference to the software engineer who worked 20+ years at Microsoft and then became a goose farmer. The LinkedIn post became viral.
Not an answer, but you don’t need an extension to defeat right-click blocking scripts: shift-right-click usually does the trick.
Really true. I hope “new UI” stays optional until I retire or become a potato farmer. I haven’t worked long enough at Microsoft to deserve geese.
The thing you are thinking about is called TOTP or timed one time password.
When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…
Masks don’t only protect from airborne viruses…
a match is never 100%
But but but, the CSI series catches murders with 100% matches! (Ok, they also hack in VBA)
You’re just returning their property ^^
But then the country you are in needs to recognize the country you’re a diplomat of and want those diplomats in their country. Diplomatic status is not a “I can go where I please” status. But it’s that way to sovereign citizens, I guess.
But if they are not citizen of any nation, wouldn’t that make them illegal immigrants in any country?
Review is done before code gets into main, but that’s inefficient for most of the non-mission critical projects out there. A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.
Assuming you have a project with continuous delivery, that is an absolute foot gun. Optimistically merge the change and then realize in situ that you forgot the WHERE
part of your SQL command (or analog statement of the query builder)? No fucking thanks.
Yep, it’s a repost of this one.
One could even think this OP is an alt account.
And yes, word is the word.
It seems like you are one of the twelve Americans who is unaware that the bird is the word.
I am in this post and I don’t like it.