Perhaps you're a testament to why we actually want "managers who are also engineers" in these roles - for exactly cases like these, where you have the experience to know what "done" means.
That's exactly why it's written this way -- to devoid the reader of any prejudice
and humanize this tragic story -- because it is tragic. If it was written "normally", like "Elvis' Grandson Ben killed himself, and here's why..." some people might hand wave it away as just another "poor little rich boy story". This is also probably one of the reasons for his suicide (IMO of course). I mean, he's Elvis' kid he couldn't possibly be unhappy, right?
As to whether or not this is appropriate for HN, I'm also not so sure... but I enjoyed reading it.
I think you're taking my example a little too literally there... it's an example. The point is to save the reveal (spoilers?) till the end so that you can relate to the story more.
I find it difficult to relate to a story about growing up the ultra wealthy grandson of a famous musician. Them being related to Elvis doesn't make it less relatable.
And personally, adding the "who is it" mystery made the story less relatable. Instead of reading it and empathizing, I was trying to figure out who they were talking about. Then there's the morose reveal of "Aha! It was Ben Keough that committed suicide."
Don't worry, by the time this kid's old enough to even care, he'll be unrecognizable. If it's any consolation. I cannot recognize this kid as anything other than a "kid". Good looking kid for sure, but still a kid.
Which right are we talking about here, the right to run an image through an ai for no reason or the right to prevent an image being run through an ai also for no reason?
Privacy is not a right, it is a condition under which you have different rights. Whether that condition exists depends on social norms - for example a picture of someone in their underwear at a public locker room is very different from a picture of someone in an equal state of undress at the beach. A major factor in whether something is an invasion of privacy is the amount of effort others need to take for it to become public - you can for example have a private conversation in a public restaurant despite the fact someone could theoretically eavesdrop, it only stops being private when you start talking so loudly that there is no need to eavesdrop. Also to be considered is the likelihood of someone maliciously trying to gain information - a bank failing to shred financial documents might be a violation of privacy as someone going through their trash is a real risk; but my grandma doesn't need to shred old post cards. I would definitely consider trawling obscure websites with an ai to be in the eavesdropping/dumpster diving regime.
Coming back to the original point, yes you don't have to explain to anyone else why you are exercising your rights, but freedom isn't free and you need to be able to justify to yourself that what you gave up in exchange for your rights was worth it. Idealistic platitudes might at first glance seem comforting, but they make serious conversation impossible. At the end of the day privacy on the internet is an extremely nebulous concept, and without questioning "what's the point?" every now and then, it's easy to lose perspective.
I appreciate you going into such details, but I think we're losing the original perspective here. What I was talking about is, parents decide so many things for their children, justifiably so. This is just one thing where they could leave the decision to be taken by their child himself if and when he starts to care and understand the consequences, with the only downside being slight hindrance to pleasing their own ego.
PS: Privacy is a right, not a mere condition. In country of my residence it's meant to be protected by the constitution, so I think it qualifies.
FWIW we’ve been using ffmpeg-wasm on one of our products [0] for a couple months and the main issue is garbage collection. You’re limited to 4GB memory, but if you don’t kill and restart the workers every N operations it crashes the browser tab (even with proper unlinking of files in the virtual FS).
I suspect you could still make it work with clever usage of the File System Access API as a cache, and process larger files in chunks. Then you’d mostly be limited by the Blob storage limits [1], and memory required to merge processed chunks together.
I think prolific in this case is more the "Super Whizkid DJ Creates 100,000 Tracks in a Week" sense -- not in the sense that you may or may not have heard of them...
