Recent submissions

Comment · 1 month ago
Yes. Because you say that as if Linux doesn't require the same or longer the second you dare use it as an average user and want to change the defaults. Or just use it in general.
Comment · 1 month ago
> The handful of popular DEs [0] are going to be much more polished and functional for like 99% of tasks, and nonexistent [1] for the other 1%.

Lol! You should try being a comedian.

Comment · 1 month ago
You make a very compelling argument. I've been thinking of at least trying it out before, but have been leaning towards it more and more over the years. A couple of questions though, if I could bother you with them?

How is remoting performance e.g. via VNC/RDP or particularly via Moonlight+Sunshine (intended for gaming and such)?

And how programmable is the configuration of Qubes? I like the idea of NixOS for example, but given how comparatively little activity there is in the actual nix rather than the packages, and across so few developers, I worry what would happen if someone got hit by a bus or something. But I still like programmatically configuring computers over manual monkey patches, because I have the memory of a gold fish. :p

Comment · 1 month ago
Comment · 2 months ago
Those two pipe dreams sound really cool! Do you have a website or something to lurk you via if you eventuality get around to those? I find it difficult to keep up, as it were, using form histories and other social media platforms.
Comment · 3 months ago
If you are going to quote a dictionary, please first ensure you are quoting it properly and without misrepresenting the contents and b) that in cases wherein a definition has multiple potential meanings it lists the different uses from common to uncommon.

As per the actual 1828 Noah Webster's dictionary, which you can find here https://archive.org/details/noah-websters-1828-dictionary-el..., on page 7828, the definition of "Milk" is:

MILK, n. 1. A white fluid or liquor, secreted by certain glands in female animals, and drawn from the breasts for the nourishment of their young.NWAD MILK.2 2. The white juice of certain plants.NWAD MILK.3 3. Emulsion made by bruising seeds.NWAD MILK.4

And, just in case the commonality of milk being milk from a cow, see also the other shorthand definitions noted on pages 987 and 988 of the table of contents.

MILKEN, a. Consisting of milk. [Not used.] MILKER, n. One that milks. MILK-FEVER, n. A fever which accompanies the first flowing of milk in females after childbirth. MILK-HEDGE, n. A shrub growing on the Coromandel coast, containing a milky juice. MILKINESS, n. Qualities like those of milk; softness. MILK-LIVERED, a. Cowardly; timorous. MILKMAID, n. A woman that milks or is employed in the dairy. MILKMAN, n. A man that sells milk or carries milk to market. MILKPAIL, n. A pail which receives the milk drawn from cows. MILKPAN, n. A pan in which milk is set. MILKPORRIDGE, MILKPOTTAGE, n. A species of food composed of milk or milk and water, boiled with meal or flour. MILKSCORE, n. An account of milk sold or purchased in small quantities, scored or marked. MILKSOP, n. A soft, effeminate, feeble-minded man. MILK-THISTLE, n. A plant of the genus Carduus. MILKTOOTH, n. The fore tooth of a foal, which is cast within two or three years. MILK-TREFOIL, n. A plant, the cytisus. MILK-VETCH, n. A plant of the genus Astragalus. MILK-WORT, n. A plant of the genus Euphorbia; spurge. MILK-WEED, n. A plant, the Asclepias Syriaca. MILKWHITE, a. White as milk. MILKWOMAN, n. A woman that sells milk. MILKY, a. Made of milk.

Specifically note the commonality of milk dash thing when it refers to plants. Not that it's particularly relevant, aside from the actual commonly used definition of milk already provides an example of milk being commonly understood as milk. As an additional example, look to the definition of mentioning almond milk on page 2134. Specifically note that it says milk of almonds, and not just milk.

AMYGDALATE, a. [L. amygdalus, an almond.] Made of almonds. AMYGDALATE, n. An emulsion made of almonds; milk of almonds.

As you can see, I care way to much about milk.

Comment · 3 months ago
To the letter of the word? Perhaps. To the spirit? Hmm.

Strange then that you reject critique elsewhere. Accessibility is not just a checkbox, it's to consider and test the actual use of it.

Comment · 3 months ago
Or perhaps you shouldn't get defensive of critique on your "design vision" such that you just write them off entirely like it has no value? You might like driving in the opposite lane, but rules say otherwise, and best practice can be likened to it because it's been decided on or landed that way due to multiple people being involved in the process of deciding those rules. Just as with best practices. There are best practices in design too, you know.

Anyhow. Depending on the viewport your panels do get in the way, it's 1/3 of the screen on mine for example. If you're going to hide the panels, hide them properly. That you show them at the top and bottom automatically, fine, though they could be smaller on mobile. However, you could at least consider the UX of using it on smaller viewports. If I want to scroll up a little bit while reading, they pop into view, making me have to scroll down to hide them again. Meaning I have to scroll higher up than intended, so I have enough space to scroll down. Another common user pattern is to slowly continually scroll too, and a tiny jitter upwards causes them to reappear, but requires comparatively massive downwards scrolling to hide again. Your site is not the only one to do this, but it's just bad design. Vision or no, and it's no justification, just an excuse. And then, what about left handed people? It's easier to accidentally click into the message box field, which opens up the keyboard and you'll have to close it. Pair this with it taking up the majority of thumb space for scrolling, given its size, and, well. Is it unreasonable for people to tell you it's aggravating? No. And this is without considering, and doing the minimum for, people who may suffer with controlling devices for whatever reason. Not by "bending over backwards" as some would have it, but at least taking such into consideration.

It's fine to have a vision of your intended or wanted design, but it's also important to be willing to reflect on how your vision may not necessarily be good design, depending on how one judges it, rather than just deflecting critique.

Comment · 4 months ago
> There's much to criticize about the dev, but there's really no way to make it significantly easier.

Not banning people that want to buy a flashing kit instead of making one would be a start.

I for one would learn nothing, and wanting privacy shouldn't require an arbitrary skill when unnecessary like in this case. Not even mentioning that buying the parts is prohibitively expensive compared to some finished kits I've seen.

Comment · 4 months ago
That sounds fascinating. Do you have public facing configuration you would be willing to share? :)
Comment · 4 months ago
As a small note against Syncthing, despite how much praise it gets, it's conflict resolution sucks. Enough so that it is easier to nuke it and set it up again instead. If you never have conflicts, it works fine though, but I find that rather unrealistic.
Comment · 4 months ago
Number 2 is so unusual I would immediately flag the company as a scam. How is asking for money a reasonable approach? There are alternative ways, easier too depending on country, and all you'd be doing is selecting for desperation while also spreading bad rumors from all the people who nope out when they see such malpractice.
Comment · 5 months ago
_Try_ to? Are you serious? We're not taking ambiguity due to phrasing, we're talking straight up not mentioning it on either the front page, on the show all page or even on the page the components button takes you to. Not even on this forum thread. There's barely any text on the front page to change and there are even multiple places you can mention React. You could mention it in the title, e.g. "Open source _React_ UI kit for modern document apps" or you could add it to the second paragraph, e.g. "React components ready to drop into user-facing flows, agents, or internal tools." Not to mention the components page. And given what you use to make the website, how does it take this long to update something this trivial when you are going out of your way to promote it, replying to comments and your other services by proxy?

Also, add either user interactive loading of components or lazy load the demos, the amount of demos murder performance on phones.

Comment · 5 months ago
You can use SSH keys and GitHub deploy keys to approximate this. Can't speak for the security of it, but I have never set up GitHub with access to every repo. Not sure if there exists approximate functionality in other git forges though.
Comment · 5 months ago
> Everything just works and it has for some years now.

Strange then, that so many people and particularly those who haven't spent years or decades fighting their OS or desktop environment, seem to disagree.

Every time a linux user says "everything just works" there's a massive gotcha. Remove the terminal and try to use a linux system, setting everything up, while properly roleplaying those who haven't spent years to get used to linux's many weird choices and you'll perhaps understand.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton