Even though this doesn't apply to enterprise customers, I'm just waiting for European customers to wake up and realize that ChatGPT isn't compatible with the GDPR today. And if the court suddenly decides that enterprise customers should also be part of the preservation order it'll be a big hit for OpenAI.
One of the biggest Norwegian banks were used as a cover for a scam in Portugal, involving 2500 ad posters distributed by advertising company JCDecaux, with QR-codes linking to scam sites. The ad campaign cost around 5M NOK ($~0.5 USD), and the victims were tricked into signing up for various loans and investment programs, with lots of extra fees added on top.
Get rid of any unwanted noise caused by gear or environment. Add a basic EQ - I'm using a 15-band one just to compensate for the room, the speakers, hearing loss and anything else that would impact the sound.
But how many of those will send conscripts abroad to fight? Norway won't, they rely on volunteers who have at least completed conscription or proffessional soldiers. Can't imagine that any of the others does it differently.
> If you're a security practitioner, teaching yourself how to hack is also part of the "Hacking is Cool" dumb idea. Think about it for a couple of minutes: teaching yourself a bunch of exploits and how to use them means you're investing your time in learning a bunch of tools and techniques that are going to go stale as soon as everyone has patched that particular hole.
If only this was true... Injection has been on Owasp Top 10 since its inception, and is unlikely to go away anytime soon. Learning some techniques can be useful just to do quick assessments of basic attack vectors, and to really understand how you can protect yourself.
I was about to ask for the same thing. All best practices within the security domain point towards multiple layers of security, simply to have some fallback if one mechanism is compromised.
One of the first things you need to think about is the inclusion criteria.
Wikipedia bases all its content on the following: "A topic is presumed to be suitable for a stand-alone article or list when it has received significant coverage in reliable sources that are independent of the subject."
This is flexible enough to allow a lot of stuff, but also causes endless debates, discussions and complaints when content is removed. This is (in my opinion) one of the things that actually give Wikipedia value. If everything is permitted, separating spam from actual content is hopeless.
Defining a scope for your application is a must; if you gain even the slightest popularity, every self-serving developer is going to try to piggyback on you. "See, my project is listed on xyz, therefore it's famous and hence I'm a rockstar."
-Do you want to include any project hosted anywhere?
-Incomplete/unfinished projects?
-Forks?
-Do you want to limit yourself to particular licenses?
-What about ecosystems such as PyPi, Nuget, npm and all the rest? Code is mainly hosted on github, but do you want to maintain any kind of relation between source and package?
I think this could be handy, both for finding alternatives if you have an issue with a library or if you're looking for "something" that does <abc>.
