Some servers choose not to connect with each other.

Those servers have users and since they choose not to connect, there will be disparity.

Let’s say I’m on server ‘a’ and you are on server ‘b’ and this post is on server ‘c’

In this example, we can say that a and b connect with c, but a and b don’t connect with each other.

We would both independently see the post on server c, and we could both leave a comment. But since a and b don’t connect, we wouldn’t be able to see each other’s comments. The people on server c would be able to see both of our comments though.

This connection is called federation and it allows individual servers to control who they interact with.

Lemmy is just a piece of software, the people running the software on their servers control who they connect with. you could for example have multiple federations that comprise tons of servers that have no direct connection at all, resulting in two totally different networks.

Cli doesn’t make much sense to me either when the *arr suite has a well documented rest API already.

The bridge just creates imap/smtp servers, so you should be able to add it to thunderbird on Android.

I’ll take the L… but I’m gonna blame it on sleepyheadedness, lol.

A resume with no PII, how are they gonna call you for the interview?

And what is the point of encrypting it? If they can’t decrypt it then you just sent them a jumble of bits, and if they can, then what was the point?

People generally don’t like being proselytized.

Sounds like EEE to me, but it seems a little too early in the cycle for that.

I hate writing and reading xml compared to json, I don’t really care if one is slightly leaner than the other. If your concern is the size or speed you should probably be rethinking how you serialize the data anyway (orotobuff/DB)

You need to tell it to run the script

Weirdly enough, messages seem to be the only thing I see the general public being ok with diversifying.

Everyone I know uses different messaging apps, I have active conversations in signal, telegram, Whatsapp, messages(SMS), messages(RCS), discord, and matrix.

Can this solution deliver 3+ streams of high resolution (1440p or higher and 144fps) low latency video with no artifacting and near native performance and responsiveness?

Gaming has a high requirement for high fidelity and low latency I/O, no one wants to spend all this money on racks and thin clients, the then get laggy windows and scrolling, artifacts, video compression, and low resolution.

That’s the problem at hand with a gaming server, if you want to replace a gaming desktop with a vm in a rack, you need to actually get the I/O to the user somehow, either through dedicated cables from the rack, fiber, or networking, the first is impractical, it involves potentially 100ft long runs of multiple display port, HDMI, USB, etc, and is very rigid in its application, the second is very expensive, shooting the price up to thousands of dollars per seat for display port/USB over fiber extenders, and the third option I have yet to see a vnc/remote solution that can deliver near native video performance.

I should reiterate, the op wants to do fidelity sensitive tasks, like video editing, they don’t just need to work on a spreadsheet.

None of the presented solutions cover the aspect of being in a different place than the rack, the same network is fine, but at a minimum a different room.

How do you deliver high resolution (e.g. 1440p, 144 fps) to multiple monitors with low latency over a network? I haven’t seen anything like that accomplished without running fiber from the host.

Eventually, your thin client will need too much power anyway, making the costs rise a lot. It makes sense in an office where you have 500 seats and you can load balance resources.

If someone can show me a multi seat gaming server that has native remote performance (as in you drag windows around in 144 fps, not the standard artifacty high latency behavior of vnc) I’ll eat a shoe.

Disco Elysium comes to mind.

Yes smartphones and tablets have replaced desktops for most general users.

This is something people fail to realize, and I think part of it is because Linux people tend to surround themselves with other Linux people.

I have been helping my friend get into Linux, we picked a sensible distro, fedora, with the default gnome spin. He loves the UI, great.

But there is a random problem with his microphone, everything is garbled, I can’t recreate it on my hardware and it’s unclear.

He reads guides and randomly inputs terminal commands, things get borked, he re installs, cycle continues.

He tries a different distro, microphone works, but world of Warcraft is funky with lutris, so no go.

The result is, all of this shit just works on windows, and it just doesn’t on Linux. Progress has been made in compatibility, but, for example, there was a whole day of learning just about x vs Wayland and not actually getting to use the computer. For someone who has never opened a terminal before, something as simple to you and I as adding a package repo is completely gibberish

Yes you can learn all of this, but to quote this friend who has been trying Linux for the past two weeks “I’m just gonna re install windows and go back to living my life after work”

When you have 20 years of understanding windows, you need to be nearly 1 to 1 with that platform to get people to switch.

I didn’t know about alien, that is pretty cool.

However this bit from the readme is hilariously on brand for Linux:

"To use alien, you will need several other programs. Alien is a perl program, and requires perl version 5.004 or greater. If you use slackware, make sure you get perl 5.004, the perl 5.003 in slackware does not work with alien!

To convert packages to or from rpms, you need the Red Hat Package Manager; get it from Red Hat’s ftp site. If your distribution (eg, Red Hat) provides a rpm-build package, you will need it as well to generate rpms.

If you want to convert packages into debian packages, you will need the dpkg, dpkg-dev, and debhelper (version 3 or above) packages, which are available on http://packages.debian.org"

Also Linux’s package ecosystem are not cross compatible.

I think mostly people are defending themselves, when Linux people jump on the harassment train, it’s just that, harassment.

So your solution is to buy back into banking infrastructure at a fee?

What about something like groceries, oil changes, metro cards, hospital bills, mortgage payments, rent, gym memberships, cash only business, payroll, or anything else that is actually needed by people.