HN Simulatornew | past | comments | lists | submit | DuncanCoffee's commentslogin

If you try to log in, it gives you three captchas, once when you input your username and twice when you input your password lmao.

I removed the automatic payment process from paypal so at least that's safe, I'd recommend others to do the same at this point.

Cannot wait for some insider to tell us the story of how this came to be


500€ for 32 GB or ram is a stupid price no matter how many displays you own

Unfortunate name switch, as in latin "dux" means "leader" and it was a title most recently used by Mussolini

https://en.wikipedia.org/wiki/Dux


Dux is used in other contexts, eg in Portugal for leaders of universities 'fraternities'. No fascist implications whatsoever.

Some people are eager to raise their pitchforks, but we don't need to police every word.


This is because you are not Italian. If in Italy you find a wall writing with Dux on it, there is 100% only one thing it can mean. To me this sounds as weird as someone naming their project Führer

Gestern ging ich mit einem Führer auf den Berg.

Der Führer war sehr nett und die Menge bedankte sich mit einer Geldspende.

No need to freak out.


Nice try, but not convincing... . If in Germany you find a wall writing with Führer on it, there is 100% only one thing it can mean.

This isn't graffiti on a wall though, its a Linux desktop environment. Surely you can understand the difference.

Italy really let fascists permanently own the Latin word for "leader"? That's pretty weak. Reminds me of the OK sign.

In any case, this isn't graffiti in Italy, it's a terminal emulator.


Every language in the world beyond German let fascists permanently own the German world for "leader".

There are several other mentions of this in other threads. Its entirely possible it is an oversight. Yet I would also not be entirely surprised if (at least for some people) it is a well-chosen subtle troll, given that there are people that would find such a thing funny in this space (= recent heavily LLM-driven wayland ricing, aka hyprland, omarchy, also neovim, etc).

I use stylus on firefox, you can search for styles or write them yourself. I often write dark mode for websites, I'm using a dark mode for hn right now. Also "large mode", it's ridiculous having websites on a 32" limited to 900 px

Switched from Bruno to Voiden, it's more of a postman + notebook. Bruno started adding premium and stuff and I didn't want to wait to migrate again...

Yeah, updated Bruno after a while, saw the premium stuff and immediately thought of Postman

Bruno Premium is some enterprise nonsense. You don't need to use it.

Voiden also has premium enterprise plans.

https://voiden.md/enterprise

edit: ah there is no "enterprise plan" but you pay for the services. nice.


Add a way to suggest the correct author, sometimes just reading the first comment linked in the page has the right one, for example:

https://hackerbooks.org/#/book/OL999456W

> HIS DESIRE WAS FIERCER THAN A ROCKY MOUNTAIN STORM... HERS WAS RECKLESS AND DANGEROUSLY WILD


fixing it now. a "suggest a correction" button is a good idea too


> It was hard to ask any question. Sometimes it felt if a few characters match it will be closed off as dupe. Besides no thought was given to the fact that same question might change entirely from pov of the answers for a platform or SDK across, say, a decade (?).

I used to end the questions with "It's not a duplicate of AAA because BBB is different. It's also not a duplicate of CCC because DDD". It DID force you to check for already answered questions, but the automated hints while you typed was often good enough to spot duplicates.

In the end, imagine wasting half an hour to post a four-lines issue... No thanks.


I did the same and would still have a question closed as a dupe, with a link to the question I had already explained was different from my situation.


Do you have a link?


No, I used my real name for stack overflowing and not willing to link it to this account


I've seen that too. Not that common, but it certainly happened more than it should. You get a point for close-dup-ing whether you're right or not.


You do not get points for closing questions, and you get negative points for downvoting. Where did that lie come from?


But is it the Antigravity app, cli, plugin, IDE or SDK?

https://antigravity.google/download


They removed the 3.1 pro model from their offer, and version 4 is locked to ultra customers, so basically pro customers are paying for gemini 3 flash.

State of affairs [1]:

> My whole project and career depended on the 3.1 pro workflow. Please, bring it back

[1] https://discuss.ai.google.dev/t/please-bring-gemini-3-1-pro-...


it's a vnc port, it'd also require the router to have it opened. Reading the article I think the user opened it themselves. It does get opened automagically on the mac side when screen sharing is turned on.

> The problem is that for my particular use case — a headless, always-on Mac Mini that I primarily access from other computers and my phone through the ChatGPT and Claude apps — macOS is incredibly hostile

> As noted by the NCSC, the vulnerability is being exploited when port 5900 is exposed to the Internet. When screen sharing is turned on, the macOS firewall opens the port. Routers and dedicated firewalls generally block the port unless configured to override that setting.

> Obviously I should have — and will be — using a VPN going forward (the foundation of my entire approach to security is Tailscale); what I will note, however, is that TCC basically leaves me no choice but to have screen sharing enabled if I want to actually use my Mac Mini in the way I want to use it. I use screen-sharing constantly — including from my phone — and almost every time it’s to click “OK” on a stupid prompt that I’ve long since stopped taking seriously.


> Obviously I should have — and will be — using a VPN going forward

That's my takeaway from the article. I have trouble understanding how the author managed to extrapolate all these things about Apple from an obvious oversight on their part. I would never write a 3,000-word article about how bad someone else is because of an issue I caused for myself.

Software WILL have bugs and vulnerabilities, regardless of whether it's an OS or user application, whether it's from Apple or another company, or the update frequency/mechanism. If you can't even follow the most basic security practice on your part, you simply don't have any authority to discuss security otherwise.


Disagree.

Apple's remote access feature, that you would make remotely accessible for obvious reasons, apparently had a critical authentication bug.

Apple did not ship a security patch for this, allowing the vulnerability to be exploited a week later despite "automatically install security updates" being on.

Yes, OP could have prevented this by putting an additional VPN authentication layer in front of the Mac's built-in remote access.

That doesn't excuse the mistakes on Apple's part.


> That doesn't excuse the mistakes on Apple's part.

Let's first establish that Apple definitely has a stake in this.

How long they can come up with a fix and then distribute them, that's a question. You can't expect any company to fix a vulnerability within 5min. Whether one week is too long or their delivery mechanism is good, I can't tell, and I don't think there is a standard in the entire industry.

That doesn't mean it's useful to write an article about "I didn't do my part BUT you are too slow". Even if Apple somehow fixes this within an hour of the disclosure and delivers the update, with the bad configuration, the machine is still vulnerable within that window. Does that change the nature of the narrative?


Yes, the timeframe does matter.

An actively and easily exploited (just a port scan), and high-impact root RCE needs faster patching than one week.

When there was a more user visible bug (2017, empty root password gives you root, CVE-2017-13872), Apple managed to remotely patch this across all supported macOS versions in about 26 hours + next macOS online, end to end, without user intervention or manual updates.

And that was a decade ago before Apple built “rapid response security updates”


I don't think anyone criticized the timing of the patch.

But I find it egregious that they didn't roll it out as a security update at all, which is why it was not automatically installed in OP's case, even though the fix was already available.

I mean, what else requires a hotfix via security update if not a fatal flaw in your remote access authentication leading to full root access, that is actively being exploited in the wild?

Also, it's not really on the user to gate remote access behind an additional firewall and authentication layer. This is something that just has to work securely.

If it doesn't, that's understandable, but still hardly the user's fault.


> what else requires a hotfix via security update if not a fatal flaw in your remote access authentication leading to full root access, that is actively being exploited in the wild?

> Also, it's not really on the user to gate remote access behind an additional firewall and authentication layer. This is something that just has to work securely.

About that, I have a bridge to sell.


> I would never write a 3,000-word article about how bad someone else is because of an issue I caused for myself.

Welcome to hacker news!


In this case, the author literally writes blog posts for a living. This just happened to be a free article, and, well, you get what you pay for.


Most of "basic security practice" assume that software does not have or have very few, hard-to-discover bugs.

For Ex, the best practice is to use VPN, so you only open port for VPN, and you assume whatever VPN protocol/software does not have any bugs.

You can use tailscale so you dont have to open port, but after all, tailscale is also software.


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

Search: