"If one root server directs traffic lookups to one intermediate server and another root server sends lookups to a different intermediate server, important parts of the Internet as we know it could collapse"

this doesn't pass the sniff test. Records sometimes being out of date for some users is par for the course for DNS. Domain owners already need to account for that. Also, the "intermediate server"s in question would be things like the .com and .org operators' servers. I would hope the likes of Verisign and the Public Interest Registry can handle a delay in sunsetting a DNS server to accommodate something like this.

What is the job?

Is this a continuation of Lemmur? The Lemmur logo appears when the app loads, but the project is not marked as a fork of Lemmur and the readme makes no mention of Lemmur

It's a "z", not an "e"

https://x.com/AnonymousArtz3

first: C++ most: Rust

I wasn't aware that there were any games that could make meaningful use of 16 cores, let alone games that might want more. Was there a major advancement in game programming when I wasn't looking? Or is the headline as far off base as I think?

I don't think in-game skill is a fair way to judge that. You can absolutely have a capable developer who is passionate about the game, but who isn't very skilled at the game itself. And unless the game has an extremely technical target audience, I can expect that most of the players who brought the challenge-winning skills to the table are not also coincidentally people who would be developing or otherwise technically supporting a continuation.

Also, if they release the source and it doesn't get traction, no-one is harmed. Any procedural and legal clearances should've been done before announcing the challenge. To me, open sourcing an EOL game or other product is about giving an opportunity for others to continue or learn. It might be sad if no-one bothers, but it's still the right thing to do regardless of when or whether someone takes on the challenge.

That is indeed a Nintendo RF converter in the background, but I don't believe we ever owned a Sega console. Granted, I didn't know we had a SNES until it was found a few years ago in a shed that was being torn down

You can get a cheap phone holder of some kind and use the timer option of your camera app. A 10 second timer is usually enough to put the last paw on and pose

The remark about style warnings is really alien to me. Style warnings are something I'm accustomed to when programming in nearly any language. I can't remember the last time I used a language where whatever IDE I happened to be using didn't have style warnings. And I've never had trouble adapting. "Oh right, C# convention is PascalCase methods. Oh, Java is camelCase". In fact I've been jumping between a C# project and a Java project recently, and I haven't been finding it difficult. Rustc having some linter-type warnings built in is a bit novel I guess, but really not a fundamentally different experience. It's really not any more difficult to disable those warnings for a Rust project than for a C# project. I don't think I can understand calling that "not okay".

It took me an entire year to realize your reply was also a link to an argument. I thought you were just stating your conclusion without bothering to explain, and was more than a little irritated. Sorry.

The main thesis of the linked article is that a VPN is a glorified proxy, but that's what I've always viewed commercial VPNs as -- proxy-as-a-service. The word "proxy" hadn't been at the forefront of my mind but it was the same mental model. And that's the only reason I've used (and still use) them. And that is consistent with the statements in my original reply. I can look at companies that advertise themselves as proxy services to see if I can get a better deal, but my current VPN plan comes with my current cloud storage plan, so unless I change that (which I am considering), it doesn't save me any money to switch.

I had the issue reoccur, and I can confirm that the jwt token was missing from the request to /, but present for other resources such as the css stylesheet

I waited for the issue to reoccur so I could test that out. The jwt cookie is missing from the request to / but is present in several of the other resources used for the page. That's consistent with Crashdoom's comment. Sometimes, the issue would only occur in a specific tab (refreshing the tab did nothing, but opening a new tab would have me logged in), which is roughly the opposite of what that user reported, but this time, it was a problem in any tab

Testing with the multimeter, the outer pins of the 7-pin connector are 1-to-1 with the pins in the same places of the 4-pin connector. I read the wikipedia article on mini din connectors more carefully, and there is an indication that this scheme was sometimes used to have a socket which could accept either an S-video cable or the proprietary one. However, the keys don't look compatible. The key on the 7-pin is both wider and thinner than on the 4-pin.

the center pin of the row of 3 connects to the pin of the rca connector, and the ring of all 3 connectors are connected together. The center two pins of the row of 4 are not connected.

Likely Solved

Of the options people have presented, a video card is by far the most likely for us to have owned at the era those options are from. The two-way arrow symbol on the connectors does give a little bit of doubt, but it seems pretty clear at this point that if I still owned the matching product, I wouldn't use it, and that's enough info for my needs

You can disable specific warnings as a project setting, not just with rustc/cargo but with every build toolchain I've used in the last ~10 years. It's very common for me to find a project with at least one specific warning disabled. That really isn't a "trust me bro" -- people can look at the project, see which warnings are disabled, and decide for themselves if that is reasonable.

I don't believe we ever owned a capture card, but it's at least plausible to me that an old video card may have used it.

Both din connectors have a two-way symbol

Any system where the most severe outcome is "A moderator will look at it" is an easy sell for me, so I wouldn't have any problem with 1 or 2. And an opt-in system of nearly any kind is going to be okay by me so long as it doesn't stand to harm anyone who hasn't given informed consent, so 3 also sounds fine.

With 4, I'd definitely want more details on what is considered "a significant risk or pattern of spammy behavior" and on why the temporary suppression "may break existing conversations or prevent new ones" before being comfortable with such a system.

It is definitely 7 pins, not 9. The pin layout matches this image on the wikipedia page for mini din: https://commons.wikimedia.org/...

I tested the pin connections and it does match the "compatible with an S-video... plug" in the image's caption, but I don't know if the keying allows for that. The key on the 7-pin is both wider and thinner than on the 4-pin.

The fact that this is a long cable instead of a short adapter does give me the impression that both the 4-pin mini din and the rca connector are supposed to be used simultaneously.