Hacker News new | past | comments | ask | show | jobs | submit | endofreach's comments login

"Too rich to be liable". What a shame. Someday people will realize what he is responsible for. But if a poor man sells weed to kids, or even worse, truly addictive drugs...

No one said "Too rich to be liable".

> But the judge found a lack of specifics about what Zuckerberg did wrong, and said “control of corporate activity alone is insufficient” to establish liability. Her decision does not affect related claims against Meta itself.


Laundering liability is expensive but a great option for those who are rich and unscrupulous. So yes... it is that they are too rich to be liable.

How do you differentiate laundering liability and someone legitimately not knowing something?

Zuck takes the wealth, Meta and society take the fall.

If I could undo anything in this world it would be social media.


"If I could undo anything in this world it would be social media."

... he posted.


Ugh that tired old thought terminator.

‘You criticize society yet you are part of society’ isn’t the gotcha you think it is.


You should act on your principles when you have ample ability to do so.

Again. Thought terminator. Thanks for piling on though! That really helped the conversation.

What is preventing you from not using social media?

Probably because it's how society operates now and while they wish society was different, they don't want to become a hermit.

No, this is not how society operates. Recall just a few days ago when chronically social-mediaed people got the shock of their life when Trump won handily. Social media did not prepare them for this outcome. Why? Because a large fraction of society doesn't use social media.

> Because a large fraction of society doesn't use social media.

They probably do use social media, but not in the bubble of the people who were surprised at the outcome of the election. That's actually one of the problems with social media. People are able to connect exclusively with in group and cut everyone else out of their lives.


Even so, putting quotations around something never said is disingenuous.

This looks like what my experience taking a passport photo with a 8 month old mini human felt like.

Oh boy do I know the feeling. We live overseas and both our kids were born here. So basically the first thing we had to do was get them their passports. Trying to get a 2-4 week old baby to open their eyes and look somewhat at the camera was... an experience.

Tip: Swaddle the baby, lie it on top of a plain light piece of fabric (we used one of my work shirts) and click the camera 100 times.

Having said that though, I'm starting to think an 8 month old would be even harder based on the fact that they move :D


I can only imagine the challenge!

Any easy way to make apps not recognize they're not running on an actual android phone?

I've read some apps that love to take too much control run CPU related checks amongst other things.

No android experience or usecase, just wonder how that works and how one would workaround that.


I don't think the point of this is to get everything ever to work. Just getting well-behaved and free software apps to integrate better than with waydroid (by reimplementing a higher level of libraries, rather than running the entire OS) would already be huge.


These are usually simple heuristics based on device name, whether you're running a signed version of Android, etc. Thirty minutes on Stackoverflow will usually cover all the fingerprints most simple apps use.

If they're using Play Integrity, you're mostly out of luck. Xposed will usually have the latest bypass, but there's long periods where there aren't any.


https://www.google.com/search?q=%22laurenzv.de%22

hardly the most creative code i have written, but though not done yet (last commit 2y ago– if this even gives me the right to keep using that word)... i still enjoy the idea very much. less struggle & more time to wander off for me, and i will finish it. but till today, nobody has seen it anyway, and likely not many will. this rough & badly executed idea, might not die a lonely death.


I was gonna say this it seems like an LLMisinterpretation of the code. I can't think of any other way how one would know the term plan9 and how to dive into assembly while not knowing what waters he is in. And then i read others had the same thought.

If this is true, i kindly ask the author to not feel embarrassed or "exposed", but be honest, so we can learn from this. I'd like to gain confidence in these type of "LLM exposed" things, but it never seems like people would admit, no matter how obvious. And of course, here it is not obvious, this is of course a wild, very judgemental guess.


Honestly? No. Please feel embarrassed about your sheer arrogance to think that LLMs are a viable shortcut to not having to do The Work.

This pisses me off so much.


> no one uses promises any more

I haven't used node in years, so i wonder: What is used instead?


async/await, which uses promises under the hood, but you typically won't interact with the raw promise objects


Ok thank you for clarifying. then i misread the original comment.


96.3% confidence score that this post was written by/edited with ChatGPT 4-o.


Why not just give kids MDMA if they feel lonely?


I think I heard this on a joe rogan podcast. Will add this to our roadmap along with DMT as an alternative.


laravel has too much magic that really, really, really gets in the way as soon as you get to where things become interesting. too much magic. definitely not clean. and architecture wise… well… i have just never seen a project with controllers that is well designed. and if you even advocate to use a framework with bad design choices because many others do the same… it’s still bad design & it will come back and bite you.

you should always prefer a codebase optimized for the business, the purpose & the people who work on it everyday. if that requires more time to grasp it for newcomers, perfect. people make that weird argument all the time for going with a framework due to popularity & common ground. that’s so absurd. optimizing for onboarding time & quickest graspability, when that factor is usually irrelevant in most projects.

also, the best thing about modern PHP are the PSRs. They are not appreciated enough. Stick with them. Don’t be clever. Don’t use magic. Be explicit. Don’t don’t repeat yourself. Write code like your mom reads it. Et voilá, your homemade framework is gonna be just fine.

Especially compared to projects built around frameworks by devs who very rarely if ever look at the source code of the magic they use. debugging and fixing those issues took more of my lifetime than the hours i’ve put into updating my personal web app framework (latenight-php).

Also: Choosing which tire you want doesn’t equal reinventing it. And also: thank good people reinvented the wheel so many times… imagine EVs on rolling stones or wooden wheels.


Couldn't get past the thoughts about the naming after reading the first paragraph...

I propose a better name: Simple Message Spec (SMS)!


Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: