Any way to prevent save files being shared by different Steam users on distros that depend on steam?(SteamOS/ChimeraOS/HoloISO)
ChristianWS
1 Post – 118 Comments
Joined 1 years ago
Not going to lie, I hate the middle click clipboard and disable it ASAP. I really dislike the idea that it copies things without my explicit permission.
As far as I know, Flatpaks have the best foundation currently, there are a number of issues, but they are fixable and not entirely by design. And with Fedora Silverblue/Kinoite and OpenSUSE MicroOS you can really see how native debs/rpms/whatever isn't really that good of an idea for the average user and Flatpak is a solution to that.
Appimages at a glance seems like a perfect solution for apps that for some reason or another needs to be kept outdated. But there is (was?) an issue of it not really bundling everything it needs, it looks and behaves as it is portable, but as far as I'm aware, it really isn't.
And then there's Snap. Yeah, that one is just weird, it honestly just doesn't feel like a proper solution to any of the problems it tries to fix.
Really hope the Rif dev creates something for Lemmy, last I heard he was going to develop for another social network
I always use Flatpaks when available, I have been using it for about 1~2 years and honestly, I haven't found any issues that are deal breakers, mostly some missing storage permissions, but KDE makes this easy to deal with. I know some apps have some issues, but the biggest one that I had is that Steam Flatpak still requires Steam-Devices to be installed as a package, but that's more to do with the way Steam Input works.
The only issue that I have is that uninstalling Flatpaks should present an option to delete the app data.
Keep in mind that because MicroOS, Leap Micro and Aeon have icons already set, this means that whoever design the rest will be restricted by the currently existing ones.
Like, both MicroOS and Leap Micro have a horizontal line and a circle in the middle. And Leap Micro basically forces a new design of Leap logo to be almost exactly like the previous one. And Aeon has the middle circle of Micro, but split into two, so Kalpa should also have the split circle somewhere.
That said, I'm not exactly a fan of the MicroOS, Leap Micro and Aeon logos. They are just outlines, and very thin. I understand that logos need to work in monochrome, but they are just.... Anorexic. Would prefer if there was an entire rebranding
It makes me really mad cause YouTube is clearly taking ideas from Material Design 3, and even M3 recommends customizing it, but the way YouTube has done it is to make components smaller and harder to use in comparison to canonical M3. Like the bottom bar which is way thinner than the M3 one in comparison.
It makes YouTube look like it's using a M3 knockoff
A family member always downloaded and installed APKs from the internet and didn't know about the Play Store cause that is how you did things on Windows.
The person is question has low tech literacy, and they were doing this for years
I'm really looking forward to the clone app feature being backed into AOSP. Hopefully LineageOS gets updated pretty soon as it was the case with Android 13
But I use KDE because of the separation that title bars offers
Even if a social network loses 99,99% of the user base due to charging to use it, those left are the ones that see no problem paying to use it, so they are more likely to eat up some insane pricing, which would help recoup losses from a smaller user base. Basically whales.
I think the only way to try to kill a social network is by going full scorched earth on it. Remove all your comments, or change them to be an annoying copy pasted comment about why you're getting off the platform. And even then I don't think it is helpful, I did that with Reddit but was forced to leave technical posts intact because I feared I might prevent someone from solving their issue.
Power users live in a weird paradox state, cause they are the most likely to even find a well hidden feature, and yet, they always complain even when all that was added was a dialog asking for yes or no
So one big disk for your Steam library and whatever you play might be slow on the first load but then as you play the game files gets promoted to the NVMe cache and perform mostly at NVMe speeds, and your loading screens are much shorter.
I really love/hate how you can immediately understand the practical application of new technologies through the use of games.
I will copy a comment I made a week ago in another thread:
It was five years after her first Android phone that I noticed that when asked to install an app, my aunt proceeded to download an APK from a random website and installed that rather than using the Play Store. In fact, I think she didn't even know the Play Store was a thing, and she was on her third android phone already.
She isn't tech-savvy, she did that because that is how she did on Windows. After that, I just accepted that things need to change in a way that might annoy me.
That is to say that while the solution found by Google has a bunch of drawbacks, and I'd prefer if old games and unmaintained apps were left alone, I don't think it was a totally wrong decision (this time).
Devices for LineageOS and I then use the official website to validate it, as well as GSMArena Phone Finder
If you use Flatpak from the start, the storage thing becomes less of an issue.
Flatpak only takes considerably more space because people use Flatpak as a last resort or too late into the life of the current installation, as flatpak will have too many requirements for too little apps.
I'm mostly using Flatpaks on Tumbleweed, I only use the package manager if I can't find a Flatpak version. Reason for that is that with Flatpak I can precisely know what I manually installed, as Tumbleweed lacks a proper easy way of getting a list of user installed packages
Alright, a few things:
- Removing a direct QS tile for Wifi and Mobile Data was a dumb idea from Google's part, and there is no defense for that. I'm on LineageOS and I have the option to add those two back, but I think this isn't something that came from AOSP.
- The Internet QS Tile is actually a pretty good idea for the average user. Most of the time when you want to disable Mobile Data you want to enable WiFi, and vice versa. This adds one more step, but removes one QS Tile and condense Internet options into a single thing. I'm fairly sure this wouldn't be a slight controversial decision if not for the removal of the direct QS Tiles.
This is the second post this week that mentions the iOS control center and I'm confused by it. On Android, the bottom area uses a upward gesture to go home and/or Recents, that's why the Quick Settings and Notification are on the top.
How does the user go to the homescreen on iOS since the bottom area opens the control center?
Really wish the RIF is Fun would migrate to Lemmy, but it appears he's going to move to another service
Far from it, but there are things that appear obvious or properly explained, only that in reality, it is not.
Android 14 is making ADB necessary for really old apps(or ones that deliberately target old APIs to circumvent restrictions). That one is annoying, but makes sense.
That's not to say I'm a fan of every decision, for instance I don't like that Google removed the ability for apps to toggle WiFi and Bluetooth, that should be a permission. But it is really surprising how non tech-savvy folks can screw up basic stuff we think are well hidden.
This is an issue I've been wondering about, the Technology example is fine, but the real edge case IMO is Official Communities.
Like, let's say I have an Android App and want to migrate my official community to Lemmy. I could build a community in:
- A big and general instance to gather more users, like Lemmy.World.
- A big but themed instance, like Lemdro.id. It has a smaller number of users but they are more likely to be interested in my App
- I could make my own instance, which would allow me to dedicate communities into topics and I would have more control over it, which is good cause it is an official community.
I feel there should be a way for "sync" communities in those cases. It makes sense in those cases to allow a full sync, with the option to unsync if things go south and there's a split.
I'm loyal to my wallet
I'm actually pretty excited for this version due to app cloning being added to AOSP, as well for predictive back, but IMO that will be something that will take a couple of years before it gets going to the point where we couldn't imagine living without it.
Android 13 that was rather eeeh, but that one was mostly a refinement over 12
I have a bunch of issues(some way smaller and borderline nitpicks) with windows, but I guess there's some big ones:
-
Linux runs smoothly on older computers, even with KDE which everyone talks about as if it was heavy. Windows is a slug in comparison.
-
Linux is free, truly free. Microsoft can't beat that.
-
Shit just works (unless you are on Nvidia...), don't need to install drivers and shit like that.
-
most of the software you don't get from a random website and they all update at once, rather than having each one update itself and only itself
it interferes with the ability to open drawers
It's funny, but I tried looking around the old Material Design guidelines and I haven't come across any mention of swiping to open a drawer. I know it was on Android Developers, but it appears that from the point of view of the design team, it wasn't really "officially" recommended?
Regardless, Discord, IMO, offers a better implementation for side sheets, as the metaphor isn't that you drag something from beyond the screen into view, you just drag the view itself to the side and that reveals the side sheet. And it works in the middle of the screen so it doesn't interfere with the system gestures
Also cloned apps which is big for me
It was five years after her first Android phone that I noticed that when asked to install an app, my aunt proceeded to download an APK from a random website and installed that rather than using the Play Store. In fact, I think she didn't even know the Play Store was a thing, and she was on her third android phone already.
She isn't tech-savvy, she did that because that is how she did on Windows. After that, I just accepted that things need to change in a way that might annoy me.
I remember the small outrage that happened when Google stopped officially calling Android versions by desserts. Nowadays I can't imagine going back.
It was always weird because it only became clear with Android 6 (Marshmallow) and 7 (Nougat) that Google stopped making major versions with x.y numbers, with x.1 being exception. You couldn't just ask someone if they were on Android 4 cause there was at least 3 major Android versions, so it was easier to use the dessert names.
It was also weird having to wonder if you should translate the dessert name when speaking casually about it.
I love the minimize all windows button. It is so small and functional, I always use the KDE Widget that copies it, and IMO, KDE should use it by default
Issue is that Immutable also conveyed a different type of information. When I first heard of it, I genuinely thought it was something like DeepFreeze for Windows
This website provides a better explanation and use cases than anything I could write. Some of the highlights:
- Newer games that run too slow at the resolution you would like them to run at (you can render games at 720p and play at 4k)
- Very old games insisting on running in a tiny (like 320x200) window (ie. xrick).
- Games and applications who insist on running full-screen with no option to make them appear in a window if a window is what you want for a particular game or application (many scene demos will only run full screen at your current resolution).
- Running older, non-widescreens games that do not support borderless fullscreen on Intel graphics with a desktop/external display (this is because Intel graphics do not support the --set "scaling mode" "Preserve aspect" xrandr argument on desktop/external displays)
Interestingly, Gamescope also provides a way to independently set max frame rate for the game when it is focused and unfocused, you could set it up to something really low when unfocused. Also interesting is the upscale options, you could use integer scaling for those old games, or force FSR on any title (although results can be mixed because the game UI will also be upscaled).
Gamescope becomes a very interesting option when you use it on a machine that doesn't have easy access to a keyboard and mouse, like a handheld, a "consolized" PC or even a "normal" PC that double duties as a "console" (playing games on a couch, despite using a desk for normal usage)
Like, I remember a friend of mine saying he had trouble running Sonic Generations on Windows because depending on what he was doing, he was either playing it on a monitor or on a TV. The Game for some reason detects that change and throws a fit, asking the user to reconfigure its graphical settings. Gamescope can lie to the game and force the game to see an arbitrary resolution.
I just flash LineageOS even when the device is currently supported by the OEM. I buy the hardware from them, not the software.
Edit: Like, the vast majority of actual custom ROMs users are either using Pixel Experience or LineageOS, there are a bunch of other ROMs, but those are mostly "purpose built" for enthusiasts of what they offer. Like, GrapheneOS is for security reasons, and things like that.
There is a bit of headache installing custom ROMs, but once you install it, it is usually pretty stable. Also, I don't get the locked vs unlocked bootloader thing in regards to security. The device is stolen and outside your hands, it is doubtful that a thief would go through the steps of flashing a ROM, but wouldn't be smart enough on how to make the device unusable if it had a bootloader locked. Either way you are screwed.
If you meant physical, clickable buttons, then yes, I agree with that and I miss the early days of Android where we still had them, the Galaxy 5/Europa was really fun to use and I miss it.
Never really liked the virtual buttons that much. As phones get bigger and bigger, they started making less and less sense. With gestures you can reach the back function by holding the phone anywhere on the screen. And the home and recents function are available anywhere on the bottom of the screen rather than having dedicated places.
One thing that might be a game changer once developers implement it is the predictive gesture, which would transform the back gesture into something analog, and I can imagine some cool uses for it that can't be done with buttons. It would also help give feedback for more complex apps and stuff like that.
That said, gestures live and die by the feedback, and to this day I think the best one was done by FluidNG, as it felt like you're pulling a black goo from the screen edge. The rest always felt a downgrade in comparison. The Android 14 one looks better than previous ones, but it still doesn't hold a candle to FluidNG
I'm running on an i3-2310M with 4 GB RAM without issues, I'm on Linux, tho
- Redmi Note 10
- It was cheap
- OLED screen, lack of Notification LED and real proximity sensor
Issue is that developers are honestly, kinda of dumb in regards to the menu gesture, and AFAIK there wasn't an actual "canonical" guideline for that gesture in the first place.
Discord offers the best implemention in my opinion, as it can function on the middle of the screen and not on the edge, so it doesn't interfere with system gestures.
Spotty internet on both sides of the equation. It is common enough to happen.
If your WiFi is weird at the moment due to ISP side maintenance, or if you are on the edge of the signal, you might want to disable wifi and enable mobile data.
On the other hand, you could simply not have enough data left in your plan, so you want to keep your phone from using Mobile Data, even if you might get out of range from your router.
A bunch of design decisions only makes sense when viewed on a smartphone and even then, only after a little bit of usage.
I remember I disliked Android 12 visual design when I looked at it through screenshots, but then absolutely loved it when I started actually using it
I always thought Sync for Reddit looked cool, but never found myself comfortable with it because RIF existed, and I always felt more comfortable with it.
I'm now using Sync and it is pretty great, but in my case it required some UI fiddling. It looks like Material Design 3, but I feel there's something wrong with the default values for font and text size nothing that is unfixable, but just... Weird
KDE Connect on KDE distros, just feels part of the KDE experience