sandblast

Maybe it was also your style that the LLMs learned from (and then pushed more towards the extreme). Oh the irony.

Well, most of commits have „brianathere and claude” as authors. Additionally, the style of comments in some of the files bears a strong resemblance to those typically generated by LLMs.

Moreover, this whole thing has 7 stars on GitHub as of writing, and yet the bottom of README boldly claims „ready for production use”. For me, that overly confident approach discourages maybe even more.

> People should clearly have the right to photograph in public

> should someone take someone else’s photograph they should need their consent to post the photo publicly

> I don’t think posting a photo on a private social media profile / group chat would count as public

That all sounds pretty similar to what I know from EU countries. Of course, there are also exceptions like photographing groups of people etc., but I don't think that goes the spirit of the balderdash's concept.

You claim that it is not the case, so I would like you to point out which of these aspects is different in one of these countries. Do you claim it's not allowed to photograph others in public without their explicit consent in Czech Republic, for example?

I think you meant "they should need their consent to post", right?

What exactly doesn't work like that in the countries you mentioned?

I don't think I implied it was, but would you mind sharing examples?

In the whole EU, I think.

I think it's similar to the difference between "the cop watching me when I'm near them and are aware of it" and "the cop watching me all the time, wherever I go and I can't know anything about this" (which would be impossible before cameras).

You can easily disable grouping in Windows Explorer.

When you have two dots in slider component and quickly move one of those over and past the other one, that second dot also unexpectedly changes position in unpredictable ways.

*what ever happened I hope I’m not the only one.

Ratios are numbers. They are literally just fractions. No one argues that the numbers don't make sense because you can have different units. But that's what units are for – to know what does the preceding number refer to. Why have a unit that doesn't give you full information?

Is the context not clear for you from the information that the article applies to "DreamWorks Interactive, Someone's in the Kitchen, version 1.0" and other clues that it's a game?

Why?

Thanks for this term, that's quite interesting! But it's kind of strange that this turns up only in 5 Google results.

Ah, that explains the good music selection!

Don't get me wrong, but I think this is a perfectly good place for a feedback, since you made the Show HN post. There is no need to redirect users to Google Forms.

I agree, I would add a default "nothing" entry in the drop down and enable both ATC feed and the music when an option is clicked.

The music selection is indeed quite good, but I would try to make sure that there are no vocals in the music — those overlap with ATC too unpleasantly for me.

I would add a toggle for disabling the clouds animation. It wastes a lot of CPU cycles for me.

Did you enable the toggle in the "Audio Controls" section? That's what got me at first.

Can you share anything more?

Why the snarkiness? Don't you acknowledge that YYYY-MM-DD is strictly superior to DD-MM-YYYY?

I would not underestimate the amount of resources necessary to support this brick-and-mortar stores model. You need to deliver those goods to each shop, then handle the returns of unsold items... Not to mention costs of employees (and their costs) — but that may be debatable, of course (creating jobs).

Do you have any sources to back up this claim? Genuinely curious.

The software catches the problem during a search triggered by tzdata change, alerts the user and asks for clarification. Before user action, the meeting is considered to be scheduled to 3 AM. Is that scenario unreasonable?

I don't see how the problems you mentioned couldn't be solved with storing clock time together with a location (or reading that time together with determining / asking for a location), as was suggested here. Could you share your perspective on that solution?

Doesn't really solve the problem mentioned, does it? I decide to generate a link which counts down to doctor's appointment 8 months from now, and in 6 months my country decides to change DST rules. The countdown is now wrong.

Would you be so kind to share some insights?