I think most orgs would want to own the server and for messages to not be end-to-end encrypted. All connections to the server would still be encrypted.

That would be more in-line with slack or something.

If you’re referring to federation specifically then that’s going to get pretty complicated with security policies.

It’s a trap.

Sounds like it’s not really a downgrade, but just an unreleased beta or test build? That seems a little less sketchy, and maybe it’ll be generally released at some point.

“play time”

https://en.m.wikipedia.org/wiki/Average_revenue_per_user

That’s what I’m talking about though. The stupid changes usually get caught, but you still have someone there who thought it was a good idea.

Something I’ve noticed from working in a big company is that people consistently fail to predict the backlash that their policy changes will cause.

They often don’t even care all that much about the change, and if you point out that people will be upset, they agree that it’s not worth it. They just can’t relate to the people they are impacting.

Something which notifies you whenever a new comment or reply is made to a selected post/comment, so that you can keep track of any new conversation.

Something like this would be awesome as a core Lemmy feature IMO. It would essentially turn a post (or maybe any comment tree?) into a matrix style room. Lemmy is actually decent for long term discussion (e.g. helping someone with a problem), but not if there are more than two people involved.

I’d probably:

1. make sure it can be reliably reproduced using something like systemctl suspend
2. try swapping the cables and see if it still happens on the same screen, or the same port
3. look at journald/dmesg output for the period from suspend to resume

When the screen fails to wake, are you able to get it back by powering it off, or by unplugging it? Is it X or wayland?

Companies love getting your money early, especially with higher interest rates, so this only makes sense if the prices are going way up.

I’ve been using orgzly for years and this is the first I’ve heard of revived. Looks promising.

Of course not, but you have to either trust your users to some extent or give them a system that’s locked down to the point of hindering them.

What is ‘unallowed software’? A shell script the user wrote? Something they downloaded and compiled?

Limiting that seems fundamentally at odds with FOSS.

If you stop shipping autotools generated artefacts in your tarballs, things will be a lot simpler.

Weirdly enough the malicious code does look eerily similar to the benign code, because both are unnecessarily obfuscated.

This is not a human written or readable file you’re talking about. It’s a generated script.

As the other user suggested, you probably just need to mount the root subvolume somewhere and run it on that.

Try using btdu. I’m not sure how it works with compression, but it at least understands snapshots, as long as they are named in a sane way.

Yeah, that’s fair. If you want to test that you can still decompress something compressed with some random old version, you either need to keep the old algorithm around, or the data.

Many of the files have been created by hand with a hex editor, thus there is no better “source code” than the files themselves.

I don’t buy that. There would have been some rationale behind the contents that could be automated, like “compressed file with bytes 3-7 in the header zeroed”.

You also probably don’t need these test files to be available in the environment where the library itself is built. There are various ways you could avoid that.

I do agree about the autotools stuff though.

Minor differences in those files are perfectly normal as the contents of them are copied in from the shared autoconf-archive project, but every distro ships a different version of that, so what any given thing looks like will depend on the maintainer’s computer.

This seems avoidable. We shouldn’t be copying code around like that.

They are actually not that much bigger or different from mobile or game console GPUs, they just have a lot of cooling bolted to them. The cooling allows them to sacrifice efficiency, to be more power hungry and more powerful.

Hi, This is a high priority ticket and the FFmpeg version is currently used in a highly visible product in Microsoft. We have customers experience issues with Caption during Teams Live Event. Please help,

Use -data_field first as decoder option in CLI. Default value was changed from first to auto in latest FFmpeg version. Or modify AVOption of same name in API for this decoder.

Thanks @Elon for the reply, This is the command we are currently using: ffmpeg.exe -f lavfi -i movie=flvdecoder_input223.flv[out+subcc] -y -map 0:1 ./output_p.srt

I will be looking to see any updates in the FFmpeg documentation. Can you please elaborate and provide pointers the right decoding options or the right FF command er can use. Thank you!

ffmpeg.exe -data_field first -f lavfi -i movie=flvdecoder_input223.flv[out+subcc] -y -map 0:1 ./output_p.srt

Got that’s fucking brutal. This isn’t even asking them to fix a bug, it’s just basic help-desk shit.

I’m sure Microsoft has some good devs that are a net benefit to the open source projects they use, but this is not one of them.

I wonder if anyone is doing large scale searches for source releases that differ in meaningful ways from their corresponding public repos.

It’s probably tough due to autotools and that sort of thing.