3,447 karma · joined July 6, 2017
Having distinct tools for serving content and handling certs is not a problem, and nothing changes on this side. Moreover, the module won't cover every need.
BTW, cerbot is rather a "fat tool" compared to other acme tools like lego. I've had bad experiences with certbot in the past because it tried to do too much automatically and it's hard to diagnose – though I think certbot has been rewritten since then, since it has no more dependency on python zope.
I doubt this practical value exists. The paper completely forgets one important element¹: having a single rider at the front saves the energy of the teammates. If a team was to put two riders upfront and then the chase takes more time than expected, they have no backup. And even if the strategy was to succeed and the leader gets back into the peloton, he/she will have two tired teammates instead of one, which means a reduced help for the remaining of the stage.
I also suppose pro teams already know all of this, even if they didn't have the precise benchmarks of this paper. It's just unpractical most of the time. For a diamond shape, the aerodynamic gain is pretty obvious, but with a high price to pay in order to protect a rider.
As a side note, the paper authors should learn about PDF metadata. It's quite ugly that the file's title is "Microsoft Word - 2025_Preprint_Formations_V2".
[¹]: Except when they quote a cycling specialist about the goal to "reduce the leader's effort without sacrificing too many team members".
I have 2 small complaints:
- I sometimes read some dubious content on MDN. For instance [JavaScript frameworks and libraries]^1. I don't think these tutorials for 5 frameworks provide any value over the respective official tutorials. Even more so with outdated tutorials: the Svelte one is 5 years old, and there have been major changes since then. ^1: https://developer.mozilla.org/en-US/docs/Learn_web_developme...
- The quality of the webextension doc is low. A clear problem is that it's mostly for manifest v2, with a few incomplete pages mentioning a transition to v3 or the compatibility with Chrome. In practise, I started developing an webextension with this doc, then had to switch to Chrome's, though Firefox was my primary target.
Any change can introduce regressions or break habits. The move toward socket activation for sshd is part of a larger change in Debian. I don't think the Debian maintainers changed that just for the fun of it. I can think of two benefits:
+ A service can restart without interruption, since the socket will buffer the requests during the restart.
+ Dependencies are simpler and faster (waiting for a service to start and accept requests is costly).
My experience is that these points largely outweigh the downsides (the only one I can think of is that the socket could be written in two places).
sshd still reads /etc/ssh/sshd_config at startup. As far as I know, this is hard-coded in the executable.
What Debian has changed happens before the daemon is launched: the service is socket activated. So, _if you change the default port of sshd_ in its config, then you have to change the activation:
- either enable the sshd@service without socket activation,
- or modify the sshd.socket file (`systemctl edit sshd.socket`) which has the port 22 by default.
Since Debian already have a environment file (/etc/default/ssh), which is loaded by this service, the port could be set in a variable there and loaded by the socket activation. But then it would conflict with OpenSSH's own files. This is why I've always disliked /etc/default/ as a second level of configuration in Debian.
jj rebase -r @ -B abc
the recommended Git alternative is: git rebase -i abcd1234
# move the last line to the desired position
This is a process I use heavily, and one of the rare cases where I prefer the Git way: less cognitive load (I don't need to memorise options b/s/r/d/A/B for `jj rebase`) and the interactive editing of the history feels simpler (especially if I move several commits).I've used jj for a few weeks, but switched back to git. I'm fluent enough with Git so I never struggle any more. jj mostly felt nice, but the added value was not enough to replace years of expertise.
A few years ago, they changed their interface for downloading. This introduced more than a dozen of bugs. Some were cosmetic, e.g. hover was the same color as foreground. Some were rare but caused a file loss. Some were performance related, e.g. deleting the history of downloads could take a minute with no visible change until the end. Most of these regressions are now fixed, but that made me lose confidence in the quality of Firefox.
This year, I had to develop a cross-platform extension for Chrome and Firefox. I started using Mozilla Documentation Network, but many pages seemed unmaintained. The relationship with extensionworkshop.com is unclear. The status of manifest v3 is poorly documented (most pages are for v2 only). The page about the compatibility with Chrome is incomplete. After a few struggles, I switched to Google's documentation. Then I lost time and energy on a severe bug with the Firefox tool that publishes web-extensions: https://discourse.mozilla.org/t/webexterror-unsupported-file...
Fun fact: this is completely wrong. The cinema theaters were much more popular in the 1920s and 1930s, with about 3 times more tickets sold in the USA (out of a smaller population).
"In 1930 (the earliest year from which accurate and credible data exists), weekly cinema attendance was 80 million people, approximately 65% of the resident U.S. population (Koszarski 25, Finler 288, U.S. Statistical Abstract). However, in the year 2000, that figure was only 27.3 million people, which was a mere 9.7% of the U.S. population (MPAA, U.S. Statistical Abstract)." in Pautz, The Decline in Average Weekly Cinema Attendance, Issues in Political Economy, 2002, Vol. 11. https://ecommons.udayton.edu/cgi/viewcontent.cgi?article=102...
The main difference appears to be that Garnet is more parallel, according to this student's report of benchmarking various keystores (see the "CPU usage" sections in the PDF) https://www.diva-portal.org/smash/record.jsf?pid=diva2%3A196...
Their recommended process is :
1. Install fasttext (it's an official Debian package, but you have to compile it on Windows).
2. Download and uncompress the LanguageTool release.
3. Create a config file.
4. Launch the server with the java command (of course, a JRE must be installed).
5. Connect to the API, e.g. with the browser extension.
Running a ready-made docker image replaces steps 1-4 and removes the need to install Java globally. Some will prefer it this way.
I've never encountered the word "Pre-Arabic" about the Arabic peninsula. It would be hard to define precisely. The word "arab" is probably more than 3000 years old. The Arabic languages may be older ; they're semitic languages like the Akkadian of Mesopotamia. And when did an "Arab" people or culture emerge from the semitic people and culture? I guess between 6000 BP and 3000 BP, but it was probably a long process, and nomad tribes didn't leave many vestiges.
> now that there is journald, you have to pay attention to another hop in your logging chain and take care of journald in addition to rsyslogd.
No, you don't have to, because a syslog daemon is not required any more. BTW, rsyslogd is not the only syslog service, I've had to work with alternatives like rsyslog-ng.
And the daily usage is now much simpler: `journalctl -b -1 -p err` or `journalctl -u mariadb --since "24 hour ago"` were painful queries with (rotated and compressed) syslog files.
> Boot and shutdown has previously been deterministic, now things just randomly hang.
That was not my experience. IIRC, with sysv-init boot dependencies were declared with comments inside shell scripts and parsed by insserv. That was a mess, and race conditions did occur. I have no experience with other boot systems, but I remember that upstart was not immune either.
> Network device naming is also a fun one.
The naming policy is vaguely relevant to systemd. `net.ifnames=1` is the default configuration of the Linux kernel. I think it's still possible to configure the kernel, udev and systemd to work with the old naming, but if it's just because "shorter is better", I don't think it's worth it.
I'm not a scholar, just an amateur, but two sentences were strikingly ridiculous.
"Legend has it that Noah hid them here from the floodwaters before boarding the ark." This article is supposed to be popular science about Babylonian archaeology, why mix it with a Hebrew myth derived from an older Mesopotamian myth? I guess it's just because Noah appeals to the ambient Christian culture. In other words, it's nonsense, but it sells.
"The information about the women of Babylon, their role as priestesses and the associated tasks, has also astonished experts, as no texts describing these things were previously known." There are many many texts about women and Naditu (sacred women) in Mesopotamia and in Babylon. According to the scholar article : "The passage has great importance for understanding the roles played by the various classes of priestesses: ugbakkātu, nadâtu, and qašdātu." Quite different.
Where did you get this information? Is it just a guess based on what Apple declared about these domains?
In the article, there is no info about the content sent to these Apple owned domains. For all we know, MacOS could send detailed reports on the user's activity.
This is an opinion that I've often read, but that does not match my limited experience. The difference in quality between BSDs and Linux is not clear. I've found outdated documentation on both sides, though BSDs mitigate this by being more stable (i.e. less innovative, if you prefer looking at the dark side).
For instance, a blog post was recently describing struggles with the NetBSD installer. It complained that the documentation chapter about installation was 7 years old, and about obsolete releases of the OS and its installer. https://eerielinux.wordpress.com/2025/05/31/installing-bsd-i...
Another example, this time with FreeBSD. The documentation still has a section about floppy disks, and the chapter about "Linux Binary Compatibility" is for Linux 3, about 10 years ago. Hard to tell if these pages are still valid.
> In New Zealand, soft plastics are mostly recycled into fence posts
The latest (2025-01) official report[^1] I could found states that the recycling of plastics in NZ is poorly known. On page 135, it mentions the report "OPMCSA plastics research (2019)" as the reference in the domain.
According to that 2019 study[^2], the plastics used each year weight more than 700k t. Much more, because this ignores packaged imports, construction and agriculture. 31% of plastics imported are LDPE (so around 170k t), which is mainly used for producing soft plastics.
Out of those 600+k t/year, 380k t go to landfill waste, and 45k t are collected for recycling. Assuming generously that 50% of those intended for recycling are actually recycled, I'd estimate that 1.7 to 3% of the yearly NZ plastics are recycled.
Here's a quote about soft plastics:
In 2017, 365 tonnes of soft plastics were recycled – but a lack of recycling market for these plastics meant that in the following year, plastic was stockpiled whilst new onshore markets were developed and a percentage of non-conforming plastic was landfilled.
365 t of soft plastics recycled out of 170k t of LDPE![^1]: https://environment.govt.nz/assets/publications/New-Zealand-...
[^2]: https://www.pmcsa.ac.nz/topics/rethinking-plastics/quantifyi...
> 28 statues that portrayed the biblical Kings of Judah. [...] They didn’t portray French kings
That's wrong. Several texts from the revolution and before still exist that prove that these kings were identified as both Judea kings and France kings. For instance, David was Pépin le bref. On one of the gates of the cathedral, the List of the French kings was engraved, starting with Clovis. That glorification of the monarchy, with parallels to the bible, was common at the time: other French medieval cathedrals show the same analogies.
Yes, I agree that some public organizations in France are making progress with Open Source. For instance, free software is now common in universities (with local variations). And overall I think there's a central influence of the DiNum ("Direction Numérique", the Digital Department of the French State) in this direction. But I don't see how this UN charter makes any difference.
There's progress, though not related to this charter. And so slow that I would bet against "Open Source" becoming widespread in French schools within the next decade.
> Facts (and code) are following.
I'm sorry, but the current situation and the past experience makes it really hard to believe that facts will follow from this charter. At least facts matching the claim that the French government will be "Open by default: Making Open Source the standard approach for projects" (quote from the first point of the charter).
If "France endorses UN Open Source principles", it shouldn't just mean that it will publish some code. It should means that it intends to respect these principles, and that proprietary software becomes the exception within the French administration.
I can't believe this post is more than symbolic, because the French law already promotes Open Source and forbids non-UE proprietary software in many public contexts. But these laws are usually not applied. Why would a non-prescriptive charter do any better?
Two months ago, the French government signed an "open bar" contract with Microsoft for the "Éducation Nationale" department. 152 M€, not for Open Source. Source (fr) https://www.april.org/nouvel-open-bar-microsoft-le-ministere...
A few days after that, a major state-owned institution (Polytechnique) announced it was migrating (including the email system) to MS Office 365. Even if it violates several laws and official decrees (it's a semi-military school). Source (fr) https://cnll.fr/news/polytechnique-men-office-365/
For music, I'm not even sure the cultural creation has increased.
A few decades ago, there were scores of indie bands. In high school I knew a few friends that were playing in amateur rock bands. Later on, when I traveled in foreign lands, most people I met listened to local music, e.g. Turkish songs which were a mix of tradition and modern influence. In my latest travel, everyone was listening to the same globbish junk.
I don't have any stats, but I suspect the music production is more homogeneous and less creative. There is less geographic variation. At least one source of creation has disappeared: musical bands are dead, except for the industrial kind, à la K-pop. Overall, I don't think the creation level is higher than 25 years ago.
> 2. The algorithms were developed to help with this problem. They are just a poor match for the problem.
I disagree with the OP that the algorithms are necessarily bad. For instance, once in a while, they could suggest a very different style to help broaden your tastes. Some already do that.
But algorithms can't compare with recommendations by friends. There were music that I would have instantly rejected if the CD hadn't been given by a friend. And sometimes you have to persevere and learn to like a music. When the curator is a human I like, I try harder.
I didn't enjoy much Ovid's books, but Homer was wonderful. The Illiad often surprised me. The human characters and their connections with gods are so intriguing. But it's mostly dark — a hero can seem nice then behead an unarmed prisoner. And I remember vividly when a river was so upset by all the atrocities of the furious Achilles that it flooded the battle ground to stop the massacre.
I haven't read the books, but the presentation by this holocaust museum was not informative. For instance, it fails to mention a relevant fact: some people earned their academic position to their activity in the party.
And, most of all, the existence is irrelevant without some prevalence. I would be very surprised if the established scholars that "actively embraced Nazi ideology" were a majority. From the Vietnam wars to nowadays, there have been US academics that embraced war or actively supported genocides, but I think most academics and students are less heinous or indifferent than the average population. That's why some German scholars were oppressed by their government, even when they were not Jews, and chose to emigrate.
So, when I care about a book, I never read Standard Ebooks' edition.
By the way, the modernization is more than joining a few words. Sometimes, Standard Ebooks replaces the word used at the time the book was written. For instance:
This time, however, the mountain was going to [-Mahomet;-]{+Muhammad;+}
The previous quote is from Galsworthy's "Forsyte Saga". The author used many French words and French spellings – like "Tchekov" for the Russian playwriter that was living in Paris. These subtleties are lost with the modernization.I also think some alterations are plain mistakes. For instance in the same book:
if she wanted a good book she should read [-“Job”-]{+Job+};
his father was rather like Job while Job still had land.I hope the American influence won't make this practice more common in British English. But it's not just about the country: The Washington Post has sane titles, like every British newspaper I've read, while The New York Times Has Elite Titles With Many Big Letters.
I can think of two explanations: (1) Debian packages have more shared parts, and (2) they have optional dependencies ("recommends" and "suggests") which I disable by default. Because of (1), there will be many library packages to download, but the overall volume is reduced.
Without the Wright brothers and Santos Dumont, aviation might have been created a few years later, but, overall, the consequence would have been small.
I think the section named "Pathname" is wrong. It describes the path of an URL as if every server was Apache serving static files with its default configuration. It should describe how the path is converted into a HTTP request.
For instance, the article states that "all of these go to the same place : https://example.org https://example.org/ https://example.org// https://example.org//////////////////". That's wrong. A web client send a distinct HTTP request for each case, e.g starting with `GET // HTTP/1.1`. So the server will receive distinct paths. The assertion of "going to the same place" makes no sense in the general case.
Xit will be compatible with Git (1), with different internals (2). It will embed a TUI (3) (Git has dozens of those but no official TUI). It will embed an alternative to Git-LFS (4) (which is ubiquitous, but no part of the offcial Git client). And (5) Undo, the really new feature (jj has a more limited `undo` command).
[meta] The page is hard to read for me: a monospace font, and a lack of contrast for my partial colorblindness. So I hit the shortcut to switch to "reader mode", but nothing changed.
I had a look at the HTML, and it's among the worst I've ever seen. Each character in its own `span` with a class matching its position on the line. The text is handled like a matrix of letters. I had to fiddle with the Developer Tools to make the text readable.