I think of them as on the same spectrum.

A thin skinned person, is someone when you stab verbally or try to otherwise harm them in a non-physical manner, it goes straight through, and they are hurt by it. It affects their confidence, behaviour and health.

A thick skinned person, is someone you can insult, and they can dismiss the meaning of the words, and be unaffected by the intended harm.

But that is not mutually exclusive with going “wtf, did you just try to stab me?”. They are opposites, in the sense that the word describes whether malicious words or actions can “pass through” and have the intended effect.

But if someone tries to shoot me, and I’m wearing armor that means it won’t kill me, that still leaves the fact that they tried to shoot me. That I was able to survive it does not make the attempt on my life ok. Being thick skinned, or “wearing armor”, doesn’t mean you react to attacks with inaction.

It describes whether you suffer harm when under fire. Not how you behave in reaction to it.

A lot of people think of being thick skinned as synonymous with turning the other cheek. But being able to take BS doesn’t mean you have to passively allow it.

You don’t sound thin skinned.

Having a thick skin doesn’t mean being unbothered by people trying to walk over you, and thereby letting them.

I get accused of being thinskinned sometimes because of starting a confrontation over a problem or behaviour I’ve noticed, but that makes no sense. Being sensitive to issues is not a weakness, and being numb to them is certainly not a strength.

I can push for change precisely because I’m unbothered by the stress of working against the status quo.

But like others said, you don’t always need to convince. If you say you won’t cover a task because it’s not your responsibility, then there is nothing to discuss. If they expect a task to be done even when you said it won’t, that is not your problem.

It’s theirs.

No?

I get that clients might break, but the web portal running inside vaultwarden isn’t gonna suddenly stop working.

Vaultwarden itself is self-contained. An API change won’t do anything to it.

My moms password manager, is just my password manager. (That’s not entirely true, she did figure it out eventually, but for a while there I was simply saving all her account passwords in my manager.)

Why would you mirror, when you could federate?

Wow! Absolute gold.

undue burden on small developers

Uuh, more often than not, the small devs already make their games indefinitely playable and preservable, just out of a love for the medium.

No actual artist wants their work to have an expiry date.

Legal enforcement is only needed for the passionless big publishers that shutter games just to funnel players into purchasing their latest releases.

It’s mentioned in the parliament presentation. Only a small minority of game publishers engage in this BS, but it’s ALL the big ones, meaning the problem is experienced by the vast majority of consumers.

There’s a difference between using AI to apply fixes for problems, and using AI to find problems that you didn’t know about.

Mythos does the latter, not the former.

Ah, no. I’m not familiar with how to do that.

But I wouldn’t think so? I’m more familiar with KDE, but with it at least I’ve always found ways to edit some files somewhere to accomplish what I want.

So far.

For this I’ve just been creating folders and setting their icons manually.

You mean the icons?

At least in KDE dolphin, you can edit any folder and set the icon as whatever you like. It’ll follow the theme color too, if you use the right icon.

The qpwgraph workaround works in the matrix clients as well, but passing media audio into a WebRTC stream meant for voice is not ideal. Any decent client is likely to heavily filter out background audio (which with a game would be a lot of the ambient soundscape), and the audio would in some cases end up mono.

Broadcast-box is on the simpler side, if self hosting. If not, there is a public free-to-use instance here: https://b.siobud.com/

Honestly, that means peer to peer, not centralised

Peer to peer vs a server does not have significant latency difference. There is one, but not one universal enough that’d make latency the reason to choose the former in most cases.

OBS will use large buffers (multiple seconds) that are then sent out to the server.

It doesn’t. Streaming from OBS over WHIP is able to get down to about 300ms of latency, and that’s when watching via a server, rather than peer to peer.

The main source of streaming latency (the buffer you mention) happens when using the older HLS standard.

WHIP or WebRTC HTTP Ingestion Protocol (and the other end for clients, WHEP) allows software like Broadcast-box to be just as fast as conferencing screenshares in peer to peer video calls. Because it is the same tech.

Matrix has MatrixRTC (or whatever they call it) but you will need the Element client and will need to activate RTC in the “labs”. Not sure if it’s in the stable build or the beta.

MatrixRTC voice, video and screenshare is in element, comment and cinny. It does not need to be enabled in labs. Its main problem at the moment is the lack of system audio when sharing the screen.

OBS with Broadcast-box allows you to achieve real-time video sharing with audio, with full control of the video stream audio and quality thorough OBS’s recording and encoder settings. And to watch, your friends need no accounts or anything, they just open the broadcast-box link in a browser.

No?

The fastest I got it down to was about 30 seconds of stream delay. It’s a limitation of HLS, which will never be truly fast.

Owncasts own guides state:

If you require real-time, video conferencing style latency you may want to look for a different solution that doesn’t use HLS video, as this scaling and distribution model will never get to sub-second levels.

Not even. You can share a stream link.

Owncast already mentioned, and while it’s good, it doesn’t achieve real-time streaming like discord does. It’s more of a twitch replacement for streamers with an actual audience thanks to it’s ActivityPub support (in that people on stuff like mastodon can “subscribe” to the server).

MatrixRTC is still new and while it’s already being used to provide voice channels in clients like element, cinny and commet, as of now none of them can stream gameplay with audio.

For this I’m currently using Broadcast-box. Self-hostable, but the dev also provides a public instance.

It uses WHIP to stream over WebRTC (OBS is compatible) to achieve less than half second latency. More than fast enough to feel like “real-time” if in a voice-chat with friends. And you can push the video quality past what any platform like youtube, twitch or discord will allow.

See, I don’t see a difference between what you are describing and most corporate leaders.

I didn’t say a good job.

Nah. It happens when you let an idiot run things.

Mobsters are still organized businessmen. Just criminal ones. They’d do a much better job.

“You know that thing we sell? Buy a shitload of it.”

Having ideas is generally not enough.

Volunteers don’t take requests. They take suggestions. They only act on the ones they want to.

If you want something to actually get implemented, offering a monetary reward, hiring a dev to contribute, or contributing yourself, is the best way to go.

I’ve gotten several features I wanted into software I use, by adding them myself.