Jaruzel
The Chorleywood Experiment (2023)
Wikipedia's Terminal Event Management Policy
Sonic hedgehog: restricted expression and limb dysmorphologies
Secret Hand Gestures in Paintings
Switching to Windows Live Writer from Microsoft Word (2024)
You can no longer use Microsoft Word to publish WordPress articles (2024)
2001's Pre- and Post-Premiere Edits
Is Mastodon and the Fediverse good enough yet?
'Raw,' 'Natural' and 'White-Balanced' Views of Martian Terrain
I got as far as manually upscaling the house, and the LCPs:
Hacking Little Computer People on the Commodore Amiga
chrome.exe --app=https://teams.microsoft.com
you can also add these two for an isolated copy of each Teams instance: --profile-directory=
--user-data-dir=At the very least, MS should let us run multiple copies of Teams, one for each tenant. The only way around it right now, is to have the desktop client open and then the web client for a different tenant.
Interchange was a java client, that fundamentally spoke standard IRC to IRC servers, but also used extra external databases to auto-connect users to channels and secure sensitive channels. The client also forced real names (via Active Directory), and was hardcoded to only connect to the UBS IRC servers.
The IRC servers themselves were altered to only allow Interchange clients to connect[1] and to only allow approved bots in channels most of which did full chat logging for compliance purposes.
Interchange was so slow it was nicknamed 'Interchug'.
The IRC server network spanned the UBS WAN network globally, and all staff were encouraged to use it. For the era, no other large banking corporate had anything similar running (officially).
Source: I worked in UBS IT during this period.
---
[1] Although the more enterprising of us just HEX edited mIRC to report the Interchange client name.
The exception for this, is private channels (the ones with little padlocks next to their names). These are created in their own isolated SharePoint site outside of the parent "teams" SharePoint site. It's done this way because the access security around teams/channels is the SharePoint security system. It's a totally nuts way to do it.
Teams is basically built using existing MS technologies in the same way that incorrect LEGO bricks can be forced together if you try hard enough.
I don't think MS have the ability to build an application from ground up anymore.
---
[1] The one upside of this, is that if you only care about the files held in Teams, you can "Sync" the site to your PC, and it appears as a virtual folder in File Explorer.
They are much, much, worse.
By freezing the drive, the metal would shrink just enough to unstick the head. Of course the location where the head crash had happened would be corrupt, but the rest of the data would be fine (mostly).
Online discourse is certainly not safe anymore, so yes we do self censor, and because of that we get out of the habit of expressing raw thought or trying to challenge the status quo for fear of being reported or banned.
It's a real shame. The internet was supposed to be this great opportunity to unify people and help push through a new way of collaboration and debating, yet it's become an albatross around all our necks.
Without healthy debate with controversial or opposing opinions we are never exposed to any viewpoints that differ from our own, so we all just end up swimming in our own echo chamber fishbowls, and the field of intellectual thinking just dies.
I'd like to wax on further about this, but I'm typing (badly) on my phone which is in itself to blame for the brevity of online conversation.