Giver of skulls

Verified icon

  • 0 Posts
  • 1.02K Comments
Joined 101 years ago
cake
Cake day: June 6th, 1923

help-circle


  • The value for the end user, the way Apple and Google do it, is that it works on every phone. It was always intended to be the next generation of MMS messaging. RCS, as designed, never had companies like Google run their own servers, but Google had to because many carriers never bothered to set up RCS in the first place.

    Who benefits today? Everyone sharing chat groups with iMessage people. I avoid iMessage but millions of people are stuck with text messaging or ostracised for breaking group messaging (because SMS and MMS are terrible).

    Furthermore, RCS isn’t just text messaging. The standard also contains digital payments and video calls. It’s an open (to carriers) alternative to iMessage that has features ready to go that Signal doesn’t even implement yet.

    Communication is literally what phone numbers are for.






  • As opposed to what? Encrypt them with a key that’s stored elsewhere on the device? Without user prompting (which any malicious app could also do, of course) storing these keys encrypted is very hard. You could use whatever key chain API your platform provides, but that’s just plain text passwords with extra steps. On Windows and Linux it wouldn’t improve security in any way, on macOS it might also not (I don’t know how Keychain access is done on macOS but I doubt it’s impossible to get the key from there if you have local file execution).

    Desktop applications aren’t sandboxed, and the ones that are will only be protected against other sandboxed applications. I’m not sure if encrypting local message databases protects anyone in practice. It just adds half an hour of chatgpt aided programing to the job of the malware devs while the users lose access to their own data.




  • I take advantage of the free disk space savings and don’t worry about disk space much. I’ll clear out my download directory and maybe some caches when my disk usage grows beyond 80% (as reported in GUI tools). Running duperemove across my drive every now and then also tends to help a lot without deleting anything.

    If I do run out of space, there are a few interactive terminal tools that’ll point out the biggest files so I can delete them and save some space in a pinch. I practice, I just don’t really think about it much.





  • df is the standard command line tool to see how much of your disk space is free.

    The problems happen in GUI tools too. Most of the time, they work out in your favour (you think you only have 10GB left but you can put 15GB away) but after a lot of deletes you may “lose” some space until you do a rebalance even through you’d think looking at the stats that you have plenty of space.

    Another issue is that file managers showing you a file’s size often don’t know about compression. You can store a large text file with standard compression on a disk and have it be reported as 100MB while it only takes up a megabyte of space. You can end up deleting a whole bunch of “hundred megabyte files” and save basically no disk space. Other file types, like images and video, often do represent the real size as they’re already compressed, making some 100MB files larger than others. If you don’t enable compression, you won’t have this problem, or course.

    GUI tools also often don’t know about CoW. If you copy a file on BTRFS, the copy action should be instant and take up maybe a couple hundred bytes for the new metadata. To your file manager it looks like you have two 3GB movie files, but in practice they’re just names pointing to the same directory. You can get petabytes of used disk space this way by just making more and more copies, even though your actual disk space barely grows. This also means deleting files may not clear up as much disk space as you’d like.






  • I found both sides rather aggressive to be honest. The implication that the use of “he” implies that the author assumes every user is male comes with an implied accusation of some form of misogyny. The aggressive defence again at the implication went too far, but the implication of malice was unnecessary, especially for an unknown outsider butting in.

    Furthermore, the “generic he” has also been acceptable English for centuries, and has only been starting to be phased out in the past few decades. In high school, some of my English study materials still came from thirty years before, and certainly didn’t contain gender neutral words like “postperson”. Singular “they” may have been around since the 14th century but that doesn’t mean it was commonplace. My native language doesn’t have an equivalent for the singular they, so I’ll probably use “he” in wrong places. Accusing me of not considering female users because I’m not a native English speaker certainly won’t make me want to help you (though I’d probably just ignore you rather than shut you down; then again, I’m not recovering from substance addiction like the original author was back in the day, so that’s not hard for me to do).