Huh, I missed that when skimming through the post and source code

I am considering implementing my own ActivityPub server to remove the dependency on a Lemmy server to get votes,

I saw that part and misunderstood it as if he didn’t run an instance.
Thanks for pointing it out!

Honestly surprised you’re able to get lemmy votes without an admin account, I thought that data was restricted to instance admins.

It’s not leak when it’s an intended and documented feature…

You can pry my fishing rights from my cold dead hands!

Norway just like Switzerland are too rich cool to join the club, we are still a part of the European Economic Area and Schengen though.

Can’t read the tweet as Twitter is blocked on Firefox, but my guess would be closer ties with NSA, i.e. NSA can exert more control and monitoring of the data openai collects.

Sure, but what random psycho would go through all your comments collecting data like weather on a specific day, car, job, etc… just to mess with you in real life. That’s like one in a billion unless you specifically seek out those kind of people.

What sort people are you trying throw off your trail? Genuine question as I’m not a frequenter of privacy communities.

Unless you’re a investigative journalist, what are the odds details such as weather, car, type of job would be compiled by someone to identify you?

Impulse? Got a similar mail yesterday for my gym too, doubt I’ll bother until my card stops working. Cards are simply more reliable than apps.

I think the idea is to make it easier to detect trolling/spam from certain accounts. But honestly, there’s no reason upvotes and downvotes can’t just be public.

Frankly, for anything other than real-time encoding, I don’t actually consider encoding time to be a huge deal. None of my encodes were slower than 3fps on my 5800x3d, which is plenty for running on my media server as overnight job. For real-time encoding, I would just grab a Intel Arc card, and redo the whole thing since the bitrates will be different anyways.

Encoding speed heavily depends on your preset. Veryslow will give you better compression than medium or fast, but at a heavy expense of encoding speed. You’re not gonna re-encode a movie overnight on slow preset. GPU encoding will also give you worse result than CPU encode so that’s something one would have to take into consideration. It’s not a big deal when you’re streaming, but if it’s for video files, I’d much prefer using the CPU.

I consider the ‘good enough’ level to be, if I didn’t pixel peep, I couldn’t tell the difference. The visually lossless levels were the first crf levels where I couldn’t tell a quality difference even when pixel peeping with imgsli. I also included VAMF results, which say that the quality loss levels are all the same at a pixel level.

I was mostly talking about how you organised your table by using CRF values as the rows. It implies that one should compare the results in each row, however that wouldn’t be a comparison that makes much sense. E.g. looking at row “24” one might think that av1 is less effective than h264/5 due to greater file size, but the video quality is vastly different. A more “informative” way to present the data might have been to organise each row by their vmaf score.

Hopefully I don’t come across as too cross or argumentative, just want to give some feedback on how to present the data in clearer way for people who aren’t familiar with how encoding works.

Feels like certain information is missing. You get very different results both in encoding time and file size depending what preset you use.

CRF value also can’t be translated 1:1 between codecs so comparing e.g. h265 CRF 21 to h264 CRF 21 doesn’t mean much.

Web browser/Firefox supports the same thing, but I appreciate the suggestion

No ads

That’s strange, I thought they were automatically synced to your mobile browser when they became available. Thanks!

Still waiting for sponsorblock