WTF Bites
-
@mott555 I'm calling bad netcode. Me and another player spawned at the start of a match, facing each other, both armed with the starter shotgun. I shot him three times, he shot me once, I died, he lived.
The devs really went and got Bethesda all over quake. Time to hold a funeral feast over one of the greats.
-
Is this bad netcode? I know I'm not the best player, but I used to play a lot of Quake III Arena back in the day.
Q3A hasn't been fucked up yet. Play that.
-
@mott555 I'm calling bad netcode. Me and another player spawned at the start of a match, facing each other, both armed with the starter shotgun. I shot him three times, he shot me once, I died, he lived.
Apparently there's something with the netcode that's tied to your frame rate. Players with 144 Hz monitors have their Internet connections saturated which causes problems, but if they limit their FPS to around 100, it reduces bandwidth usage and the game works great. And I saw someone mention that the game is unplayable if you only have 60 Hz because of this netcode-FPS thing, and you'll end up with a lot of shots that look like hits on your end but misses on the server. I only have 60 Hz monitors...
-
Apparently there's something with the netcode that's tied to your frame rate.
So yes, bad netcode.
-
@mott555 I had full health, full armor, completely overcharged by pickups. Enemy sucks down 5 of my rockets, which counted as hits on my client because I got the "honk" noise, then he cut me down with a 0.3-second burst from the machinegun which is the weakest weapon in the game.
-
@mott555 If I use "practice mode", it puts you against bots. And my weapons actually kill them! I thought they nerfed the railgun, but no, it just doesn't work in online play because
netcode. It works fine otherwise.
-
@levicki said in WTF Bites:
Joking aside I just realized that you cannot write COM out-of-process server in C#. That sucks major Krogan quads.
Literally nothing in those two sentences is correct. You can strip the in-proc server information from your registration and write your own server and drive the moniker/factory system by hand, or you can add one bonus registry entry to your registration and (if the client asks for out-of-proc activation) use the system-provided surrogate server.
And unless you're doing something completely outrageous, why the hell (as a component provider) would you want to run out-of-process? That you can do so sucks major Krogan quads.
-
@levicki said in WTF Bites:
Opening links is NEVER a safe action, sometimes not even with web browsers which use their own malware/badware URL filtering. And they ALL use URL filtering so that is probably a good sign that Zoom should do it as well.
Zoom is just doing the same thing Skype for Business does, and Teams does by default, and Teams sends rich text, so the sender has control over what becomes a link anyway. UNC paths being linkable is a required feature for many users anyway. All similar tools either turn them into links or make them linkable.
@levicki said in WTF Bites:
People to blame if it succeeds are therefore:
1. Microsoft for not disabling NTLMv1 with a big scary warning if the administrator enables it.
2. Microsoft for implementing NTLMv1 in the first place.
3. IT admin not disabling LM and NTLMv1 via GPO.
4. IT manager allowing people to use unmanaged home PCs to connect to work network.
5. Zoom for shitty securityWindows is not even on the list.
Yes, it is. In the first two places.
@levicki said in WTF Bites:
Plenty of serious fuck-ups there indeed. But this is not one of them.
-
@levicki said in WTF Bites:
SMB protocol will attempt to authenticate with remote computer using currently logged-in user's credentials
Why would Windows use the current user's credentials to contact a random site that it's never seen before?
For :histerical:
. The SMB protocol originally used only NetBIOS names, which were local to network segment, and it was a reasonable assumption people will use the same login and password for all computers around the office they had access to even before any centralized account management, and in the early days of that when it was provided by NetWare.Since they implemented Kerberos for central account management, which can do this properly with zero-knowledge, the ancient scheme should have died in a
, except it was kept around for backward compati(de)bility.And somewhere between the SMB protocol started also using DNS names, which is when the (de) part became definitely true.
-
@levicki said in WTF Bites:
Because there is no way to tell the difference between \\files.myworkdomain.adf\share and \\files.blackhats.are.us\share? D'oh!
Well, the feature exists for the cases where there isn't an Active Domain, so there is nothing to dell the difference between (when there is an AD, the authentication is done with Kerberos tickets, which are properly zero-knowledge).
-
So Windows could use some change for better security, but it would likely break even more stuff which now relies on the current user's credentials being tried first.
That's been 20 years ago. There is no excuse for the protocol not to be off by default now, with an option under stern warning that it is insecure and that you should really, really throw the file server that does not support any newer in the trash already if you want to turn it on.
The trying of current user's credentials first is also as likely to break things as make them work. The other customer had a short password change period and 15-minute-lock after I think 3 failed login attempts. Well, if you ever saved your password to their share (we were not in their domain, so Kerberos didn't apply), then after the password change the initial implicit attempts became enough to trigger the lock out and for some reason cleaning the password from the store didn't seem to help; Perhaps without this implicit current user credentials it wouldn't exhaust the try limit.
-
The trying of current user's credentials first is also as likely to break things as make them work.
Oh, it fucking DOES!
And if it succeeds in any capacity even once Windows will forever remember that it did and make it extremely difficult to "log out" or switch credentials without a (unlikely to succeed) set of commandline voodoo.
-
WTF of my day: So, I'm about to hand in another document for an advancement position. For that, Hamburg has created a site where you can search for such positions, bookmark them inside the site. You're then guided through filling out and uploading the various requirements.
Since one of the requirements is writing a concept, I set a browser bookmark to the overview.
When I returned two days later, having written said concept, I first clicked on "Login" and was greeted with a lovely "Site error". But I was logged in! I then simply went back to my bookmark, refreshed (via F5) the site and clicked on the guide.
Site error.
Now, I've had this happen before (last time they migrated the server and somehow overlooked that parts of their site were not working
) and thus wrote them that their site keeled over - again.I received the reply that using bookmarks is a Bad ThingTM and that I should follow the links from the main page (wherein said guide is a bit well hidden, that's why I set the browser bookmark in the first place!)
Seems to me like they somehow broke REST and made a simple GET request non-idempotent. Quality software...
-
Since they implemented Kerberos for central account management, which can do this properly with zero-knowledge, the ancient scheme should have died in a
, except it was kept around for backward compati(de)bility.And somewhere between the SMB protocol started also using DNS names, which is when the (de) part became definitely true.
But… what they should have done is not send credentials to unknown hosts unless they're in a known domain (a check which you can ask the domain server about). Like every other operating system does. Then the user would get a popup saying “I see you haven't logged into this server before; what username and password (or other credential type from this dropdown) do you want to use, and do you want me to remember that for you for the future?” with the default button being Cancel (and OK not being enabled until the credentials are provi ded). That acts as a big old warning against trouble while still allowing legitimate use to get going.
-
Seems to me like they somehow broke REST and made a simple GET request non-idempotent.
Session cookie expired on their end and no fallback.
-
Seems to me like they somehow broke REST and made a simple GET request non-idempotent.
Session cookie expired on their end and no fallback.
Immediately after logging in?
-
Seems to me like they somehow broke REST and made a simple GET request non-idempotent.
Session cookie expired on their end and no fallback.
Immediately after logging in?
I've seen that happen on sites that keep two separate timeout counters, one for backend and one for frontend, and they not being connected so each bit can time out independently at different times. Not saying that is what happened here.
-
Redmond has apparently fallen into the void, if this address is to be believed.
-
@mott555 I'm calling bad netcode. Me and another player spawned at the start of a match, facing each other, both armed with the starter shotgun. I shot him three times, he shot me once, I died, he lived.
Apparently there's something with the netcode that's tied to your frame rate. Players with 144 Hz monitors have their Internet connections saturated which causes problems, but if they limit their FPS to around 100, it reduces bandwidth usage and the game works great. And I saw someone mention that the game is unplayable if you only have 60 Hz because of this netcode-FPS thing, and you'll end up with a lot of shots that look like hits on your end but misses on the server. I only have 60 Hz monitors...
Disable V-sync. Then google for some universal FPS-locking program and lock it to 100.
-
Microsoft for implementing NTLMv1 in the first place.
NTLMv1 was introduced in Windows NT 3.1 all the way back in 1993. It was a different world back then. For example, 56 bits in a hash were more than enough security.
-
Redmond has apparently fallen into the void, if this address is to be believed.
Mount St Helens blew up again?
-
Just realized that Windows Calculator no longer has a data entry window, so you can't paste numbers any more.You can, the box no longer has a visible boundary, so it looked to me like you couldn't.
-
Just realized that Windows Calculator no longer has a data entry window, so you can't paste numbers any more.
Pasting works perfectly fine.
-
@jinpa Discoverable!
-
Just realized that Windows Calculator no longer has a data entry window, so you can't paste numbers any more.You can, the box no longer has a visible boundary, so it looked to me like you couldn't.
Looks like a visible boundary to me! (it even goes away when calc looses focus). The only difference between this and XP's calc (yeah, I turned on my VM to see) is that the mouse only changes to an edit cursor over the numbers now instead of the whole control.
-
Just realized that Windows Calculator no longer has a data entry window, so you can't paste numbers any more.You can, the box no longer has a visible boundary, so it looked to me like you couldn't.
Looks like a visible boundary to me! (it even goes away when calc looses focus). The only difference between this and XP's calc (yeah, I turned on my VM to see) is that the mouse only changes to an edit cursor over the numbers now instead of the whole control.
Mine does not look like that. Not posting this from my Windows (work) computer, so I'll have to post a screen capture later. Maybe it does only appear when it has focus (not sure why you'd call that "even", as if it makes it more obvious somehow).
-
Mine does not look like that
Mine does. But it goes away after clicking any other control, and then there's no way to get it back without restarting the Calculator. It's consistent in inconsistent behavior
-
@Applied-Mediocrity said in WTF Bites:
it goes away after clicking any other control, and then there's no way to get it back without restarting the Calculator.
Redmond has apparently fallen into the void
-
Redmond has apparently fallen into the void, if this address is to be believed.
Mount St Helens blew up again?
Much too far away, almost 200 miles. Redmond is potentially in danger from Mount Rainier or Glacier Peak, but both are far enough away, 60–70 miles, that it would require a really catastrophic eruption to pose any significant danger. Glacier Peak is capable of that kind of explosive eruption, and one several times as large is Mount St. Helens occurred about 13000 years ago, but most of the danger would be to the (relatively) sparsely populated valleys to the west and potentially very heavy ash fall downwind, mostly eastward. (Seattle, Redmond and other major population centers are south.)
-
-
-
@Applied-Mediocrity That's the keyboard focus rectangle. You can -- eventually -- get it to reappear by Tabbing the hell out of it.
-
@TwelveBaud said in WTF Bites:
@Applied-Mediocrity That's the keyboard focus rectangle. You can -- eventually -- get it to reappear by Tabbing the hell out of it.
Or using the hidden registry setting exclusive to readers of HowToGeek
-
@TwelveBaud said in WTF Bites:
Tabbing the hell out of it.
For curiosity I decided to figure out the tab order...
And you were doing SO WELL!!!
Edit: The "Scientific" mode is even worse! And you can't tab to the Function dropdown at all, you just have to know that when you tab to Trigonometry you have to use the arrow keys to get to it!
"Programmer" mode is just as bad...
-
@Tsaukpaetra With the exception of "inverse", all the keyboard shortcuts from previous versions of calculator carry over, so if you have that muscle memory at least that still works.
-
@Applied-Mediocrity said in WTF Bites:
Mine does not look like that
Mine does. But it goes away after clicking any other control, and then there's no way to get it back without restarting the Calculator.
Like so much of Win10, the calculator looks like crap. Some time ago I discovered there was a better version in Windows 10 Enterprise 2016 LTSB, and you can download it here
-
-
This post is deleted!
-
-
-
Today I had to make an app that I made for my employer's largest customer work on Windows XP. Fortunately it was easy, most of the libraries either worked right out of the bat or could be downgraded and AsyncBridge took care of all the async stuff.
-
@magnusmaster said in WTF Bites:
Fortunately it was easy, most of the libraries either worked right out of the bat or could be downgraded and AsyncBridge took care of all the async stuff.
E_MISSING_WTF
-
@Zerosquare said in WTF Bites:
@magnusmaster said in WTF Bites:
Fortunately it was easy, most of the libraries either worked right out of the bat or could be downgraded and AsyncBridge took care of all the async stuff.
E_MISSING_WTFYeah, that looks like either a Status post
, or a Cool Stuff post!edit: Updated because of XP...
-
-
Yeah, but it's a pretty weak one.
-
Ran out of space on my C: drive today.
That's not the WTF, though.
Naturally, I ran the built-in-to-Windows disk cleanup utility. Told it to clean up system files. It said that something like 34 GB could be freed (~29% of the total space). Sounds good. Ok.
It only freed ~5 GB.
Disbelieving, I ran it again. Now it said that ~29 GB could be freed.
Ok...
It freed ~4 GB.
Ran it fucking again. You're starting to see the WTF now, aren't you?
In the end, it ended up freeing about as much space as it initially told me that it could free... but it took running it something like 10 times!!
In hindsight, that's why I ran out of space. In the past, I've ran the disk cleanup utility when it complained about low free space, but it never fucking occurred to me that running disk cleanup multiple times could possibly be more effective than just running it once and calling it good.
-
It said that something like 34 GB could be freed (~29% of the total space).
There's the
! A 120G drive. (my C: is currently using 163G)
-
It said that something like 34 GB could be freed (~29% of the total space). Sounds good. Ok.
"
Oh, you wanted those 34 GB to be cleaned up right now? "
-
Ran out of space on my C: drive today.
That's not the WTF, though.
Naturally, I ran the built-in-to-Windows disk cleanup utility. Told it to clean up system files. It said that something like 34 GB could be freed (~29% of the total space). Sounds good. Ok.
The few times I've used it, I've never had that problem. The bigger problem in my experience is the absurdly long time it takes to do the job.
Deleting a few gigabytes of files, from an SSD, should take a few seconds at most, not 30+ minutes.
WTF is it doing that takes so long?
-
@mott555 Bethesda made a WTF in my favor. After looking through the vanity shop and seeing the unlockable old-school Doom skins for the weapons, I now have them in-game even though I never actually paid/unlocked them...
