Oof. I didn’t get that far. They really mention DEI in the project README? That’s going to be a hard no from me. Even if I did agree with them, it has no place in the repo.

Big oof. I should have finished reading.

Wait, what? How did politics come into this? Did they talk about DEI in the README? I didn’t read the whole thing.

That would be disappointing.

I mean, read the github README. The author is claiming that there are people trying to sabotage progress on X11.

If there are folks actively working on a fork, then it’s not deprecated, is it?

Ok. This is interesting, if a bit conspiracy-theory-ish:

moles from BigTech, are boycotting any substantial work on Xorg, in order to destroy the project, to elimitate competition of their own products. Classic “embrace, extend, extinguish” tactics.

Right after first journalists began covering the planned fork Xlibre, on June 6th 2025, Redhat employees started a purge on the Xlibre founder’s gitlab account on freedesktop.org: deleted the git repo, tickets, merge requests, etc,

I wonder what the story behind this is. Why would anyone want to hinder progress on X11?

Are those thumb keys not angled? Could you describe them, or sketch with Paint, or something? Because those thumb keys look angled.

Good choice. I’ve been running Radicale for years, reverse proxied behind Caddy, and it’s been solid.

Very probable! When replying, my client only lets me see the comment I’m replying to, so losing track of who said what is a common problem for me. I assumed you were OP because I didn’t think anyone else was advocating for Plebbit.

Naw, there are several good use cases for blockchain. Ask a blockchain hater how to implement an auditable change log, and they’ll re-invent blockchain and claim it’s not.

I’m only saying: you specifically mentioned Bitcoin, and then later said design goals included cryptocurrency integration. I’m not opposed to crypto, conceptually - I’m just giving a possible reason why you may be garnering downvotes.

Because there is no such thing as a universal standard for software.

You’re imagining a way for software to talk to each other with something like Esperanto, right? Some universal library interface, a language that can be compiled for every CPU architecture, byte ordering, and operating system.

This would require all hardware vendors to agree on what that interface is, for each type of device. It would require that the API never changes, or else old devices wouldn’t work with new OSes; the alternative is that OSes have to support years of different versions of the language. It would prevent bug fixes, unless you add the ability to flash individual chips, which would make many more expensive. It would have to be a higher level interface which would limit both innovation and performance tuning. But the biggest issue is that this universal language would have to understand every operating system to know how to access itself using the OS’s paradigm.

Sure; I’m saying that there are trigger words that are guaranteed to generate negative comments: blockchain, crypto, crypto currency, and Bitcoin.

You said that you can’t understand the negative feedback. I’m giving you one reason why you might be seeing it. Lemmy and Mastodon (the AP FediVerse in general) is not cryptocurrency-friendly. If you mention “Bitcoin” in the post, you’re going to get brigaded. If someone sniffs around on the repo documentation and sees the crypto link, they’ll mention it in the comments and you’ll get brigaded.

I think there’s such a knee-jerk reaction to any mention of crypto currency, even in comparison, that even a whiff of a relationship generates negative reactions. As you say, much of it is based on no actual knowledge about the topic. It doesn’t help that there are some truly deplorable people associated with cryptocurrency, a great many bad actors, and proof-of-work was in retrospect a terrible design decision by Satoshi.

Blockchain isn’t cryptocurrency, and vice-versa, but most people can’t distinguish between the two. If there’s any mention of blockchain on the site, or especially if you mention bitcoin (as you did) you’re going to get crusaders.

Thank you, I’ll check them out.

I never considered that Alaska might be less serviced than other states, given how removed it is. It’s no Hawaii, but still.

My problem has always been finding a SIP company I wanted to give my money to, for providing a land line #. For a glorious, brief, period, I was able to do this through Google Voice. But then they got rid of that feature, and I haven’t found another provider who I like the looks of.

Oh, most of the “old” programs are all well-behaved. It’s just a crop of more recent tooling; I seem to encounter more frequently ones that either barf if they can’t understand the terminfo, or always generate terminal codes that need to be cleaned out.

It’s not just me. I think I have a shell function defined to strip control codes, but after trying to build it myself a while ago I ended up stealing someone else’s that was more complete. The fact that it’s easy to search for and find Q/A about this is a pretty good indication I’m not having a singular experience. IIRC, even the fairly complex perl script I eventually ended up with came with a disclaimer about there being edge cases it didn’t handle.

My understanding of escape codes is that there’s really only a handful (0x1bNNm) and they should be easy to strip, but there are complexities like being able to compound codes (0x1bNN;XXm) that make it more challenging. That’s about where my knowledge ends.

I just know it’s occasionally a PITA when I want to process data.

Oh! One example is immortal. immortalctl always dumps control characters and is impossible to reliably grep.

This person Unicodes

LogSeq has other note types; it’s just the default is bullets.

LogSeq is about as future proof as you can get. Notes are stored in a directory tree as markdown files.

Maven and later gradle, groovy and spring boot really made it more fun to use.

There is no better example of “to each their own.”

I started programming Java professionally when it was still called “Oak.” I was working at a University doing distance learning stuff and applets were incredible. They were also the thin end of the wedge, although I didn’t know it at the time.

I watched over the years as a nice, concise, core library of a dozen packages swelled like a bloated corpse. The last core library book I contributed to was larger than War & Peace, a veritable tome just to describe the standard library.

And then tooling like Maven and Gradle came along, and frameworks like Spring Boot became unavoidable, and I found more of my time was spent not programming but trying to detangle some horrible maven build config. In XML. That’s about the time I jumped ship.

My philosophy is: tooling is fine, but if it takes over the project so that it’s impossible to build the project without it it’s not tooling anymore, it’s a framework - a platform - that you’re locked into. You get to spend your time debugging issues with the framework, over which you have no real control, where your best hope is work-arounds and crossing your fingers that upstream fixes their shit before your work-around becomes permanently engraved into the build.

It’s funny to me that what I saw as bloated distraction, a hateful corruption of simplicity onto layers of obfuscation that themselves became platforms needing maintenance and debugging, would have been a pleasant and even fun addition to the ecosystem.

Oh, yeah. This doesn’t surprise me. There’s barely any nod to accessibility, and all of that’s in desktop functionality. A braille terminal sounds like an utter nightmare, especially with more recent, “modern” tooling that insists on colorizing output, or self-managing paging. Libraries like Bubbletea make for some pretty output, but it’s downright hostile for screen readers.

This is an old problem, too. I can’t count the number of times I’ve furiously wasted time cleaning up output from a program that insisted on using terminal color codes. And I’m fully sighted.

Try it, it’s good. There’s a mobile app, for Android, at least. It’s free; it only takes a little time investment, so low barrier for entry.