Teams, RDP/UDP, FICIX, Google, Python, Tracking, Security

  • Went through several usability issues of Microsoft Teams @ Wikipedia. Many aspects of the app are so badly done, it's more like trolling that bad code? It seems that they don't consider usability and consistency issues at all. Even completing same action repeatedly can lead to different end result and so on. It's just so bad, that it makes me sad. (It could make me mad in theory, but it's really not worth of it. It's just better ignore extremely bad software, than getting mad about it for no reason) - As example, first time you share document / gif (Upload from computer), it's shown in the message as expected. But second time when you share the same content, which is already uploaded to the OneDrive, it isn't shown anymore, but now it's link to OneDrive. Why, what does it matter what the source for content is? Phew. Maybe the problem with Teams is not "eating your own dog food". That's the way to deliver really repulsive software, because it's so bad, nobody wants to use it and you won't be getting any feedback which could (at least in theory) lead to better software.
  • Confirmed that the unreliable UDP RDP connection doesn't get disconnected even when streaming 4k video over RDP. Which pretty much moots the claims that it would be any kind of packet rate limit related issue. The problem is caused by something else.
  • Many Finnish ISPs peer on FICIX, of course. But then many are split between peering at LINX, AMS or DE-CIX. Which can be sometimes bad, if you're using ISP which peers only at DE-CIX and your servers are in Amsterdam, or ISP which is choosing AMS and your servers are in Frankfurt. Well, that's life, and not that bad after all.
  • Google doesn't delete Google Tracking cookies on Chrome Browser. Not really surprising at all. Who would expect spying company trying to make spying harder. This is totally expected development. This is also exactly the reason why anyone shouldn't trust "build-in" encryption. Which is enabled, when required, but can be also totally seamlessly disabled whenever it's needed. We're seeing something like this in Australia.
  • Dealt with Python Logger issues, where all of the multiple-processes tried to log-rotate the file at the same time, as well as some of the threads were trying to log-rotate file several times, while being locked and so on. Or causing data loss, because the file is rotated several times, overwriting other files. So classic problem(s), which are caused by not doing the key things correctly. Interestingly the multiprocess logging works beautifully as long as the log rotation isn't triggered.
  • How hard things really are? Seems to be really hard. I just laughed a lot, because company like SOK / S-ryhmä / Prisma / S-Market (the largest retail chain in Finland), can't get even simple things to work correctly. On their receipt, date and decimal numbers use incorrect formats for Finland. Also time is marked against official recommendations. And they mix , and . as decimal separators on the same receipt. It seems that they don't anyone in the organization whom would be capable of handling this ultra complex rocket science thingie. - Yep, no news, most organizations are like that, unfortunately. Correct date format for Finland is DD.MM.YYYY and time format HH.MM (24h) and for decimal numbers of course using a comma instead of a dot. 12,34 not 12.34.
  • While complaining about that, I just noticed that Microsoft Teams uses 12h clock and ignores system settings. Business as usual, let's do something random. Maybe Teams can't handle the situation, that I'm using Finnish locale and English (US) language.
  • Twitter requires me to login to follow public link to public content. That's totally and absolutely annoying. I need to continuously work around crappy services like LinkedIn and Twitter. Post is public, why I would need to provide any credentials to view it? Oh yeah, you want to track and spy on me.
  • Security issues, in one case we've got a team of N persons pre-announced. When we arrived identities were checked for N-1 persons, because one person couldn't make the meeting. Yet, we still got N access passes. That's clear security protocol failure. What's the point of checking identities if they don't care who gets the access passes. Similar failure to the airline ticket / id validation, I did report earlier. They didn't check the identities, so someone else could have been brought in with that access pass.