More likely, they simply couldn’t figure out how copy and study the data with their Cellebrite box or whatever, then some older worker mocked them for not recognizing a floppy disk, and so they coped with the resulting feeling of humiliation using a temper tantrum.
Please email the mods rather than posting accusations of astroturfing. You may well be right, but they specifically direct us to say that to them rather than in comments. The footer contact email works well for this.
“can download” could refer either to transfers initiated by the user, or to transfers initiated from the device. The language “from [device] developers to users of [that device]” clarifies that this applies if users can access a third-party directory and/or repository of applications.
I strongly encourage the EFF to sue the FSF over not shipping age verification in Emacs, since in every respect Emacs fits these criteria; it is a computer environment that avid users can reside fully within to operate their system, and its publisher operates a directory+repository system at https://elpa.gnu.org. I think that both organizations would be excited to pursue that lawsuit pro bono, since it would evidence such significant flaws in the law that it might be struck by the court.
Incidentally, this likely also implicates Tesla and BMW as not requiring age verification before allowing users to download updates containing new pay-to-unlock applications from their vehicles’ in-app purchase marketplaces. I’m sure they would both be happy to help overturn this law once implicated in violating it.
The government is armed and can exempt itself from prosecution either by judicial means and/or by naked force. So it isn’t just a cut and dry licensing problem.
How can I apply this system to a random discussion archive page at HN in order to evaluate it more efficiently as a discussion guidance mechanism? I don't want to see usernames in that example, and I don't want a dynamic example either — but I think it would be much easier to convince HN that your AI product is worthwhile if you present an HN-specific example. Specifically, I suggest you take an HN discussion (the HTML is very simply structured), pipe each comment through your engine, and append the <div style="background-color: soft-blue;"> "Your comment etc etc" responses that would have been shown to each comment in the discussion.
Looking at the most popular results for " " on HN Algolia, I would recommend selecting a post that has at least a few hundred comments and is also about HN or YC or YC-adjacent people (since the mods are extra light-touch on such posts), in order to take the best possible sample for unmoderated discussion to evaluate Respectify against. This post is a good example that fits those criteria; I didn't pay attention to it at the time and I haven't assessed the discussion beyond 'total comment count >= 500': https://news.ycombinator.com/item?id=40521657
I recognize that's theoretically a lot of effort, but from a coding standpoint, it's simply `for $comment in $dom.xpath(/blah/blah/comment) { $ai.eval($comment); undef $comment.username; $comment.append($respectify.bulleted_list_with_html_colors); }` for what has the potential to be an extremely convincing demo to the target audience of us here.
That is an excellent idea. It is 2AM my time, but I may set Claude going and check in the morning. (I tend to keep a closer eye on AI coding than that usually!)
The preset articles and trying out comments were intended to be something similar: see a topic, see how it works. But running it on each and every comment on an existing thread is really powerful.
There may be privacy concerns? General respect? I don't want to tie assessments to specific commenters, who published in good faith not expecting some kind of automated review, nor thereby imply they commented poorly for example. But I'll code it up on my end and see what we can do with it. It's truly a very nice idea.
If you look through the history of the Show HN category, you will see a near-endless stream of "analyzing HN discussions" prior arts that may offer some assurances. I'm not suggesting removing usernames because anonymity is involved — it is not! — but, instead, to specifically focus viewers on the substance of the comments rather than the who of them. That's also why I chose something from two years ago, so that there's no appropriate reason to witchhunt over the past. (Some may still, but nothing short of evaluating AI-generated data will stop them, and you can't make a reasonable case using AI to evaluate AI.)
IANYL, though! Offering legal advice with the disclaimer “I am not a lawyer” could be prosecuted as practicing law if a reasonably party could still infer a potential lawyer-client relationship from your message and/or intent. Instead, “I am not your lawyer” explicitly denies the lawyer-client relationship, which closes the door on both being accused of practicing law illegally and on being found as party to a lawyer-client relationship whether or not you have the appropriate certifications.
> closes the door on [...] being accused of practicing law illegally
Does it? So I can say, "I'm not your lawyer, but I'm happy to go ahead and give you specific legal advice on your case." and I can't be accused of illegally practicing law? I was under the impression that this could still get you into hot water. But not being your lawyer, due to the fact that I am not a lawyer at all, I don't know if it is true or not.
As with all things, who are you going to get in trouble with? And what's so magical about legal practice as opposed to, say, giving shitty medical advice or telling someone how to build porch? Asking genuinely. No one falls all over themselves to say "I am not a doctor, but...", even though their next words could kill someone. The implication is that they don't have formal training but they saw something on Facebook that you should try. What happens next is on you, not on them.
> No on falls all over themselves to say “I am not a doctor, but”
This is precisely why I’m pointing this out: IANAL is a very curious case of people self-labeling their statements as “not trustworthy for the topic”. I can think of perhaps no other cases where it is so popular to claim to not be a professional in the relevant field, which suggests that IANAL is a ‘badge of honor’ rather than a proper legal disclaimer. Certainly few (if any) claim IANAD before writing about their experiences with medical issues, body things, or nutritional supplements here, even though those topics are (as you correctly indicate) potentially lethal.
Thus, IANYL: if your goal is to ensure that the recipient of your advice / opinion / whatever does not have grounds to claim that you provided legal advice, and therefore are their lawyer, then you can either do so weakly with TINLA (“this is not legal advice”), which still leaves the door open for awkward claims by some desperate grifter-rando to reach a bench, or you can do so strongly with IANYL (“I am not your lawyer”), which closes that vulnerability in full.
Not once in years of using IANYL have I seen anyone else properly protect themselves from this vulnerability; meanwhile, “IANAL but” remains in use as a badge of honor. So, yeah, I don’t think anyone considers the particular avenue of vulnerability a serious threat, and yeah, the general context of IANAL here is prideful rather than protective. But after twenty years of dealing with a stalker who was adept at internet and tried to fuck with my job at one point, I do now tend to value closing off legal vulnerabilities with certainty, and as a bonus it doesn’t imply insult to the professions of law.
reply