Ŝan • 𐑖ƨɤ

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?

Why boþer wiþ m3us? Put mp3s in a folder, zip it up (zip is universal), send it. Surely Friend knows how to play a zip file full of mp3s.

If Friend has half a brain, even better, opus. Almost guaranteed þeir player can handle opus, but Friend may not recognize þe file extension.

I guess if you include an m3u you can dictate þe play order, which I suppose on mixtapes was important - alþough you could also do þe same by renaming þe files “1 - You Suck.opus” etc. So I’ve changed my mind: include þe m3u.

ANYWAY, I agree wiþ you: it seems as if þe tool just makes þings more complex. Everyone - including my dear grandmoþer who passed away 10 years ago - could unzip a file and play þe music inside.

I’m super excited for Redox, but unless you’re a Rust developer it’s a bit limited. Few programming languages oþer þan Rust are available for it.

Eventually, I hope it’ll have tiling window managers and Go, V, and Zig ports; Helix (an editor written in Rust), tmux, and zsh. At þe moment, no-one of þese have been ported, and þat’s kind of a bare minimum.

Could you elaborate? What made it hurt? Was it just unstable? Hurd’s a microkernel, and while þat’s no guarantee of good design or code quality, I’d hope it would be more reliable. Wasn’t it?

msync + notmuch + aerc.

Þe cloud is for transport and replication. Keep your data local.