Mixtape

Just to supplement your point with an anecdote: my first "proper" Jellyfin host was a retired Optiplex 3020. I added a 128GB SSD through one of those silly CD drive bay adapters and threw in a Quadro P400 that I bought off of eBay. On top of that, the actual server ran Proxmox with Jellyfin nested in an LXC container. By all accounts, the machine was a janky pile of e-waste given a new, horrible life through sheer stinginess.

There were quirks (mostly self-imposed ones) to getting the whole thing set up, but it ran like a champ for the better part of a year. Hardware transcoding really does make a world of difference, even in the worst of cases.

Their articles seem to load fine in my reader (Fluent) if I fetch them as they're published. Beyond that though, if I try to fetch the full content or open the article in my browser, I hit the paywall. It seems like either their paywall takes a few minutes to apply to their new articles or they deliberately make them accessible to RSS users fee-free.

2019-23.

It's worth noting that GroupMe sticking around was honestly probably a byproduct of my own circles and the specific campus culture to a certain extent.

When I finished my undergrad a few years ago, we were relying heavily on GroupMe chats, with the occasional Slack and one or two LinkedIn groups mixed in. Discord was just starting to exit the gaming sphere and hit the mainstream though. I'm willing to bet it's absolutely dominating the space now.

Wouldn't that imply that >80% of all monitored telnet sessions were exploit attempts for the specific CVE in question? Even with the scale of modern botnets, that seems unrealistic for a single vuln that was undisclosed at the time.

In no particular order: 404 Media, Ars Technica, BleepingComputer, The Register, The Verge, and Tomshardware.

These usually sit in the corner of my screen through the day. Some are better than others for work purposes. The Verge could probably go, and 404 is a bit more socially-focused than the rest. In particular though, having rapid updates from BleepingComputer and El Reg is a great way for me to learn about new vulns, issues that might affect my users, etc.

Seconding this. I have one for my work desk, where (surprisingly enough) it made a lot of sense. The DPI isn't as big of an issue as people make it out to be if your workflow doesn't depend on high density, but the curvature definitely could benefit from being a bit tighter. You need a fairly deep desk or a keyboard tray if you don't want to be turning your head a bunch.

That being said, having this in combination with PowerToys FancyZones has been fantastic. At any given time, I'm usually running 1-4 main working windows plus Signal, Outlook, and an RSS reader. This gives me more than enough real estate to keep them all available at a moment's notice. I have roughly 40% of the screen real estate dedicated to Signal, Outlook, and my RSS client, with the interior 60% being hotkey-mapped to divide in different proportions. Compared to my old setup (one ultrawide plus two verticals) it's been awesome.

Just a nitpick: analog NTSC was roughly 480i at (just under) 30 FPS. The latter is significant, as 3:2 pulldown (as would have been necessary if the station's cameras were scanning at 24 FPS) would have introduced judder and made tracking even harder. To its credit, interlacing also improved motion clarity at the expense of loss of detail, but whether that's a net benefit ultimately amounts to a matter of preference.

Just a guess, but Google Maps has (had?) an integration with Spotify that adds basic playback controls below the map view during navigation. It's meant to keep you from needing to switch apps while driving.

IMO, poor website UX plays a big part in this too. People are far less likely to Google "[city] public works" if "public works" is a top-level menu item on the city website. When you first need to click a hamburger menu, hover over the "departments" entry, select "other departments", and then pick "public works" from the site header though, Joe Public is just going to do a search.

You are correct. This is a consideration at all levels of government currently, with faith in those grants' persistence varying based on an individual recipient's responsibilities.

Absolutely, and that's a risk that we carry, especially in the public sector. That being said though, I don't know if adopting a better-regulated domain is itself enough to alleviate that.

The very unfortunate reality is that many (most?) users evaluate phishing attempts with the null hypothesis that "this is trustworthy". They are looking for evidence that something is wrong and assuming all is well if they don't find it. To that sort of user, the thinking goes something like:

* Some trustworthy sites use .com.

* My municipality is trustworthy.

* My municipality uses .com.

If you draw out the venn diagram, there's a clear gap in that line of thinking. That doesn't matter to someone's Great Aunt Linda though. She just knows that .com is what goes after Amazon and Google, so it must be good.

With that in mind, could using .gov help to protect those folks? To a certain extent. I can see the argument for keeping the more discerning few from getting scammed. For the broader group though, it won't change anything.

Offhand, the alternative solution that I'd offer would be providing clear communication standards to the public. Specifically, defining when, how, and from whom municipal notifications go out. Think of it like the IRS only sending physical letters; archaic as it seems, it makes it pretty obvious that an email "from them" is bogus. The clearer someone's understanding of where to find us is, the more optimistic I am that they'll get where they need to be.

Just my $0.02 as a net/sysadmin for a small municipality in the US:

A big part of why we haven't been able/bothered to migrate to a proper .gov domain boils down to the amount of technical debt we'd need to pay back in the process of doing so. Everything that we do uses our non-.gov domain, namely our Office 365 connectors. On top of that, end users' day-to-day communications with the public make use of the existing domain. Modifying that in any capacity could prove disruptive to ongoing communications and potentially render them liable for dropping the ball somewhere. Not to mention that every single internet account ever created by staff using the current domain would need to be migrated or risk being lost forever.

Additionally, we're a small team. Only myself and one other individual would really have the technical knowledge to migrate our infrastructure. The opportunity cost involved would be massive. There are grants available to help us with this, but obtaining/using those can get complicated at times.

Ultimately, the pros just don't outweigh the cons enough to make a huge difference. From a purely academic angle, should we have a .gov TLD? Absolutely. In practice though, the residents and staff are familiar enough with the current one to render it a non-issue. The average non-technical user doesn't "see" "[municipality].[state].gov". They aren't familiar with the concept of a domain hierarchy at all. They just memorize "[municipality_website]" and move on with their day.