Try qView

For just viewing image files, qView is much nicer. It literally just opens images.

So… Is that kinda like a linux subsystem for windows?

I’m sarcastically referring to microsofts telemetry, UI changes, and anything else they try to sell that a lot of people simply don’t want or like.

I’m on the Index. Afaik steamvr is the only thing that really works on linux.

Ah! A fellow beat saber enjoyer.

Bows in the customary greeting that is visible in multiplayer

I’d argue that a lot of the other “additions” and “improvements” make any improvement in comfort irrelevant, as they are unbearable.

On a sidenote, you can set up a generic bottle in Bottles, and then set things up so that double clicking any miscellaneous .exe files just runs them in that bottle.

Well yeah, you’d still have the limitation that you can’t connect multiple devices at the same time. But the idea is that just like before, nothing is actually stopping you from having as many devices as you like ready to go, all able to be used one at a time.

I already commented on this, but do they actually block you from setting up multiple devices with the same key?

I’ve had my own server node for a while, there’s nothing stopping me from using the same key and config on multiple client devices, as long as I don’t connect them at the same time.

I’m not limited to five keys, obviously, but the keys aren’t device specific. I could set up just one on the server, and then use it everywhere.

Does Mullwad stop this in some way?

That’s a pity.

Is there something preventing you from having the same key ready for use on more than one device? So that two devices that are never connected at the same time can take turns using the same key?

TL;DR They are moving to wireguard only.

I’m ok with that.

Actual game website

Also it’s apparently already being completely destroyed by a cheater.

I know that Thunder lets you “label” users so you can recongize them more easily, and I think you can find a list of labeled users somewhere in the app, too.

so yeah it’s technically always voice-over-IP even if I use the cell network.

It’s not. GSM calls are definitely still a thing, and while VoLTE is becoming more and more common, it’s not universal.

Maybe?

Afaik wifi calling works the same as VoLTE, which afaik is just VoIP, but handled by your mobile provider, and integrated into your normal mobile plan, so it works with your phone number.

When both ends of a call have the service, the call is entirely VoIP, which is how it achieves the much nicer audio quality for these calls.

If you just completely disable the mobile radios (set your phone not to use any kind of connection from the sim settings, while still enabling the sim) and use wifi exclusively, then it should work as if you just have VoIP service?

Read further into the thread.

You are mistaken.

I know it’s about convenience. That still isn’t how whatsapp works.

Using WA you cannot be logged in on more than one device. If you do log in for real, the previous device stops working. All additional devices have to be linked to the first one, and they access the service through that one main device.

You can’t use secondary “linked” devices or sessions if the main device is off. Try it. Open whatsapp web, login, then turn off your phone. The web session will stop working until you turn the phone back on, because it doesn’t actually connect to WA, it connects to your phone. Only your phone is what is actually connected to WA servers.

All “linked” devices/clients/bridges work this way. All available whatsapp bridge software works by pretending to be an additional “device”, and as such suffers all the same limitations.

And Beeber doesn’t do anything special, their systems are based on matrix. In fact I’m literally running the exact same bridge software they do.

Edit: Something has changed. This used to be true. Somewhere along the years WA has significantly changed how their systems work. I can only assume they buffer activity for 14 days and somehow defer the synchronization of content with the main client, because all the same limitations of devices being subordinate to a main session apply.

The most mind-boggling is the alteration that multiple client devices are now allowed, but also not really.

And they still require that user history be monolithically stored by the user, on their MOBILE device. And the only way to have a backup is through their backup solution, and god-forbid you press the wrong button when setting up a new device, because not restoring when the one chance is given, means everything is gone forever.

The main reason I use whatsapp via a bridge, is to have my message history stored on a proper server, so I don’t have to do the restore backup BS whenever I switch devices. I just re-link the bridge and go.

Perchance there’s hope for you yet! Despite this happenstance of negativity.

How did that even work at all? All activity goes THROUGH the WA app. WhatsApp only allows one real client to be connected, all other clients (other devices with the app linked to the first device, bridges, whatsapp web sessions, etc. they all still go through your “main device”). If you turn your “main” phone with the whatsapp app off, for example, all others stop working.

Looking it up, the bridge connection expires without activity at least every fourteen days to keep your account active in general. As long as you allow the app to run (which it has to do anyway, because that’s how WA works) it’ll do that on it’s own I think, no need to open it every fourteen days. Or at least, I’ve never had to. My bridge connection is literally over a year old, and I’ve definitely gone months without opening the actual WA app in that time.

I run my own instance and bridges.

I use fluffychat on mobile. Though I also have element installed as fluffy doesn’t support all message types, and has some bugs despite the nicer (imo) UI.

As for the battery drain of element, that’s something you’ll have to look into yourself. One of my own qualms with matrix atm is that there’s no really excellent mobile client for it… It’s all kinda meh. There’s element which is feature complete but has a bunch of issues, or there’s stuff like fluffy, which is nicer, but not feature complete, and still has issues.

Ah. I guess you might remove some metrics or some such that way, but that’s not a very transparent way to achieve that unless you dig in personally.