Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
defanor
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
defanor
1y ago
I saw it on HN before (and did not like that, either), while now noticed it in another submission by the same user, on a similar topic. [0] Apart from that, as mentioned in another comment here, the article's content seems no less stra
62.
▲
by
defanor
1y ago
Looks like A and B are swapped in the "errorB vs. errorA" plot's description: in other places (and on the plot itself, actually) A is the noisy sensor, B is the occasionally-faulty one.
63.
▲
by
defanor
1y ago
SVG feels much like HTML to me, especially when animations are involved: on the first sight it is quite nice and simple, does its job well, can be handled by fairly basic viewers (as well as converters, editors) and generated easily. Then t
64.
▲
by
defanor
2y ago
I think an article like that would benefit from focusing more on protocols, rather than particular APIs to work with those: referencing the specifications and providing examples of messages. I am pretty sure that the article is about chunke
65.
▲
by
defanor
2y ago
> It's such a wild idea that I've never heard it in the public discourse. IIRC there is a Dilbert comic strip about that. > Clickbait [...] would become worthless overnight Advertisement is not the only incentive. E.g., the
66.
▲
by
defanor
2y ago
I did not mean that there is a problem with it, only that I appreciate the simplicity of WHOIS. While HTTP-with-JSON is perhaps the most practical solution these days. To clarify my point of view, an ad hoc HTTP client for this indeed shoul
67.
▲
by
defanor
2y ago
I like WHOIS with its extreme simplicity [0]. RDAP, on the other hand, works on top of a large and changing HTTP [1], and uses a JS-derived serialization format [2]. RDAP has advantages, such as optionally benefiting from TLS, the data bein
68.
▲
by
defanor
2y ago
Indeed, that one would be more descriptive. At first I thought that the project is a joke about pretend-discovering that you can create a web page without tools other than a text editor, and without embedding external resources, similar to
69.
▲
by
defanor
2y ago
User experience with it, and opinions on it, seem to vary. I, for one, rather like both postfix and dovecot: both are well-documented, maintained, lightweight, reliable, yet configurable and feature-rich software, with few dependencies and
70.
▲
by
defanor
2y ago
More than SMTP hosting, but I use a VPS for multiple online services, including SMTP. SMTP in particular is handled by postfix, OpenDKIM, policyd-spf. Its incoming mail part is additionally supported by uacme with knot, nftables, fail2ban,
71.
▲
by
defanor
2y ago
Same, with Firefox on a Linux desktop, even after enabling JS. Edit: apparently it uses Oklab/oklch() [1], which is supposet to work in Firefox since version 113, but does not seem to work in 115. Or possibly it also uses something els
72.
▲
by
defanor
2y ago
Same here (not certbot and containers, but the part about reusing certificates for multiple services): it feels wrong to couple certificate acquisition with a web server. Apparently it is convenient when there is just a web server out of TL
73.
▲
by
defanor
2y ago
As a counterpoint, I find custom formats to often be nicer than reusing generic ones: atomic values (individual lexemes, primitive types: strings, numbers, etc) tend to have custom formats or semantic restrictions anyway (say, dates, length
74.
▲
by
defanor
2y ago
It is one of the proposed mechanisms, but apparently it is still unclear what is actually used [1,2]. [1] https://en.wikipedia.org/wiki/Magnetoreception#Proposed_mech... [2] https://www.scientificamerican.co
75.
▲
by
defanor
2y ago
As a satire, it does look amusing: the "professional" versions are about as rude as "unprofessional" ones, but the wording in those makes it more annoying (and perhaps condescending), "adding insult to injury".
76.
▲
by
defanor
2y ago
As an option that still uses HTML, with relatively minimal and common dependencies: the unified header and navigation insertion, as well as other aspects of website generation and syntax checks, can be handled with XSLT. Or one may employ a
77.
▲
by
defanor
2y ago
A few things in it that I would not put into a beginner's (or any) guide: - Semantic tags (header, footer, main, section): machine-readable semantics can be fun to play with if one is so inclined, one can go even for RDFa, but AFAICT t
78.
▲
by
defanor
2y ago
With search engine results polluted with "AI slop" (often long-winded and useless articles, not answering the questions; a relatively advanced SEO spam), I notice that Stack Exchange websites are among the good ones now: if there
79.
▲
by
defanor
2y ago
In section 5.7: > But in this section we’re going to be talking about a specific kind of merge: the fast-forward. This occurs when the branch you’re merging from is a direct ancestor of the branch you’re merging into. Looks like "fr
80.
▲
by
defanor
2y ago
I guess that authoring in MathML, and rendering MathML into images for browsers that do not support it, would have helped to avoid the mentioned inconsistency.
81.
▲
by
defanor
2y ago
> So we did that for a bit much to the annoyance to developers. Then we started emailing them to see if they wanted to chat- I can't speak for you, but a lot of people in our book didn't reply. This looks like an amusing misund
82.
▲
by
defanor
2y ago
> It gives us 50x better engagement than email and 8x better response times to customers. Does it mean that it forces the customers to send 50 messages instead of a single mail message? > However, developers hate email. Always feels a
83.
▲
by
defanor
2y ago
For libre options available from Linux distributions' repositories, see isync (aka mbsync) and offlineimap. And mail clients in general should be able to handle IMAP and standard formats (Maildir, mbox). If one cares about mail backups
84.
▲
by
defanor
2y ago
Not exactly accessibility features, but a more general usability, even for people without disabilities. I personally noticed the lack of a scrollbar when I wanted to check how far through the article I am, but another common use case for th
85.
▲
by
defanor
2y ago
The DEs it uses are GNOME and KDE, which are as far from "simple" in that sense as one can get on Linux-based systems: the two largest (and perhaps most widely criticized for being buggy and bloated) DEs. While the use of uncommon
86.
▲
by
defanor
2y ago
Indeed. I was about to write about it to the author by mail, but noticed that he posted this link, and probably will read these comments, so can as well provide the feedback by joining this subthread: at least a few readers are not happy ab
87.
▲
by
defanor
2y ago
Unless the precision (resolution) is known (stated), it is unclear whether the trailing zeroes are significant or not, one may only guess (while such a guess looks reasonable in this case). A convention for writing that unambiguously is to
88.
▲
by
defanor
2y ago
A few more, which seem to be used somewhat commonly: - Emacs clients: built-in rcirc and erc, non-built-in Circe. - irrsi (standalone TUI) - Quassel IRC (GUI; have not tried it myself, but saw others using it). - mIRC (GUI, for Windows).
89.
▲
by
defanor
2y ago
I think it is about as varied as communications outside of IRC: there are different communities with different rules, which are sometimes written down and linked from the channel topic. Generally hanging around quietly for a bit may help to
90.
▲
by
defanor
2y ago
AIUI, the "Decentralized" added to RSS here stands for: - Propagation (via asynchronous notifications). Making it more like NNTP. Though perhaps that is not very different functionally from feed (RSS and Atom) aggregators: those j
More ›