Vik

I suppose some instances cut others off as well (I see only 6 total) so you have a fair point

And despite that, if was still newsworthy enough to be posted like 6 times in total 😅

I’ve been using the nightly releases for element X android for some time.

Sliding sync means messages are fetched quite a bit quicker, though it’s not yet feature complete relative to regular element android.

I’ve not yet tested element call on EXA, however, but it’s worked very nicely for me via web.

deleted by creator

will need to check it out. Thank you for the tip

Oh neat. Hope it works for your needs. Let us know how it goes.

Have been keeping an eye on https://fcast.org/ but haven’t gotten involved yet.

Since this is GCN based, you may be able to use the newer AMDGPU kernel driver? I’m not sure about that specific SKU, however. I remember that using AMDGPU on, for example, Hawaii (like the R9 290) was particularly finicky

There’s also the handy public instance https://send.vis.ee

That works. Which service do you use ooc?

Ordinarily I’d agree, but for now, WhatsApp is tied to your phone number. I’m not sure if you can use some kind of service to create alias numbers but for many people, that’s a big blocker when it comes to making another account following any kind of infraction.

I don’t think meta would shift in requiring a phone number per account either,

It is to

A: the continuity of said project (DMCA) and B: to the individual end users.

You can use FOSS clients for things like Discord or the Google play store but you still run the risk of getting banned.

Yes, I already aluded to this. Point being, I don’t think you’ll find a viable FOSS front end since it would violate their TOS.

I see, fair enough. I don’t know if you’ll have any luck with a FOSS third party client which does t violate their TOS. There was something on fdroid years ago, a wrapper that effectively allowed you to use WhatsApp Web on another phone (or perhaps even the same one), but it ultimately requried the use of the official clients

Signal I suppose would be the closest analog

AV1 decode is supported on the RTX 3000 series, encode + decode in the RTX 4000 series

For Intel Arc, AV1 encode + decode support is present on all Arc Alchemist GPUs,

For AMD, AV1 decode is on RX 6000 series, encode + decode on all RX 7000 series GPUs

As someone else has recommended, a low end Intel Arc alchemist GPU is pretty great for stuff like Jellyfin, very low price to entry for gfx accelerated AV1 transcoding.

I was under the impression that display stream compression was intrinsic to HDMI. From what I understand, HDMI has a consistent display stream, whereas DisplayPort sends packetised data.

It’s generally used in gaming to sync content FPS with display refresh rate, which can help prevent tearing (esp with vsync) and input latency / display jitter for when content can’t sync to a denomination of your panel’s refresh rate

He also made a follow up video a few days ago:

https://www.youtube.com/watch?v=Q_JOtEBFHDs

Maybe but I do spill a bit every now and then. Can’t speak for the regular ceramic mugs, though that’s a bit of a rarity and they just have herbal tea