Fuck that. First come, first serve. Get it if and while you can.

Pretty sure all the humans left Reddit like two years ago.

If they claim they destroyed everything in the first round, they don’t have a reason to go back.

She wasn’t his girlfriend. He found her interesting because she was a client, and she slept above the covers.

Four feet above the covers.

Technically, its only a hamburger if it comes from the hamburg region of Germany. Anywherr else, it is sparkling beef.

I’ve found Jami from another comment a few hours ago, but I haven’t downloaded it yet. But I think it expects an existing internet/network connection, where Briar seems to be focused on getting messages across through any means available.

I’ve never used it, but I’ve heard of “Jami” that is supposed to operate in a similar fashion.

AFAIK, yes. Latest release is from March of this year, and they have commits as of a month ago.

Are you familiar with Briar?

Works over internet, TOR, local wifi, bluetooth, even “sneakernet”.

Technically, orbit is just forward, really, really fast. “Up” is incidental to the process.

Open source with profanity in comments is statistically better than code without it

For your web browser, Add this to your uBlock Origin block list:

lemmy.dbzer0.com##.title:has-text(/nytimes.com/)

You can add additional sites, separated by pipes like this::

lemmy.dbzer0.com##.title:has-text(/nytimes.com|theverge.com|404media.co/)

(Change the leading url to that of your own instance)

This will turn this:

into this:

So you don’t accidentally get interested in a bullshit paywalled article.

History is written by the victors.

Ok, I’ll try again:

Again a solved problem, just make a decent GUI for your application.

You are promoting monolithic design. You completely fail to comprehend Unix philosophy:

2. Expect the output of every program to become the input to another, as yet unknown, program. Don’t clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don’t insist on interactive input.

GUIs are only used for human/application interaction. They are not needed for application/application interaction. While it is not unreasonable to have a GUI for interactive input within your application, it is infeasible and undesirable for a GUI to be needed for your application to interoperate with other applications.

Go ahead and create the GUI if you really want, but expect your users to want to call it from a shell script. Give users the capability to automate away unnecessary manual interaction, and allow the machine to take up that pointless busywork.

So googling how to do someone, copy/pasting command is better than finding it in GUI?

Oh, absolutely. Especially for a one-off setting that you might never look for again. There’s just no sense in wasting the time building up a complex GUI to handle every possible interaction a user could ever want to employ.

The solution to the “problem” of “needing to use the terminal” is to retrain the user to understand how limiting even the best GUI can be, and to greatly prefer the terminal.

So, my suggestion is, rather than try to hide away the terminal, it should be featured prominently, exposing the limitations and shortage of command line applications available to windows users. An effective, powerful, well-supported terminal is one of the major benefits of Linux.

Are you suggesting users with no programming experience can simply add the flags they need to a terminal application but would be unable to do the same with a GUI because the GUI is the barrier?

Yeah, why not? I’ll go ahead and make that suggestion.

I mean, the terminal allows them to ctrl-c, ctrl-v a simple solution developed by someone else, even if that someone else didn’t bother to build out a GUI for applying their changes.

The convoluted steps they would have to take to achieve the same effect with a GUI would seriously hinder the GUI-only user.

What I am really saying, though, is that the problem of “needing to use the terminal” is not actually solved by ensuring that every possible setting can be accessed and manipulated with a mouse.

I’m saying that the best way to solve this “problem” is by pushing the user to expect and even demand the terminal. Distros should autolaunch a terminal window at startup. Put it right out there, front and center. Invite the novice user to interact with it with friendly little toys like fortune, cowsay, sl, toilet, espeak. The insane usefulness of the various shell tools are more than enough to keep them using it.

BlueShell

With open source, the delineation between “user” and “programmer” is arbitrary and capricious. The GUI-centric Windows approach reinforces that artificial distinction; the terminal breaches that barrier.

Setting search is a solved problem, you simply search for the setting name in the UI,

This assumes the developer bothered to make that setting available through the UI.

With the terminal, that isn’t a problem: You’re using the same UI as the developer.

An effective terminal is a feature, not a bug. Every Linux problem has the same solution: search the web, ctrl-c, ctrl-v.

No navigating through “settings” and “preferences” and “tools” menus to figure out where this particular developer decided to hide that particular setting. Just copy and paste, problem solved.

They mix the mind control chemicals straight into the jet fuel. The pilots don’t even know they are complicit in making chemtrails.

/s