• 1 Post
  • 50 Comments
Joined 11 months ago
cake
Cake day: December 24th, 2023

help-circle




  • Recently, Linux removed several people from their organization that have Russian email addresses. Linus made a statement that confirmed this was done intentionally. I believe that there was some mention of following sanctions on Russia due to the war. I haven’t looked into the details of it all, so take my analysis with a grain of salt. From what I understand, it sounded like it was only Russian maintainers that were removed and normal users submitting code from Russia can still contribute. Maintainers have elevated permissions and can control what code gets accepted into a project, meaning that a bad actor could allow some malicious code to sneak past. This may have also contributed to the decision since this type of attack has happened before and Russia seems like a likely culprit. The reactions to this change have been varied. Some people feel it is somewhat justified or reasonable, some people think that it means it is no longer open source, and some people think it is unfairly punishing Russian civilians (it is worth noting that that is part of the point of sanctions).





  • I’m from the US as well, and I can verify that very few average people use those types of messengers primarily. It is almost exclusively iMessage and SMS/MMS/RCS texts as the main form of messaging. I will admit that quite a few people will use the messaging features that are built into social media apps (like messaging in Snapchat, Facebook Messenger, etc). At least to me, it seems like those are moreso used for sending memes or messaging people you don’t interact with regularly and are still secondary to the other forms of messaging.



  • I had an issue where a client reported a crash on login. The exception and stack trace reported were very generic and lent no clues to the cause. I tried debugging but could not reproduce. I eventually figured out that the crash only happened for release (non-debug) builds that were obfuscated. I couldn’t find the troublesome code, so I figured out which release introduced the issue, then which commit, then went change by change until I was able to find the cause. It turned out to be a log message in a location that was completely unrelated to login. That exact log message was fine a few lines up. Other code worked fine in that location. For some unknown reason, having that log message in that specific location caused a crash in a completely different area of code.


  • I’ve used Bing for a few years for the free rewards points and purchase rebates, and it has worked very well for me when it comes to normal searches including searches for software development. I very rarely have to turn to Google when trying to look something up, and as you mentioned, sometimes Google honestly gives me worse results. I will say however that I have found the image and video search on Bing to be significantly worse than Google’s (which I already have some issues with). Not sure about the other search types like shopping or news since I never use them.


  • It was obfuscated only in the release build. The issue is that they have a system to send certain logs to an API so they can refer to them if a user has an issue that needs further investigation. Unfortunately, their target audience is not very tech literate and have a hard time explaining how they got into a situation where they experienced a bug, so the remote logging was a way to allow us to try to retrace the user’s steps. Some of the logs that get sent to the API have JSON values converted from class data, will refer directly to class names, etc, and those logs had the obfuscated names.


  • I have a somewhat related real world story. I had a client that was convinced that tons of people were going to decompile their application and sell their own version of the program, so they insisted that they needed their code obfuscated to protect company secrets and make it harder to reverse engineer. I tried explaining to them that obfuscation wasn’t that big of a deterrent to someone attempting to steal code through reverse engineering and that it would likely cause some issues with debugging, but they were certain they needed it. Sure enough, they then had a real user run into an issue and were surprised to find that their custom logging system was close to useless because the application was outputting random obfuscated letters instead of function and variable names. We did have mapping files, but it took a lot of time to map each log message to make it readable enough to try to understand the user’s issue.





  • I would say it’s a bit more nuanced than that. I have installed quite a few games on my Deck that have had serious issues that require their own unique fixes in order to work. I had a few games that had shader issues with flashing neon textures that required specific Proton versions to work, a few games that could never get past the main menu due to infinite loading that required reinstalls and using specific Proton versions, and one that required adding some additional commands on the startup in order to avoid crashes. I’ve also run into a few games where the Deck has quirks, such as one I played where the keyboard would cover the game’s text input and the keyboard would appear immediately after closing, which meant you could hardly read what you were entering text for. They do work eventually, so you are technically correct, but they require effort to fix that some people will not feel comfortable doing.