Prometheus/VictoriaMetrics/Grafana are pretty good, had no issues with it and there’s an exporter for damn near anything. They’re pretty easy to custom write too.
Note: do that from a live CD/USB or with the source drive mounted readonly. If you dd a mounted and used filesystem, you’ll most likely end up with a corrupted and useless filesystem on the target.
I get that you can’t stop people from commenting on your posts but you can still filter it out from the results.
Mastodon is arguably easier to deal with since you’re replying directly to someone, so the user’s server can reject it and be done with it. On Lemmy it really should behave as if you blocked the user: just hide it from view. Simply because if you’re on instance A, blocked instance is B and the community is on C, B has no problem posting to C as it doesn’t know you’ve blocked it on A. But even defederation doesn’t address that either: you can reply to defederated users and they’ll never know for the same reason.
I think on this type of social media, not seeing it is the best you can do regardless.
They even used to be the best drivers, a long time ago when nobody cared about the graphics stack. Had ATI/AMD? You got the FGLRX proprietary driver and it was really bad.
12 years ago it was probably one of the least broken GPU drivers available. You actually got most of your GPUs capabilities.
Now with Intel and AMD going open-source, those are now the best drivers and NVIDIA is lagging behind and not keeping up with advancements in the Linux graphics stack. Hopefully the open driver and NVK catches up and brings everyone a good open-source NVIDIA experience so we can stop relying on the proprietary driver.
Yeah, if I see “Steam Deck verified”, I expect the game to work 100% out of the box. Although I guess a “playable” rating might have been more appropriate, but with online mode being so popular I’m sure there would be tons of complaints if Valve said it worked perfectly.
I think it can also get weird when you call other makefiles, like if you go make -j64 at the top level and that thing goes on to call make on subprojects, that can be a looooot of threads of that -j gets passed down. So even on that 64 core machine, now you have possibly 4096 jobs going, and it surfaces bugs that might not have been a problem when we had 2-4 cores (oh no, make is running 16 jobs at once, the horror).
I have none of that on my phone, just plain old keyboard.
But the reason it’s everywhere is it’s the new hot thing and every company in the world feels like they have to get on board now or they’ll be potentially left behind, can’t let anyone have a headstart. It’s incredibly dumb and shortsighted but since actually innovating in features is hard and AI is cheap to implement, that’s what every company goes for.
That file looks like it’s barely playable in general.
FFmpeg and MPV can’t play it at all:
<span style="color:#323232;">max-p@desktop ~ [123]> mpv https://lemmynsfw.com/pictrs/image/f482b4d7-957a-4ed7-a9ec-0493907a8cb3.mp4
</span><span style="color:#323232;"> (+) Video --vid=1 (*) (h264 576x1024 30.000fps)
</span><span style="color:#323232;"> (+) Audio --aid=1 (*) (aac 1ch 44100Hz)
</span><span style="color:#323232;">File tags:
</span><span style="color:#323232;"> Comment: vid:v12044gd0000cp23h1vog65ukmo9lhkg
</span><span style="color:#323232;">Cannot load libcuda.so.1
</span><span style="color:#323232;">[ffmpeg] Cannot seek backward in linear streams!
</span><span style="color:#323232;">[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 1, offset 0x30: partial file
</span><span style="color:#323232;">[lavf] error reading packet: Invalid data found when processing input.
</span><span style="color:#323232;">[ffmpeg] Cannot seek backward in linear streams!
</span><span style="color:#323232;">[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 1, offset 0x30: partial file
</span><span style="color:#323232;">[lavf] error reading packet: Invalid data found when processing input.
</span><span style="color:#323232;">[ffmpeg] Cannot seek backward in linear streams!
</span><span style="color:#323232;">[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 1, offset 0x30: partial file
</span><span style="color:#323232;">[lavf] error reading packet: Invalid data found when processing input.
</span><span style="color:#323232;">[ffmpeg] Cannot seek backward in linear streams!
</span><span style="color:#323232;">[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 1, offset 0x30: partial file
</span><span style="color:#323232;">[lavf] error reading packet: Invalid data found when processing input.
</span><span style="color:#323232;">[ffmpeg] Cannot seek backward in linear streams!
</span><span style="color:#323232;">[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 1, offset 0x30: partial file
</span><span style="color:#323232;">[lavf] error reading packet: Invalid data found when processing input.
</span><span style="color:#323232;">[ffmpeg] Cannot seek backward in linear streams!
</span><span style="color:#323232;">[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 1, offset 0x30: partial file
</span><span style="color:#323232;">[lavf] error reading packet: Invalid data found when processing input.
</span><span style="color:#323232;">[ffmpeg] Cannot seek backward in linear streams!
</span><span style="color:#323232;">[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 1, offset 0x30: partial file
</span><span style="color:#323232;">[lavf] error reading packet: Invalid data found when processing input.
</span>
VLC seems to be able to, but it complains that it’s not proper:
<span style="color:#323232;">max-p@desktop ~> vlc https://lemmynsfw.com/pictrs/image/f482b4d7-957a-4ed7-a9ec-0493907a8cb3.mp4
</span><span style="color:#323232;">VLC media player 3.0.20 Vetinari (revision 3.0.20-0-g6f0d0ab126b)
</span><span style="color:#323232;">[00005ca01d39d550] main libvlc: Lancement de vlc avec l’interface par défaut. Utiliser « cvlc » pour démarrer VLC sans interface.
</span><span style="color:#323232;">[00007ea2f413f5c0] mp4 stream error: no moov before mdat and the stream is not seekable
</span>
Some players are more generous in what they tolerate but the file is undoubtedly mildly corrupted.
Lemmy should not let people upload corrupted files in the first place.