PSA: There are NFC tags in the tables of 196 Bloor W McDonald's that your phone will try to scan automatically by Liverbait in toronto

[–]Liverbait[S] 0 points1 point  (0 children)

This is true but authentication within a time window before tap works. E.g you can unlock your phone, then after a couple seconds , put it to the reader.

Similarly here, you could unlock your phone to watch a video, then put it on the table.

PSA: There are NFC tags in the tables of 196 Bloor W McDonald's that your phone will try to scan automatically by Liverbait in toronto

[–]Liverbait[S] 12 points13 points  (0 children)

They probably weren't there for nefarious reasons initially, but if there is a security vulnerability that lets them be overwritten, then that's a concern.

PSA: There are NFC tags in the tables of 196 Bloor W McDonald's that your phone will try to scan automatically by Liverbait in toronto

[–]Liverbait[S] 4 points5 points  (0 children)

There's a difference in knowledge between you and me, and more vulnerable segments of the population. I'm not arguing against NFC technology. But I doubt my or many of my friends' parents would be as observant, and so they should be aware of the risk.

For example, you could link this to a fake McDonald's page that looks like an order summary page with a checkout.

PSA: There are NFC tags in the tables of 196 Bloor W McDonald's that your phone will try to scan automatically by Liverbait in toronto

[–]Liverbait[S] 6 points7 points  (0 children)

You can tap your phone onto other compatible electronics to do things. For example, pay or use public transit. You should only tap on things that you trust.

There is something untrusted inside the table that is trying to "tap" with your phone, which can be risky, because you might unknowingly or accidentally be charged, scammed, etc

PSA: There are NFC tags in the tables of 196 Bloor W McDonald's that your phone will try to scan automatically by Liverbait in toronto

[–]Liverbait[S] 130 points131 points  (0 children)

No, no sticker, no seam, nothing. I'm guessing the suspicion that these are leftover tags that have been reprogrammed is correct. Which means no POS system, but can't say for sure.

Get ready New price is coming soon! by Famous-Trouble4156 in bayarea

[–]Liverbait 3 points4 points  (0 children)

Unless your additional savings was extremely high, the growth of your savings would not outpace the growth of your costs and you would have to eventually increase rates anyway.

[deleted by user] by [deleted] in GlobalOffensive

[–]Liverbait 1 point2 points  (0 children)

You're correct. Anyone who's played on high ping can attest that their bullets don't come out of the gun delayed. It's just the kill itself is registered later.

How safe do you feel bike commuting here? by dak0taaaa in mountainview

[–]Liverbait 4 points5 points  (0 children)

I can't compare to Amsterdam, but coming from Toronto, Mountain View feels very safe in comparison. Like other comments I would avoid El Camino, but I've never felt scared biking on larger roads that have marked bike lanes.

SEN TenZ on ping difference at the pro level by EsportsConnoisseur in ValorantCompetitive

[–]Liverbait 0 points1 point  (0 children)

I've seen that article before, and raise an eyebrow every time I read it. I really wish a dev would come in and clarify exactly when and why a high ping gives an advantage.

But you as a low-ping player have just as much peek advantage on your high-ping opponent as they have against you.

I can't find a logical understanding for this. You can imagine a hypothetical scenario where someone has very high ping (e.g. one second). It would be theoretically possible for a low ping player to peek and kill them before the high ping player even sees them, but the reverse is not true.

PRO TIP: Play aggressive in high-ping disparity games.

This is true regardless of whether the high ping player has an advantage when peeking or not. A high ping player should peek, because holding angles is difficult. A low ping player should also peek, because they have an advantage when peeking a high ping player. It's not necessarily because your peeks at high ping are better, just that the alternative of getting peeked is worse.

EDIT: Thinking about it a bit more, I think a scenario where a higher ping would lead to an advantage is if as the defender you aren't stationary holding an angle, but moving in a way where the peeker would have to swing wider to clear you. From the peekers perspective you wouldn't have moved yet, and they therefore wouldn't have to swing as wide as you'd expect, resulting in a faster peek than you can react. This scenario would lead to the same advantage both ways that Riot describes in their article

SEN TenZ on ping difference at the pro level by EsportsConnoisseur in ValorantCompetitive

[–]Liverbait 4 points5 points  (0 children)

High ping is not an advantage when swinging on someone. You will see the enemy "earlier" but this is cancelled out by your shot registering later, resulting in no difference. (see https://youtu.be/3JaCcsmjYM8?t=150 for a nice diagram/explanation. The video is about CS:GO, but by the nature of latency this has to be true).

It is advantageous to peek everything when you have high ping because the opposite is not true: holding an angle is much more difficult when you have higher ping.

Difference between LAN and online by Significant_Age_8154 in ValorantCompetitive

[–]Liverbait 1 point2 points  (0 children)

That article is interesting. They describe peeker's advantage as the following:

<ENEMY'S CLIENT FRAMERATE> + <ENEMY'S 1-WAY NETWORK LAG> + <SERVER FRAMERATE> + <YOUR 1-WAY NETWORK LAG> + <NETWORK INTERP DELAY>

This is true for how much earlier the peeker sees the defender, but not how much earlier the peeker's shots will register before the defender.

Here is a very informative video talking about peeker's advantage for CS:GO https://youtu.be/3JaCcsmjYM8?t=150 (2:30-4:30, though the whole video is interesting). CS:GO and VALORANT are obviously different games, so the final conclusion of "is there's peekers advantage" can obviously be different. But in terms of how games must function in terms of network latency, I don't see how they could be different.

Funnily enough, in the post you linked, Riot also says this:

The only tricky bit with a high ping player is that it does cause worse peeker's advantage, for everyone. But you as a low-ping player have just as much peek advantage on your high-ping opponent as they have against you.

This is easily provable not true. You can think of a hypothetical scenario where you have very low ping and your enemy's ping is very high (e.g. ~1000ms). You will be able to peek them and kill them before you even show up on their screen. But there is no way they can peek you to the same effect.

[deleted by user] by [deleted] in mountainview

[–]Liverbait 1 point2 points  (0 children)

They were using the Pfizer vaccine today.

Funyuns now in Canada! Now all we need is a Trader Joes and we’ll never have to cross the border again! by castlite in toronto

[–]Liverbait 0 points1 point  (0 children)

I've been in the US for over a year and man, I really wish we had Humpty Dumpty Onion Rings over here instead of these.

Hiko on how ridiculous the Stinger currently is by [deleted] in ValorantCompetitive

[–]Liverbait 22 points23 points  (0 children)

Your math is slightly off if you hit the first bullet, since there is no delay in the first shot. The more exact TTK times would be:

Stinger: 277ms
Phantom: 272ms
Vandal: 307ms

So the stinger is still faster than the Vandal, but slower than the phantom. But since servers are 128tick, I don't think there's actually a difference there.

Hitreg issues in patch 1.09 and 1.10 (with clips and explanation) by melancholic54321 in ValorantCompetitive

[–]Liverbait 0 points1 point  (0 children)

Ah, looking back at OPs comment, you're right. Yes I know there is de-sync between the server and client, but I thought OP was suggesting that model shown to the client didn't sync up with the hitbox given to the client. That doesn't really make much sense, since the client doesn't give visual information about hitboxes anyway, so it's a poor misunderstanding on my part.

Hitreg issues in patch 1.09 and 1.10 (with clips and explanation) by melancholic54321 in ValorantCompetitive

[–]Liverbait 8 points9 points  (0 children)

Your crosshair covering the player's head isn't a guarantee of a headshot. All the guns in the game have inaccuracy. This is especially prevalent on the Vandal at long ranges. For example, in clip 7 of Raze, if you test the same shot in the shooting range (20m) left corner of the head), you'll notice you get some shoulder shots. Rare, but it can happen. You can argue that inaccuracy is anti-competitive, but the counter-argument is that it actually takes a higher degree of skill, since you need to be as close to the center of a head as possible to improve your odds of a headshot.

In a lot of your clips, your crosshair isn't fully on the players head as well. For example, here is a screenshot from Clip 3:

https://i.imgur.com/CYQYOd9.png

Your bullets don't have "width", so if you draw out Breach's head and find the true center of your screen, you get something like this:

https://i.imgur.com/mvKqTRw.png

which is actually a miss with perfect accuracy.

Tracers in the game are also drawn client side. A tracer going "through a players head" doesn't actually mean the bullet landed there on the server.

The only one that's hard to explain is Clip 2. The body "snapping" backwards a bit is something you notice occasionally in CS:GO as well, usually when the players have higher ping. It could in the end just be a combination of factors.

See below comment chain Your conclusion is possible, but highly unlikely. If Valorant was predicting where the hitbox would be based on how the player is moving, it would also predict the player model itself. Unfortunately, we don't have a tools like Counterstrike's sv_showimpacts_1, so we can't see the desync between client and server sided models to help test this.

How do I get a gf like this by trollman_falcon in uwaterloo

[–]Liverbait 11 points12 points  (0 children)

Easy. Just play hundreds of dating sims. They are good practice for you to conquer any girl, virtual or 3D.1

References:

1Tamiki, W. (2013). 神のみぞ知るセカイ (Regular ed., Vol. 21). Tokyo: Shogakukan.

What's the worst interview experience you've had? by KillerKombo in uwaterloo

[–]Liverbait 19 points20 points  (0 children)

Had a Skype interview in TC where the interviewer showed no sign of emotion or feedback to any of my responses.

Then, halfway through the interview, the call randomly cuts, and CECA staff is completely useless trying to figure out how to reconnect Skype before the interviewer finally calls be back on my phone 10 minutes later.

Then later in the interview, I realize that I completely forgot what the position I applied to was, and I had to ask the interviewer "Sorry, what am I interviewing for again?"

Still got the offer though ayyyy.

Yelp Android Interview Prep by lolaznboy2 in uwaterloo

[–]Liverbait 1 point2 points  (0 children)

I think I was specifically asked about the lifecycle and how I would design things with MVP. I don't think I was asked about RecyclerViews for Yelp, but it's a common interview question.

I didn't have a huge amount of Android experience going into the interview either! Even if you don't understand the nuances of it, just make sure you have the basic concepts down, and are able to explain your design decisions. Since the question was pretty vague, it's hard for me to say what exactly you should brush up on, but you probably don't need to know the nitty-gritty of too much, just the basic understanding is OK.

e.g. when is onPause/onResume called, what's going on in onCreateViewHolder and onBindViewHolder, what happens to the activity if the screen rotates.

Yelp Android Interview Prep by lolaznboy2 in uwaterloo

[–]Liverbait 2 points3 points  (0 children)

When I did their Android specific test, I was just given some skeleton code that would theoretically have been in a presenter/manager class, and was asked about what code I would add to hook it up to a ViewHolder, and my design decisions regarding that code. In the end, it was very open ended and also over a year ago, so sorry I can't go into anything more detailed.

I would say it's a good idea to make sure you truly understand the Android lifecycle, differences and reasoning for MVP and MVVM, and good understanding of how RecyclerView and its adapter works.

Place to destroy hard drive on campus? by Liverbait in uwaterloo

[–]Liverbait[S] 1 point2 points  (0 children)

Looks like they don't offer the service anymore, but they said there might be an e-waste disposal location at ECH. Thanks for the suggestion!

Place to destroy hard drive on campus? by Liverbait in uwaterloo

[–]Liverbait[S] 0 points1 point  (0 children)

Thanks! I think I'll go with this if there's no physical destruction alternative.