We hand count in Canada and don't have a notable accuracy problem, and ballot security is a rare concern. We manage that by having simple ballots which make voter intent clear while having the count being run by an independent, non-partisan national organization _and_ each table where tabulating is occurring can be watched over by representatives of the parties running.

_And_ we have mail-in ballots.

When issues do arise it tends to occur when a ballot box needs to be transported between locations; when this occurs it is taken quite seriously by Elections Canada.

It works great. Perhaps the USA should contact Elections Canada and learn a thing or two.

The last decade has seen an increase push in what Google started calling "Zero Trust"[0] and dropping VPNs entirely. The issue being that once someone got into a VPN it was much, much harder to prevent them from accessing important data.

So everything "internal" is now also external and required to have its own layer of permissions and the like, making it much harder for, e.g. the article, to use one exploit to access another service.

[0] https://cloud.google.com/learn/what-is-zero-trust

I've been trying to use HTML's native popover and dialog recently. The promise of not having to write/import focus traps, better integration with standard platform "cancel" UX, the top layer concept, etc made them sound great, but in reality it's been kind of painful.

Stacking order when you have multiple modal dialogs and popovers in the top layer is based on most recently revealed element, so that toast that just opened is now hidden under a dialog. Anchoring is currently only supported in Chrome, so popover tooltips show up in the corner. Firefox supports transition animations when opening a dialog but not closing it. The web platform feature needed to tie the mobile back button to closing a dialog isn't actually implemented yet. Frameworks that patch the DOM might clobber modal dialog state because it's a function of both the "open" attribute and the result of showModal().

Some of these will improve but I think the display order problem is here for the long haul.

I'm with the other commenters who agree in spirit, but would hate the details in the post. Assigned channels where you are expected to post your random thoughts feels utterly dystopian to me.

In my experience, "rambling" channels build up organically... as you have a thought, you share it with someone relevant, not just drop it into a channel and see who reads it. Over time, small group chats evolve naturally, and assuming everyone has communications skills, topics that become relevant to the whole team are then shared with the whole team.

I agree that such discussions are healthy, maybe even required, for a functional remote team. But let people organize themselves - don't prescribe specific methods that teams must follow. The last thing we need is a formal framework of how to have organic discussions.