No idea what you are talking about… did you get an assignment to implement some CLI program and want ideas for what to do?

If this program was made in a language that supports creating packages for other programs (e.g. Python, Rust, NodeJS), should this program be a ‘package’, or should it be a standalone program that has a simple “setup” script?

I’d assume what you call “packages for other programs” would be plugins? In that case, unless you have a specific existing program you want to write a plugin for, then yours would be a standalone program.

About the “setup script”, if you mean that’s an installer of sorts, then no, your program must not necessarily have an installer (you or others may write standalone installers or packages for various package managers, but that’s another story).

Just try and see how it goes - it’s not like you can’t go back

To me it looks like “we believe in our product” companies are an endangered species

IDK about the current status of x86 with android, but last time I checked it wasn’t good.

Lineage might be your best bet… it supports a few androidtv boxes (most notably the nvidia shield) see https://wiki.lineageos.org/devices/

where SyncThing is overkill

I just have a dedicated shared folder between my phone and desktop and drop oneoff stuff there (it’s also easier to script this way)

For files I use syncthing (also for music/photos/notes/etc… syncing files is IMHO the way to go wherever applicable).

For sending links to my PC (eg. articles linked from podcasts’ notes) I used to rely on firefox sync, but I’m starting to distance myself from Mozilla so I am gonna experiment with wallabang.

For sending small notes to myself (stuff that I want to sort or act upon when I get to my PC), I’m using signal’s “note to self” but I’m investigating alternatives because signal doesn’t mark such messages as unread and so sometimes I forget I’ve sent some.

That’s called dogfooding, not self-hosting :)

Let me get this straight though: I’m not saying no project self-hosts their code (eg. IIRC both KDE and Gnome do), I’m just saying that the majority of FOSS projects (including those that are dedicated to self hosters) does rely on some sort of third party to host their source code.

I don’t think it’s fair to criticize a FOSS project just because they rely on a third party (even commercial ones) to publish their source code.

Yep but eksb’s comment was about selfhosting, not FOSS or ethics (same can be said for this community, although that’s less relevant than the specific comment of course)

Even that is questionable to say the least: while codeberg is the main fogejo contributor, the forgejo project and codeberg are separate entities with separate governance and funding.

I’ve blocked the bot because I find it’s more annoying that useful (I’m not complaining - just giving feedback).

That said, IMHO from that list you should remove the entries that:

• are ambiguous (eg: HA has 2 entirely different meanings in your list)
• have become words on their own (eg. DNS, HTTP, etc…): nobody cares what these expand to (think, NASA) and also knowing what these expand to doesn’t help at all (if you tell me that HTTP means “hyper-text markup protocol” will I not have to go read wikipedia anyways to understand what it is?)
• are often not used according to your definition (eg. IP is more often used to refer to an IP address rather than to the protocol) - of course you may want to amend the definitions instead

Also, you should keep the acronym expansion (“RAID” => “Redundant Array of Independent Disks”) from any comment you may want to add (“for mass storage”) and - since you are at it - provide relevant links to wikipedia articles and/or other resources.

PS: since a lot of entries in the list are not even acronyms… maybe you should consider renaming the bot to something related to “abbreviations” or “glossary”?

What self-hosted software you use is not hosted on some third party forge?

For the fellow community members who are not up to date with the latest AI BS trends:

• if you search for “speckit” you’ll land on https://speckit.org/ “Spec Kit - AI-Powered Specification-Driven Development Toolkit”
• if you’ve never heard of “spec-driven development” it’s because, far from being a noteworthy development practice like TDD or DDD, it’s just another word for “leave all coding to coding agents”

I clicked on them all so you don’t have to (well, so you can better decide what to investigate and what to ignore):

Ratty 3D Terminal
Is the compiz of terminal emulators
https://ratty-term.org/

TheyLive Adblocker
An ublock origin lite fork that replaces ads with slogans from John Carpenter’s 1988 film They Live instead of hiding them
https://github.com/davmlaw/they_live_adblocker

TerminalPhone
CLI messenger (with voice messages) that operates over tor
https://gitlab.com/here_forawhile/terminalphone

Cuda Oxide
“Rust-to-CUDA compiler that lets you write (SIMT) GPU kernels in safe(ish), idiomatic Rust”
https://nvlabs.github.io/cuda-oxide/index.html

Wario Synth
Browser-based midi player + search engine (doesn’t look like you can easily download the midi filies)
https://www.wario.style/

Jmail & EpsteinExposed
Epstein files search engine (seems very US-focused: I tried looking for a few non-US people and found nothing)
https://epsteinexposed.com/

Wikipedia Doomscroller
“pseudo social media feed that algorithmically shows you content from Simple Wikipedia. It is made as a demonstration of how even a basic non-ML algorithm with no data from other users can quickly learn what you engage with” (AGPL)
https://xikipedia.org/

Puter
I’m not 100% sure by looking at the homepage, but it would seem it’s a containerized desktop you can access via web (think webtop)
https://github.com/HeyPuter/puter

Honker
SQLite extension providing functionality similar to postgres’ notify/listen
https://github.com/russellromney/honker

Yes, these are 9 and not 10… Sorry, I only see 9 in “Topics Covered” above and I don’t want to go to youtube (I’ve already wasted spent enough time on this). If you can, pls integrate the list with the 10th project by replying here.

I’ve been thinking about AI and autonomous agents.

These days this is enough to stop me reading, but thanks for saying out that the article is about AI in the first sentence and spare me a click (declaring that in the title would be even better, but first sentence is pretty darn good).

Synchthing if I want local copies, otherwise I just mount sshfs shares from my nas (using sftpman as a helper)

you will have to spend a lot of time learning the Nix language

I’d say you shouldn’t use any system (be it nixos, ansible or even bash scripts) if you are not willing to learn it.

That said, I too find pre-made modules less useful that I initially thought when I got into nixos: unless you want to do very basic stuff, a lot of times it’s easier to just generate whatever scripts/configuration files you need directly (using one of the trivial builders in lib or writing a custom derivation) rather than learning how the corresponding nixos module works.

One could say nixos modules make easy things slightly easier, and hard things much harder (this is adapted - possibly imprecisely - from a quote on ORMs, I think by Joel Spolsky).

In your shoes (and, in fact, in mine) I’d try to move away from interactive tools and into file-driven ones.

Personally I use nixos, run WUD (what’s up docker) to be notified of available updates, and manually test/update the containers once in a while (every couple weeks or so?)

There are a bazillion other solutions (from stuff like ansible/chef/puppet, to docker-compose, to kubernetes, to… a hand-written bash script) - the idea is to setup stuff via files that you can version, reference and write comments in rather than using some gui for interactive steps that you’ll forget to document in some wiki.

Monitoring is a whole different beast than configuring: you’ll be probably better off using something that does just that instead of some all-in-one solution. Try looking into something like beszel before going for the full prometheus/graphana stack.

domain-driven design (or development?)

I’m not 100% what it is (I’m really not into nomenclature), but I think it’s the practice of modeling your software after the domain you are working in… IDK if/how it differs from what everyone has always been doing since forever.

It would seem my point is not getting through (ie. I must not have expressed it well enough).

You having freedom doesn’t mean other people have a duty to support what you do - it just means they don’t have legal ground to stop you.

For example, freedom of speech doesn’t mean that newspaper must publish whatever you write - it just means the police won’t come knocking on your door at 5am because you of something you wrote.

The “idea of linux” (by which I take you mean the idea of FOSS in general, not of the kernel specifically) isn’t to support anything and everything.

Does dropping 32 bit go against the “idea of linux”? Does software being developed/tested only on specific distros go against it? Do devs that only supporting glibc because they don’t care about musl go against the idea of linux?

I’m just expressing a concern where over relying on one init system will limit options

Nope, nothing actually limits the options of people who don’t like systemd: if they want to run some FOSS piece of software whose upstream devs don’t care about openrc (or whatever init of choice), they’ll just have to fork the projects, put the work in, and the upstream devs won’t be able to stop them in any way.

This is what the “freedom” in FOSS means. Twisting it to mean that upstream goes against “the idea of linux” if they don’t support whatever thing you care about and they don’t is entitled.

this doesn’t go with the idea of Linux, which is having “freedom” with your os

Err… it’s “freedom” as in “you are free to run your own system using whatever software you wish” not “freedom” as in “distros and devs have a duty to support your freedom to run any specific software you happen to like”.

Let’s turn down the entitlement dial a bit.