HNHacker News
TopNewBestAskShowJobs

slacktivism123

159 karma · joined July 10, 2025

submissionscomments
slacktivism123··on I accidentally became PureGym’s unofficial Apple Wallet developer

    No secret. Just vibes.
Since you know the tells of LLM generated text, you'll know that this is a classic: No X. Just Y.

    Proxyman -- pick your poison.

    And if you're from PureGym reading this—let's talk.
There's a mixture of em dashes joining words and double hyphens spaced between words, suggesting the former were missed in a find and replace job.

"And if you're from [COMPANY] reading this[EM DASH]let's talk" is a classic GPT-ism.

    It's like the API is saying "Hey buddy, I know this is odd, but can you poll me every minute? Thanks, love you too."

    Shame Notifications: "You were literally 100 meters from the gym and walked past it"

    It's just a ZIP archive with delusions of grandeur
Clear examples of fluff. Not only do these fail to "add facts or colour to the story", they actually detract from it.

I agree with you that em dashes in isolation are not indicative, but the prose here is dripping with GPT-speak.

slacktivism123··on OpenFreeMap survived 100k requests per second
>What exactly leads you to make this sort of claim?

https://news.ycombinator.com/item?id=29651993

https://news.ycombinator.com/item?id=42365295

https://news.ycombinator.com/item?id=44038591

>are you just running your mouth off?

Don't be snarky. Edit out swipes.

https://news.ycombinator.com/newsguidelines.html

slacktivism123··on Fire hazard of WHY2025 badge due to 18650 Li-Ion cells
What's with the mock-security-advisory with logo for the 'vulnerability' (Heartbleed, anyone?)

Why is the important safety advice buried in a bunch of interpersonal drama and administrivia?

slacktivism123··on The PSF has paused our Grants Program
>In an ideal world, we wouldn’t need to pause the Grants Program and would instead be granting even MORE awards to our inspiring community.

>The AI sector, for example, relies heavily on Python and is mostly untapped for the PSF, PyCon US, and our entire community.

slacktivism123··on Anthropic revokes OpenAI's access to Claude
>That's like asking why is an SDK phrased as a special kit

It's Software Developer Kit, not Special Developer Kit ;-)

slacktivism123··on How to Secure a Linux Server
This guide ignores many sane defaults in favor of a patchwork of cargo cult scripts and outdated packages, added over time by random people with no thought for threat modeling, that may even result in an increased attack surface.

See this comment from 2019: https://news.ycombinator.com/item?id=19178938

I will leave you with this line from README.md:

>I am not as knowledgeable about hardening/securing a Linux kernel as I'd like. As much as I hate to admit it, I do not know what all of these settings do.

slacktivism123··on Performance and Telemetry Analysis of Trae IDE, ByteDance's VSCode Fork
> As long as the conclusions are sound, why is it relevant whether AI helped with the writing of the report?

TL;DR: Because of the bullshit asymmetry principle. Maybe the conclusions below are sound, have a read and try to wade through ;-)

Let us address the underlying assumptions and implications in the argument that the provenance of a report, specifically whether it was written with the assistance of AI, should not matter as long as the conclusions are sound.

This position, while intuitively appealing in its focus on the end result, overlooks several important dimensions of communication, trust, and epistemic responsibility. The process by which information is generated is not merely a trivial detail, it is a critical component of how that information is evaluated, contextualized, and ultimately trusted by its audience. The notion that it feels wrong is not simply a matter of subjective discomfort, but often reflects deeper concerns about transparency, accountability, and the potential for subtle biases or errors introduced by automated systems.

In academic, journalistic, and technical contexts, the methodology is often as important as the findings themselves. If a report is generated or heavily assisted by AI, it may inherit certain limitations, such as a lack of domain-specific nuance, the potential for hallucinated facts, or the unintentional propagation of biases present in the training data. Disclosing the use of AI is not about stigmatizing the tool, but about providing the audience with the necessary context to critically assess the reliability and limitations of the information presented. This is especially pertinent in environments where accuracy and trust are paramount, and where the audience may need to know whether to apply additional scrutiny or verification.

Transparency about the use of AI is a matter of intellectual honesty and respect for the audience. When readers are aware of the tools and processes behind a piece of writing, they are better equipped to interpret its strengths and weaknesses. Concealing or omitting this information, even unintentionally, can erode trust if it is later discovered, leading to skepticism not just about the specific report, but about the integrity of the author or institution as a whole.

This is not a hypothetical concern, there are numerous documented cases (eg in legal filings https://www.damiencharlotin.com/hallucinations/) where lack of disclosure about AI involvement has led to public backlash or diminished credibility. Thus, the call for transparency is not a pedantic demand, but a practical safeguard for maintaining trust in an era where the boundaries between human and machine-generated content are increasingly blurred.

slacktivism123··on Speeding up my ZSH shell
>it seems like ZSH tries to update on every shell spawn

Learn your tools first, not bloated frameworks. There's a gulf of difference between vanilla zsh and this:

>Community-driven (with 2,400+ contributors) framework for managing your zsh configuration

>Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc)

>140+ themes to spice up your morning, and an auto-update tool that makes it easy to keep up with the latest updates from the community

slacktivism123··on “I noticed a clear violation of our contributing guidelines”
Is this the future of collaborative coding?

When

https://github.com/antiwork/flexile/pull/427#issuecomment-30...

results in

https://github.com/antiwork/flexile/pull/427#issuecomment-30...

More incredible examples where a LLM flags contributors' pull requests because their comments contain minor grammar errors:

https://github.com/antiwork/flexile/pulls?q="our+contributin...

slacktivism123··on LLM Inevitabilism
Comments should get more thoughtful and substantive, not less, as a topic gets more divisive.

https://news.ycombinator.com/newsguidelines.html

Aside from that, I don't see how the collection of simple one-shot JavaScript wrappers (like "Extract URLs", "Word Counter", and "Pomodoro Timer") that you keep bringing up is related to your argument.

slacktivism123··on LLM Inevitabilism
Yeah, this model didn't work it seems.

You're holding it wrong. You need to utter the right series of incantations to get some semblance of truth.

What, you used the model that was SOTA one week ago? Big mistake, that explains why.

You need to use this SOTA model that came out one day ago instead. That model definitely wasn't trained to overfit the week-old benchmarks and dismiss the naysayers. Look, a pelican!

What? You haven't verified your phone number and completed a video facial scan and passed a background check? You're NGMI.

slacktivism123··on LLM Inevitabilism
I look forward to the inevitable replies from HN's appeal-to-authority darlings explaining why we are "crazy" to not believe in this "future".

Debate team techniques are super useful when your salary now depends on shilling LLMs!

slacktivism123··on Kiro: A new agentic IDE
Having ten "Electron Helper (Plugin)" eat a GB of RAM each on idle is the premier desktop experience nowadays. We can't have native apps any more: we don't know how to build them.
slacktivism123··on Show HN: Refine – A Local Alternative to Grammarly
Incredible. Has any non-AI grammar checker ever returned a "safety" refusal to the user before? Is this the power of LLM wrappers?
slacktivism123··on Show HN: Refine – A Local Alternative to Grammarly
>LLMs can also correct other sorts of mistakes, such as correcting "The first US President was _Ben Franklin_" to "George Washington".

And they can also cause new factual mistakes that a grammar checker never would!

slacktivism123··on At Least 13 People Died by Suicide Amid U.K. Post Office Scandal, Report Says
Please don't do this kind of tangential grammar nitpicking here. Comments should get more thoughtful and substantive, not less.
slacktivism123··on Configuring Split Horizon DNS with Pi-Hole and Tailscale
So Tailscale is now a US company and you can't bind to Headscale? Enshittification.
slacktivism123··on Perplexity launches Comet, an AI-powered web browser
Use case for LLM-infested Chromium wrapper?
slacktivism123··on Biomni: A General-Purpose Biomedical AI Agent
>doing that unlocks potentially billions of dollars of value that is otherwise elusive

What's more, it unlocks potentially new additions to the 206 legal cases where generative AI produced hallucinated (fake) content.

https://www.damiencharlotin.com/hallucinations/

slacktivism123··on Magic .env files built for sharing: Human-first, AI-friendly
Use case for non-deterministic processing of .env files?
← PreviousPage 2 of 2