Does it need to be accessible via API (e.g. SQL) or just a spreadsheet-style web interface?

What about the usage demographics within each country?

In underdeveloped/exploited countries, internet usage is more likely to be concentrated among the economic elites who formerly benefited from colonialism—so if increasing adoption in those countries just follows the pattern of other internet use, it could have the opposite effect from the one intended.

You can use any port for SSH—or you can use something like Cockpit with a browser-based terminal instead of SSH.

If you didn’t map a local config file into the container, it’s using the default version inside the container at /app/public/conf.yml (and any changes will get overwritten when you rebuild the container). If you want to make changes to the configuration for the widget, you’ll want to use the -v option with a local config file so the changes you make will persist.

It’s similar to how Adobe Illustrator works—if you leave the default compatibility options checked, saving in PDF or native AI format results in an identical file with the only difference being the filename extension.

Rather than starting from scratch, would it make more sense to make an ActivityPub plugin for the open-source MediaWiki software Wikipedia runs on? MediaWiki already has some “interwiki” functionality that such a plugin could expand on, and you’d have the advantage of being able to fork content from WP and other MW projects without having to re-format it. Plus you’d be able to leverage other MW plugins—Semantic MediaWiki in particular could add a lot of useful functionality to federated wikis, like articles that could query and aggregate information from other federated articles rather than just linking to the text.

“I like it when companies game search engines by titling their promotional pages to mimic search query results.”

The Mac keyboard layout was largely inherited from the Apple ][ and pre-OSX systems, which were non-Unix. The original Unix keyboard layout differs from both Mac and Windows layouts.

That tends to be the outcome of processes like this, and sometimes it is because the agency already decided on policy ahead of time and only asked for public input for the sake of appearances. But in other cases the request for input is in good faith, and industry interests end up dominating the discussion because other voices convince themselves they’d be ignored anyway.

In the case of new industries still in flux, it’s more likely that commercial interests haven’t yet infiltrated the relevant agencies to dictate policy from within—which is why they have to rely on hyperbolic scare tactics and hope no one contradicts them.

From their list of concerns:

The benefits and risks of making model weights widely available compared to the benefits and risks associated with closed models; Innovation, competition, safety, security, trustworthiness, equity, and national security concerns with making AI model weights more or less open; and The role of the U.S. government in guiding, supporting, or restricting the availability of AI model weights

It seems like they’re concerned about both open and closed models, and they’re interested in supporting as well as potentially regulating both.

If the other services are exposed on local ports, you can have NPM forward to those.

Wouldn’t that be Run Lola Run (in that neither the main character nor anyone else is aware of the resetting story line)?

Looper.

There’s a “sort [posts] by new comments” option.

For anyone confused by “Nextcloud” in the title, it’s just the blog attribution—Nextcloud isn’t involved in the acquisition.

Weakness and risk are distinct things, though—and while security-through-obscurity is dubious, “strength-through-obscurity” is outright false.

Conflating the two implies that software weaknesses are caused by attackers instead of just exploited by them, and suggests they can be addressed by restricting the external environment rather than by better software audits.

Interpreting “a previously-unrecognized weakness in X was just found” as “X just got weaker” is dangerously bad tech writing.

To whom are you sending the signal, though?

For most people who don’t already know about the fediverse (i.e, most potential threads users), the first time the concept crosses their awareness threshold will be when threads finally connects and the media start running stories about it. Any attempt to send a signal before that point will be invisible to them.

Plan on defederating with them, but wait until they actually do something that violates fediverse standards (which shouldn’t take long). That’ll raise visibility for the issue with the media and threads users, especially if it’s part of the same news cycle when threads is touting its implementation of the protocol.

As a casual self-hoster for twenty years, I ran into a consistent pattern: I would install things to try them out and they’d work great at first; but after installing/uninstalling other services, updating libraries, etc, the conflicts would accumulate until I’d eventually give up and re-install the whole system from scratch. And by then I’d have lost track of how I installed things the first time, and have to reconfigure everything by trial and error.

Docker has eliminated that cycle—and once you learn the basics of Docker, most software is easier to install as a container than it is on a bare system. And Docker makes it more consistent to keep track of which ports, local directories, and other local resources each service is using, and of what steps are needed to install or reinstall.