HNHacker News
TopNewBestAskShowJobs

Wilder7977

183 karma · joined July 7, 2024

submissionscomments
Wilder7977··on Notepad++ hijacked by state-sponsored actors
You are confusing being political with carrying out political discourse. They are not the same thing.

Being political for software means for example making some specific choices while designing it and advertising them as such. Means choosing a license over another. Means announcing political positions and possibly aligning the software to them (depending on what it is).

It doesn't mean going in forums related to that software to discuss random political topics.

Wilder7977··on Notepad++ hijacked by state-sponsored actors
In 2026 hoping that software could be (more) apolitical is a very brave stance. I look at the software world and I can see core political statements in almost every popular software. From privacy invasion, supporting shady industries (e.g., marketing) even at the expense of people (a reverse-welfare, in a sense), environmental destruction (e.g., complete lack of care for resource usage) and many more.

If anything, we need much more politics in software, ideally exercised by those who write that software instead of "apolitical" software writers who end up executing the political software of those who pay them.

If you meant to scope your statement only to FOSS, then this still applies (in fact, FOSS is inherently political), plus I suppose some people who invest their time to write software want to also use the same effort for political activism and there is nothing wrong with that. This can be expressing their political views via that software (e.g., vim and the support to children in Uganda) or can be using a license that only allows co-ops to run their software, or many other ways.

The idea that software even could be apolitical stems from the idea that technology can be neutral, which again, in 2026 is really a tough idea to support.

Wilder7977··on Notepad++ hijacked by state-sponsored actors
What a bad take. Not every political statement is morally equivalent nor worthy of the same respect. Supporting self-determination of people is not the same as supporting oppression of people - for example.

So the free expression is considered by everyone according to their own ethical and moral values.

Wilder7977··on Finland looks to introduce Australia-style ban on social media
You mention free will, but it would be an interesting conversation to discuss how much free will there is when people fight, without knowing it, against psychological manipulation, addition creation, all crafted with plenty of money and research. Especially when this people are young ones. Can the behavior still be called free will when you get hooked to mechanisms specifically designed to exploit humans in this way?
Wilder7977··on My Mom and Dr. DeepSeek (2025)
Nothing personal, but without receipts I am going to take this story as made up propaganda. I simply can't believe that visiting 4 health professionals, giving context about using a computer all day, nobody diagnosed a very common issue nor suggested it as a possibility.

I simply can't imagine this happening based on my experience with healthcare in two (European) countries.

Wilder7977··on Why do RSS readers look like email clients?
Then you write in your own language or in broken English, or you study the language you want to write in? If you can't write a text at all (even with plenty of mistakes), you hardly can review AI output. So, you just let AI write something for you that you might not even mean?

This is not "I need to communicate with a doctor" or another necessity, if you put content out there, presumably it's because you want to communicate. You want to write in another language? That's great, learn the language and help yourself with a vocabulary, even a translator, but write yourself (which is also a way to learn).

I am saying this as a non-English speaker, as it might be obvious.

Wilder7977··on Waiting for dawn in search: Search index, Google rulings and impact on Kagi
In Italian verbs for foreign words are almost always generated from the first conjugation (-are), which means "to google" is actually "googl-are".

With kagi, one cannot miss the opportunity to generate a similar verb " kag-are", which sounds exactly like "going number 2" (in a relatively rude way), which is what I ironically use every time I decide not to use the generic "search" verb. I consider it one of the minor benefits of being a kagi user!

Wilder7977··on Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss
Honestly, if I had to start from scratch in my own company, I would pick zulip. That is thread friendly for real, for proper async communication. Slack threads were bolted on as a feature, and it shows. I know that in 2 this is not a problem, but the way that - for example - notifications work for threads when you have 10s (or 100s) of threads is a pain. Finding back threads you were involved with is a huge pain.
Wilder7977··on I hate GitHub Actions with passion
A classic example would be build (container build) images instructions. Of course, other examples are running a security static analysis, running tests, or whatever other standard practice is desidered for security.

Say that you build 100 images, each with its own repository where there is the code, there is the Dockerfile etc. Now, if you build images with "make build", it means that ultimately the actual command line flags for the build command are going to be in the Makefile, inside each repository. These flags could include flags like --cache-from, build arguments, --add-host, or many other flags that may not be desirable in an organization. Imagine what the workflow file would like for such a case: you have your in-repo CI file that clones the repo, and then executes make test, make build, make push, etc. Do you know if make push sent the PCI registry secret somewhere else on the internet? Do you know what exactly flags were used to build? Not really, you need to trust the code inside the repo to at most collect this information, and how do you know it was not tampered or spoofed?

Compare it with the following scenario: All 100 repos at some point in that CI invoke an external workflow, which contains instructions to build images, push them to the registry (and run tests before, whatever). This can obviously also be a combination or workflows, I am saying one for simplicity. This workflow (or workflows) at the end produces an attestation, including provenance data and about what is run. It can do so reliably, because the instructions of what had to be done are within its own context. There is no input that comes from outside (e.g., the repository) that determined build flags or instructions, outside of what the workflow exposed (e.g., few variables).

In the second case, I can then use a policy that restrict images that have attestation and that were built by my workflow(s) that contain standard and deterministic instructions. This way I know that no image was built using weird build flags, including strange dependencies, maybe tampering with network and DNS (in makefile I can write whatever) or local docker cache, etc. I know this because a standard workflow was executed in a fresh, "sterile" environment with a standard set of instructions, that can't be changed or tampered by those controlling the repository content.

Note that all of the above is solely concerned with being able to make security statements on the build artifact produced, not on the context of the build (e.g., no network access).

Wilder7977··on I hate GitHub Actions with passion
See my other comment.

> when the implementation of these actions at some level live in the repo anyway

This is the false assumption. You can standardize that not to happen, and you can verify at runtime that's not the case. You can control admission of container images for example, restricting those that were built by your workflow X (the approved, central, controlled, standard one) and reject anything else. You do this via build provenance attestation.

With makefile I don't know how you can achieve standard and centrally manageable (and verifiable) instructions (which are part of SLSA).

Wilder7977··on I hate GitHub Actions with passion
Not really, that's the point. Reusable workflow, in a tightly controlled repos avoid exactly what you are saying and they are a fairly standard practice (if anything, also to avoid having 200 versions of CI instructions). You can also verify attestations provenance by enforcing attestation performed via that particular, approved workflow, which is not security theater, it's actual real controls.
Wilder7977··on I hate GitHub Actions with passion
You haven't engaged with what I wrote, of course it doesn't make sense.

The easiest and most accessible way to attest what has been done is to have all the logic of what needs to be done in a single context, a single place. A reusable workflow that is executed by hash in a trusted environment and will execute exactly those steps, for example. In this case, step A does x, and step B attests that x has been done, because the logic is immutably in a place that cannot be tampered with by whoever invokes that workflow.

In the case of the makefile, in most cases, the makefile (and therefore the steps to execute) will be in a file in the repository, I.e., under partial control of anybody who can commit and under full control of those who can merge. If I execute a CI and step A now says "make x", the semantic actually depends on what the makefile in the repo includes, so the contexts are mixed between the GHA workflow and the repository content. Any step of the workflow now can't attest directly that x happened, because the logic of x is not in its context.

Of course, you can do everything in the makefile, including the attestation steps, bringing them again in the same context, but that makes it so that once again the security relevant steps are in a potentially untrusted environment. My thinking specifically hints at the case of an organization with hundreds of repositories that need to be brought under control. Even more, what I am saying make sense if you want to use the objectively convenient GH attestation service (probably one of the only good feature they pushed in the last 5 years).

Wilder7977··on I hate GitHub Actions with passion
For certain things, makefiles are great options. For others though they are a nightmare. From a security perspective, especially if you are trying to reach SLSA level 2+, you want all the build execution to be isolated and executed in a trusted, attestable and disposable environment, following predefined steps. Having makefiles (or scripts) with logical steps within them, makes it much, much harder to have properly attested outputs.

Using makefiles mixes execution contexts between the CI pipeline and the code within the repository (that ends up containing the logic for the build), instead of using - centrally stored - external workflows that contains all the business logic for the build steps (e.g., compiler options, docker build steps etc.).

For example, how can you attest in the CI that your code is tested if the workflow only contains "make test"? You need to double check at runtime what the makefile did, but the makefile might have been modified by that time, so you need to build a chain of trust etc. Instead, in a standardized workflow, you just need to establish the ground truth (e.g., tools are installed and are at this path), and the execution cannot be modified by in-repo resources.

Wilder7977··on The struggle of resizing windows on macOS Tahoe
I have been experiencing this on my 2k monitors as well (Also BENQ). I tried every "fix" under the sun, eventually it stops after enough voodoo (reboots, unplugs) and cursing.

One of the many random issues on the OS with the best UX in the world (lol). Like music sometimes stopping and sometimes switching to speakers when turning off Bluetooth headphones, mouse speed going bananas randomly requiring mouse off and on, terminal app (iterm2) reliably crashing when I dare to change any keybinding, and many other things that never happened in years of working on Linux.

Wilder7977··on Jimmy Lai Is a Martyr for Freedom
Anthropologically speaking these statements about human fundamentals (or "human nature") end up falling flat. There have been plenty of societies organized in ways such that private property was irrelevant when existing at all.

I suggest "Debt" from David Graeber for a great dissertation of this topic (which is not the core topic, but definitely touched).

All of this without considering that private property of means of production is different from private property in general.

Wilder7977··on Airbus to migrate critical apps to a sovereign Euro cloud
Guess which country had never any interest in a strong (politically and militarily) Europe, to maintain the world hegemony?

A Europe with an independent defense is dangerous competition for the US. Maybe it means that some international trade will be done in Euro. Maybe it means foreign policies in Europe's interests.

Wilder7977··on 2026 Apple introducing more ads to increase opportunity in search results
Yes, accessing more than half of the market in US and about 25% of the worldwide one is surprisingly something businesses want to do.

Of course businesses do it because it's profitable. The point is that the market is ridiculously controlled while you are pretending that businesses can make _free_ choices, while for many of them they are not free or in some cases not even choices.

Wilder7977··on Show HN: Stickerbox, a kid-safe, AI-powered voice to sticker printer
These are all (both mine and yours) opinions, and we will need studies to see what's what. That said, my opinion is that not everything is a software development pipeline and needs to be efficient with short feedback loop.

To me what you say:

> will mean that they start seeing rewards for their efforts much faster

sounds essentially a negative. This leads to rewards-chasing and a habit of obtaining result without an appropriate amount of effort. This means that many won't even ever discover their passions or what they are good at. Putting the effort is a necessary step to grow. In other words, will any kid with this machine ever draw something from scratch, after they got used to having something much better than what they could do (at least at the beginning) by hand?

All of this without even mentioning the impact of creativity, where instead of having to think/conceive stuff you have a technology that does that for you after a minimal input, rehashing what has been already thought.

My wish is that tech people just realized that the world is better off without their tech in most cases and stopped thinking that everything in the world needs some tech to "help" (which of course is really a way to make money).

Wilder7977··on Internal RFCs saved us months of wasted work
I generally agree that it's better than nothing. That said, it's possible that sometimes these processes become bureaucratic shields for avoiding certain processes.

For example, a broken RFC process might be a way not to actually involve and gain useful consensus from people (I.e., I did my presentation during the weekly session, nobody had feedback), which instead would be the natural way in a company without that process.

100% agree that it's all about the people (and the culture shaped by them).

Wilder7977··on 2026 Apple introducing more ads to increase opportunity in search results
Reality forces people to do that. When 90% of people do whatever they use programs for via mobile, you (as in, a business who wants to succeed) are forced to make an android and an iOS app.
Wilder7977··on Using TypeScript to obtain one of the rarest license plates
Working should be a free choice (we can discuss about how much freedom exists for many people), and should always be paid. There is nothing wrong if a prisoner chooses to enagage in (fairly paid) labor. But if they are not free to do so, then they are slaves, not workers.

Prisoners already lack freedom in many aspects. "Sitting on their asses" like if they were sipping cocktails on a beach is a bit a misrepresentation don't you think? I wouldn't exchange the possibility to move and do what I want for possibly any amount of money, nor for being able to "sit on my ass" in that sense. Would you?

Besides the moral arguments - which I will say, they are so obvious that it feels incredible even having to discuss why enslaving prisoners is wrong - you can make economic arguments. For example, that having cheap or borderline unpaid labor compresses the salary in that market, or that this system creates a dysfunctional incentive to increase prison population for private profits.

Maybe that's why the US is one of the countries with the highest incarcerated population in the world. The highest among western and larger countries.

I understand though there is a cultural barrier. I am from Europe and in most countries here prison has a rehabilitation purpose, which is what most benefits society, and prisons are not private entities.

Wilder7977··on 2026 Apple introducing more ads to increase opportunity in search results
They are not free to do that when there is a duopoly and in most countries the platforms don't even allow competitors for that market (especially true for Apple).

Seriously, playing the "free market" card in the tech (especially mobile) space is really brave.

Wilder7977··on Internal RFCs saved us months of wasted work
In my organization we have RFCs, PRDs, ADRs etc. and I would say that the process is fairly broken. That said, I think what you mention is an important but not the only failure mode of a proposals process.

In some cases I have seen, people use RFCs to steamroll decisions when they are the only stakeholders. Here the waste comes from the fact that the proposal becomes just a bureaucratic step or a way to diffuse responsibility.

In the case you mention (which I have seen many times) I would say the general issue is that the goals and the constraints are not qualified sufficiently. If that's the case, then there are only 2 cases: there is an objective way to measure if an objection or comment makes sense or not, or it is subjective. If it's objective, then consensus is easy to reach, if it's subjective, it needs to be acknowledged and usually the decisions falls on those who are responsible for the outcome (e.g., the team who needs to maintain or build the thing).

Of course, the debate can move to constraints, goals or even ways to measure, but these are generally more straightforward.

Wilder7977··on Instagram chief orders staff back to the office five days a week in 2026
I feel what you are proposing is the worst of both worlds.

The company still needs to pay a full office (decreasing chances that money will be used for home office benefit or raises), people are still forced to live somewhat close to the office, not realizing the biggest benefit of remote work: living where you want, close to the people you care and freeing up money and time.

If working together really helps, it's enough that those who think that coordinate and agree on days to go to the office. If nobody agrees, than maybe the benefits are only perceived or subjective?

I will be honest, I believe that lots of people go to the office because their 9-5 (+ commute) job made it impossible for them to maintain and cultivate social relationships outside work, which means they see the office as their attempt to escape loneliness. I am not saying that's everyone, but that for many people is the case and that explains people non-stop interrupting, walking in on others, chatting etc., which is quite common in office environments.

That said, I think that remote work needs also a few key elements to succeed:

- a remote culture in the company (e.g., everyone understands flexibility in terms of working time, meetings are online-first, documentation and async work culture, etc.) - a good space to work at home. I can't imagine working on a stool and a laptop like some people were forced to do during covid. - discipline (e.g., not let work time bleed into personal time, blocking time etc.) - good social relationships with friends/family. It can be very alienating otherwise.

Wilder7977··on From M1 MacBook to Arch Linux: A month-long experiment that became permanenent
How? Finding a Mac docking station that works with 2 monitors is already a lottery. 70% of people in my company, me included, ended up plugging the HDMI directly into the mac (and a DP into the docking station), while the same docking station worked flawlessly with 2 monitors on Linux. I haven't tried four monitors, but I have to say that multiple monitors handling is something so far I would list under the downsides on Mac.
Wilder7977··on Progress towards universal Copy/Paste shortcuts on Linux
> Isn't it the same issue across all operating systems then?

Sort-of but not in my experience at least. In Linux there is a tendency of using /etc or .config files, where it's quite trivial to catch/modify anything.

> they didn't do something that would fix their issues

Oh well, I can't say I _fixed_ my issue. My mac usage compared to my linux+i3 usage still feels like bronze age tech, but definitely I salvaged what I could :)

Wilder7977··on Progress towards universal Copy/Paste shortcuts on Linux
No, I mean keybindings that are app specific and that are _not_ exposed in the keyboard configuration menu. Case in point, iterm2. Tons of useless keybindings that you have no easy way to see and disable. Let alone the fact that the app immediately crashes every time I try to modify one.

You really assumed I haven't searched - and figured out - how to change keyboard shortcuts?

Wilder7977··on Progress towards universal Copy/Paste shortcuts on Linux
I respect the personal opinion, but I personally find unbearable the number of times Apple devs demonstrate to think to know better how I should use my machines. Having sane defaults and customizing basic things (like not using a docking bar, or moving icons on the window on the other side) is something that I don't think requires any maintenance, or at least nothing that a trillion dollar company can't afford.

> For me the value of apple consistency and aesthetics far outweigh the costs.

For me this has ~0 value. I use a device multiple hours every day, muscle memory that makes sense for me is 100x more important that an abstract consistency for things that do not make sense for me. I know that different people have different priorities, though. To make a similar example, I use routinely two keyboards, a TKL and a split 58-keys keyboard. I use 2 layouts (one en-US and my native language). I have absolutely no trouble switching from one to another, and from one layout to another, it requires no effort or concentration, it's all muscle memory and context awareness. The same is with devices or programs for me. Consistency is for what _I_ decide is important to stay consistent, otherwise it doesn't have an absolute abstract value.

> It is just too much work to get to basic ok defaults, to have any energy left to think about what I might want to customize.

I have used Linux for about 10 years before I became even aware of all the things I could do with it. For everything I had to do from high-school to university I never touched more than the basics (Ubuntu and Mint, at the time). I think the defaults were totally OK, and nothing _needed_ to be customized. When I started working I started having additional requirements and the flexibility allowed me to customize and make more efficient the aspects of my workflow I considered important. All of this to say, while this is my experience, I can't relate at all with what you are saying.

> Iphones are another story, but eventually the tradeoffs outweigh android ux illogical nature and inconsistency there too.

I can't comment much on this. I find iOS UX to be completely a mess, full of hidden interactions (on this topic, see https://interactions.acm.org/archive/view/july-august-2025/s...), but I use my only iPhone minimally just for my work phone, so I concede this is a matter of habit (as it's probably the opposite - given 90 yo tech illiterate people can use Android phones).

Wilder7977··on Progress towards universal Copy/Paste shortcuts on Linux
From the perspective of a user, what's the difference?
Wilder7977··on Progress towards universal Copy/Paste shortcuts on Linux
> Devs do not get to decide

In my experience Apple devs are the _most_ opionated in terms of telling users how they should use their machine. The UI controls are super touchpad-centric, and it's crazy that a community-driven project like i3 is light years ahead to macOS "wm" features (not to talk about the native UI management). Also they decide for you where the icons to close the windows are, you want to change them? Nope, sorry, you are doing it wrong and can't move them. Your keyboard? Also wrong, you should buy an apple one, otherwise your modifiers are all messed up. You don't use the application docking bar? Well, you are doing it wrong, you can reduce it, but can't remove it, it's always going to be there at the bottom.

There are countless of instances in which the only way to do something is the Apple way, so much so that everyone who switched from Linux to Mac I have spoken with essentially concluded that either you bend to how Apple decided things should be done, or you will be constantly fighting your own machine.

I appreciate that this means that if you start with Apple and get used to their way, you have no cognitive burden on how to do something, but when you use your machine every day, you want to decide how things work to reduce your cognitive load (I.e., this is more intuitive for me this way), and Apple really doesn't like that.

← PreviousPage 2 of 4Next →