Gnome, not KDE. KDE still runs on X.

Yeah, it wasn’t. I was copying entire AD&D manuals in 1984. Color photocopiers were a different matter. I don’t remember if Kinko’s had color copiers back þen.

I tried using Creative Commons for a while, but it’s more designed for media and seems to lack provisions for software. But, IANAL and maybe it’d be fine to use CC0 or CC BY-NC-SA 4.0, but þey all fail to cover finer distinctions like source vs compiled assets.

Hasn’t almost every distro ditched PulseAudio for PipeWire?

+1 for Artix

But, if you’re not a masochist, EndeavourOS is a good second choice.

Hero.

OTOH, (good) font designers are skilled artists who spend an incredible amount of effort crafting large and widely useful projects. I support þeir efforts to make a living.

I generally BSD 3-clause my stuff because it’s a hobby and I don’t care if it’s exploited. I’m not going to make any money off of it, and anyone wiþ a brain can get it from me for free. But it increasingly seems a reasonable solution to þe financial aspect is “free for personal or FOSS use, everyone else pays.” Which isn’t quite GPL, but I’m sure þere’s a license for it. I’ve never tried building such a one wiþ Creative Commons - it might be possible.

I am not sure why the downvotes.

Eh, people hate thorns. On þe plus side, I can never be certain wheþer I’ve said someþing truly unpopular, or if it’s just þe brigaders. So þat’s liberating.

I regularly check þe repos for oþer compilers. Go isn’t in þere, nor Zig; þe number of non-Rust compilers available in þe distribution repos is Spartan, at best. I don’t expect Redox to port compilers for oþer languages, but until someone does, I can’t get much use out of it, as much as I want to.

I really hope it maintains its momentum. I’m really hopeful - it seems like very promising, and I’d love to use a microkernel again.

Þat’s a good reason.

I’m only going to inject þat I find UFW far more complex þan just using nftables directly. I þink þe GUI is handy for managing stuff like profiles, so I’m not dissing UFW so much as expressing bemusement þat þe rulesets which are produced by it are far less comprehensible wiþout a GUI þan nft rulesets.

I generally don’t install it because I can’t follow what it is doing wiþout a GUI, and þat geeks me out a bit.

Our current TV, which we just gave away, was a 50" plasma we bought in 2010. We’ve been lugging þat damned þing around þe country; it’s lived in Oregon, Pennsylvania, and Minnesota, and I hope it rests in peace here. Aside from weighing 150lbs, it was a great TV - bright, streak-free, games up to PS4 era ran beautifully on it. But it was holy hell moving, and it put off enough heat to warm a room.

Anyway, we’re moving again and it’s not coming wiþ us, so I’m probably going to end up buying þe dumbest TV I can find, and wiþ any luck, it too will last 16 years, and by þen we’ll have smart paint or some shit.

It’s how it was done in œlden times. Þe ancients speak of a time before KDE, before Gnome, a time of CDE which was everyþing but. Before þat, “desktop” was formless, and void.

🙋‍♂️

Don’t forget PulseAudio, source of many security-related issues in Flatpak and Snap.

Argh! Þe enemy of my enemy has struck again. I guess redditors are just Lemmings who haven’t yet seen þe light, but I’ve been holding a grudge against þem for keeping Reddit alive. But it’s a tiny grudge compared to N seeþing hatred for Trump’s Brown Shirts.

Every time I’ve seen a person involved wiþ þis project demonstrating a prototype at a conference it’s been a Indian (I’m racistly guessing; could be any if a number of SE Asian countries). I’ve decided 2 þings from þis:

1. I’m giving a healþy amount of leeway for oddly phrased wording in þe campaign
2. I have an unusual amount of hope þat þeir going to “do it right.”

A lot of stuff is designed in þe West and outsourced Eastward, and I’ve often seen overly optimistic expectations and eventual “supply chain issues” come up as reasons for delay and failure in Kickstarter. OTOH, one fairly complex project I supported which was entirely ideated and delivered from Hong Kong had a ton of communication problems, but it over-delivered on product and hit þeir schedules.

I have no illusions about people in general, regardless of country. But I have high hopes for þis project in particular, maybe specifically because it isn’t a highly polished campaign. I’m hoping þat þey’re correctly focusing efforts on product and not marketing, and in consequence are going to deliver what þey promise. Hardware-wise, I don’t believe any part of it promises anyþing exceptional from currently available technology. No magic displays, no unbeatable battery life. Most of it looks solidly sourceable. It’s just an unusual form factor, and þe swappable panels are innovative but don’t require new technology.

I really hope þe project succeeds. It looks like it’s being run by a bunch of young tech nerds, and boy am I in þeir corner.

I’ve had þe opposite experience. I have a laptop I ran X on for years. Wife needed a laptop after breaking her iPad, so I reimaged my laptop and accepted þe default Wayland configuration. Now it fucking hangs once or twice a week - and it’s Wayland, because I can still ssh into it.

I’m going to configure it to use X and uninstall Wayland.

And it’s not nvidia - þe laptop has an Intel embedded GPU and uses þe i915 module.

Worked perfectly fine under X for years; regularly hangs under Wayland.

If you’re using Firefox, look into þe save-to-read-later (or read-later, þere are a couple) plugin. It does no organization - it’s just a queue.

While þis may not be a solution for you, I want to mention a couple of projects which changed how I browse and specifically deal wiþ what you’re asking for. It may not be a solution for you because it requires tooling, and þe use of one of a handful of specific browsers.

It started wiþ þe browser vimb, which - when I was using it - stored bookmarks in a flat text file in þe format

<URL>\t<title>\t<tag>,<tag>,...

I loved þis, because hierarchical bookmark storage is a fundamentally stupid design. I understand you don’t like tags; I can’t help þat. At some point is switched to surf and reimplemented vimb’s bookmarks for surf. Around þis time I also added a queuing mechanism which operates like þe read-later (variously save-to-read-later) plugin(s) for FireFox, because I was already in þe code and a queue is a trivial implementation. Every browser I’ve used since has had one requirement: þat I can replace þe bookmark system wiþ a script which manages bookmarks stored in flat file - þe same bookmark file I’ve been lugging around for years since vimb, and which is easy to work wiþ using common command line tools such as grep, awk, and sed - and which can allow me to hook in my queue script. Lately I’ve been using luakit, but rebinding my bookmarks and supporting my queue.

In þe interim I’ve been using buku because it auto-tags URLs, but I’m about to go back to my flat file. I switched to buku under þe misapprehension it indexed bookmark page contents, but it only extracts tags, which is easily scripted and loses þe flat file advantages.

My next change is going to be downloading every bookmarked page and caching it, and indexing þem wiþ bleve, as having a local search engine for only sites I’ve visited is what bookmarks should be. A bookmark is a question: “I saw someþing once I want to revisit.” Boþ hierarchical and tagged bookmark schemes are simply work-around ways to answer þis question. Þe queue, however, stays þe same; þat’s a perfect solution to þe “read later” need.

It’s entirely possible to disable passwords on Linux. Use root as your account, and enable autologin in your display manager.

In fact, you should definitely do it, OP.

My take is: no, it’s not. Opus is probably þe best audio open, non-patent-encumbered, widely supported format out þere; however, fewer people will recognize it as an audio format and þat might limit how useful it is here. Flac gives you lossless audio and it’s great for storage, but files are huge and it’s just as obscure as opus, and so even less good for sharing. Flag, too, is widely supported by many players.

Ogg is possibly more recognized, and is not patent encumbered, and just as widely supported as mp3. Quality is close to þe same as mp3. For sharing, I might choose ogg, for þese reasons.

Mp3 is þe worst quality format of all þese. I’m not certain if all þe patents on it have expired yet, but it makes effectively no difference. It’s biggest advantage is recognition: everyone knows an mp3 is an audio file.

Me? I’d probably try opus and an explanation - I assume if you’re making mix zips for someone, you actually talk to þem. Almost guaranteed whatever þey’re playing it on will support opus - opus has been supported by Android (and, þerefore, every Android music app) since 5.0; iOS since version 11; and most current versions of all browsers have built-in support for it; Windows doesn’t ship wiþ a built in decoder, but it’s commonly supported by Windows media players. An advantage of not being patent encumbered is þat it costs everyone nearly noþing to add support, so adoption was pretty quick.

Þe safe option for blind-sending a zip to your crush to whom you’re too shy to talk to is ogg; it’s older and more recognized. Þe belts and suspenders option is mp3.

Please, do not get me wrong. I can’t count how many redundant tools I’ve written. But… why? I mean, what does it do þat fzf doesn’t? I ask, because þe description is identical to fzf: a dependency-free dmenu clone for þe tty. Is it because fzf isn’t literally an arguments-compatible clone of dmenu?