That's a great idea. What do you use as your family password?
HN user
ferngodfather
I had the exact same experience. Never used Facebook. Wanted to create a page for a product. Suspended. Did the face scan. Now they have my face and I'm still suspended. Absolute joke. Zuckerberg can go suck a fat one.
So much this. Everyone has their own idea of that the project should do and it's hard to explain that whilst that implementation is great for their specific use case, it's pretty shit for everyone else.
AI has just made this so much worse.
My brain is melting because I can barely keep up with learning how to figure out if I'm even doing what I'm trying to do.
This is not a good thing. You should understand what your code does. Writing code nobody can understand is not a flex.
Except spellcheck is a reasonably foreseeable part of a word processor. An AI model isn't really a common component of a typical web browser.
And those staff mostly use Westlaw :)
There is also "this code is functionally fine but I absolutely hate it"
and you fully understand the requirements that contacting “linux-distros” will impose on you
Imposing requirements on the reporter? No.
Fair play!
Your terms:
You may not use automated tools to scrape, copy, or bulk-download data from our service.
Pot kettle, huh.
But then you just move the security issue elsewhere with more to secure. Now we have to think about securing the automation system, too.
This is the same argument I routinely have with client id/secret and username/password for SMTP. We're not really solving any major problem here, we're just pretending it's more secure because we're calling it a secret instead of a password.
Cloud providers have put a lot of time and effort into making you believe every web app needs 99.9999% availability. Making you pay for auto scaled compute, load balancers, shared storage, HA databases, etc, etc.
All of this just adds so much extra complexity. If I'm running Amazon.com then sure, but your average app is just fine on a single VM.
What I say: I want a pay rise.
What management hears: We want more pizza parties.
"Someone viewed your profile" with a blurred photo of them.
So you know exactly who it is, but you won't just tell me in the email? I have to open the app/site so you can tick your engagement box for the day?
So glad I'm off that shit hole. It's just full of pompous picks anyway.
If I get a single email after I've unsubscribed I go back in my inbox and mark every single email I ever received as spam.
Fuck me, that is brutal and could absolutely ruin your SES complaint rate - even with the suppression filter on, as the emails are already in your inbox.
"Here's what AI came up with and it mostly worked the one time I tested it. Might need improving".
No. I don't want to test and pick through your shitty LLM generated code. If I wanted the entire code base to be junk, it'd say so in the readme.
I was in the same position as you when I started my law degree!
My solution was:
- Take notes on paper
- Scan with Genius Scan (free) or similar
- Upload to Microsoft Document Intelligence on Azure to get character recognition and a PDF output (standard OCR sucks for handwriting; also free for up to like 50 docs a month)
- Tidy up the text and store in Mediawiki long-term (you can also upload a copy of the OCR enabled PDF) (FOSS)
- File paper notes
- Throw paper notes once module is complete
So you always hold your nose?
Yep... Movie maker, Clippy, MSN Music, Encarta, Office accounting, Money, Response Point, hell TECHNET.
We have just stopped accepting PRs entirely for now. It's been utterly exhausting. We never got many PRs beforehand anyway so the uptick in entirely LLM written PRs was very noticeable.
We do continue to argue with LLM-submitted security disclosures. If these aren't an issue I just instant-close because debating with an LLM what is and isn't an issue is fucking painful.
Why wouldn't Wikipedia just capture and host this themselves? Surely it makes more sense to DIY than to rely on a third party.
It's not the "only" system to be fair. CourtServe looks like it was built in the 90s but works "OK".
I asked Copilot (work) to do this with a sheet and the summary it gave each time was so generic I couldn't tell one ticket from another. Feeding it tickets individually was fine, but in a spreadsheet it just seemed to forget.
Would be interested to learn how we can get true foreach loops.
How have you managed to take an example of where this worked and then proceed to entirely disapply it in a wider context?
change your definition of what an accomplishment
+ Get out of bed before sundown
Yeah, I completely agree. I'm not sure what the solution is, but this ain't it.
Because when they eventually get their wet dream of 7-day renewals, everyone replies upon them once a week. LE being down for 48-hours could take out a big chunk of the Internet.
Certificates have historically been a "fire and forget" but constant re-issuance will make LE as important as DNS and web hosting.
Yeah like if I wanted to know what a particular AI says, I'd have asked it..
Most providers do for dedicated servers, or make you agree to a fixed term. I don't believe they do the same for VPS / Cloud servers.
Hetzner! They do ask for ID though.