Hacker Newsnew | past | comments | ask | show | jobs | submit | 3form's commentslogin

>No argument against more onerous checking is undermined or rendered less severe due to an age field already existing

From your point of view.

What I can tell you is that there are definitely people who will argue that this is, by the fact of being written into law, now the spirit of the law.

Then these people will argue that the spirit of the law is being broken, and the implementation needs to be better and tighter. Not that it needs to be repealed! Because clearly this is something that was wanted. And to many, many people, this will be sufficient argument not to complain about further measures.


This needs to be simply fought because it's a measure that is supposed to fight the reluctance of the society, not actual problem. For the actual problem it's ineffective. This will be met by surprise once it's fully implemented and new, worse measures will be proposed. Hence, it needs to be cut off as early as possible to spare everyone the trouble.

Don't they ban people using custom clients when discovered? I feel like I've read something on that note.

They do - but the utility is so high vs the risk (for a new number) that it’s worth doing anyway for many users and even organizations.

Just yesterday we spoke with a $50-100m ARR org org using baileys for internal messaging!


> a $50-100m ARR org org using baileys for internal messaging

Couldnt they just use post-it notes internally and still be a $50-100m ARR org?


Yes - the interesting part is the decision that the “risk of losing internal comms to a ban is worth it” - even at that size.

According to one of the founders there’s no better way for them to reach a lot of low-skill part-time employees reliably.

It shows the need to bring AI to where people already are and onto the platforms they already use.


How does someone's refusal to install an extension necessitate millions of users having to close the popup? I guess you mean someone as in "vast majority of population"?

A proper course in technological literacy would also necessarily include the fact that browser extensions are quite possibly not safe.

One thing I would like to see addressed is the misconception that QC can help turn NP problems into P. I see this floating from time to time.

Yes, totally. I feel like the computational complexity part of quantum computing is actually pretty well explained to the 'layman' by some of Scott Aaronson's work, but unfortunately it's not well placed in context (i.e. it very much focuses on the theoretical CS, and not the whole QC picture). You have to sort of start digging for material about computational complexity theory/quantum and stumble into his output.

I like the final conclusion. And sadly I don't feel like anything changed for the better on this topic since 2023.

I am afraid that without a major crash or revolution of some sort, user won't matter next to a sufficiently big biz. But time will tell.


I've found the users-first mentality degrading over the years at companies. It's a bit jarring too, since a lot of my early training was pretty user-centric.

This is definitely true. In growth companies there is way more emphasis these days on investor hype over user centricity.

For companies that have a solid competitive moat they have at best gotten lazy about user centricity and at worst actively hostile.


I do have a feeling that the example of bigger players is carefully followed by many of the other companies, kind of as a cult of success. And that example for a long time has been rather lacking.

And importantly, older games now tend to work better in Linux than they do in Windows.

"Lawyer benefitting from cases about prostitution equals to a pimp" kind of argument.

Only if they provide the software or software as a service. Then I suspect it's good enough if the modifications or forks made are shared internally if software is used only internally, but on the other hand I'm not a lawyer.

> if software is used only internally

Internal users are still users tho. They are entitled to see source code and license allows them to share it with the rest if of the world.


Employers might argue that such internal use and distribution would fall under the “exclusively under your behalf” clause in the GPLv3, which is inherited by the AGPLv3.

Oh, I guess it would. Ignore me.

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

Search: