fedorareis

While I get what you are saying, it seems weird from the standpoint of the other player since they have been out of the engagement area for 1+ seconds. It still seems to me that you would want some sort of cap on the rollback period.

> I use the reliable mode for sending client inputs to the server: the server needs to be able to recalculate the state of the game reliably, and it's not acceptable for some client inputs to get “lost”. This may cause a bit of latency, and a bit more work for the server, which will have to “rewind” the game a bit further if an input arrives very late, but that's the price to pay for a stable game.

Maybe I’m missing something, but wouldn’t you either want the input to drop or the rewind to not happen at some point? If my network is extremely laggy when I’m playing a multiplayer game I would expect that my attempt to hit an opponent wouldn’t still succeed 1+ seconds later when they have already moved and are no longer in a position to be hit.

But if they are doing accessibility they have to create alt text for the icons anyway and that needs to be translated. So the only i18n complexity left would the ltr vs rtl languages and depending on how you place the text they wouldn’t need to really change the layout to accommodate both.

Why does the folder color matter? Is it just because that is what you are used to from a specific OS?

Color helps for some people but when making an accessible design you have to account for color blindness and other vision issues. Which means the icon needs enough contrast and can’t rely on just color to convey meaning, unless the icon is paired with a text label that also conveys the meaning the color was trying to convey.

So while I agree that color iconography can be extremely helpful for the average user, unless it is supplemented by other techniques it can make a product completely unusable for a subset of users

I don’t agree that it is obvious that it is more interesting or deep. I have played a lot of hours of Threes and it is mildly more complex because the tiles only move 1 square at a time, but in my opinion that doesn’t actually make it more interesting or deep.

My understanding is that you are correct. If the repo and all of its forks stay private then the only people that would be able to view them are people who have permissions to access those repos.

A red reset button appears in the top right of the cards after you slide the slider.

One of the best ways to affect this is to make complaints to the CFPB. They are the regulatory body that is responsible for making sure the credit bureaus aren’t harming consumers

Those types of suits generally hinge on proving malicious intent

I had a similar issue with people ignoring my availability at my previous company. I just started declining meetings. It forced people to either decide they didn’t need me in the meeting or they would reschedule it

Bing didn’t even release it in the main flow. It is a separate tab within bing like images or maps. So Google could have done a similar thing

While yes a lot of music is based on prior art there are levels of that and there is a lot of case law on what doesn’t break copyright. There is a lot of music that steals from classical but that is public domain. There are rules about how much of a riff from a copyrighted song you can borrow before it becomes copyright infringement and you owe the original writer royalties. Music also has a lot of standard conventions that lead to similar conclusions at least if you are using western music theory since that is based on western classical music.

So an amount of this deals with scale and the copyright status of the prior art.

A lot of the APIs that allow for things like starring projects have been around for a long time. Before GitHub introduced an official mobile app there were a number of unofficial mobile apps that used those types of APIs to give users a “fully functional” GitHub app.

I would say though that if GitHub is allowing requests like that through the API then they should be banning the API token and the account it was issued to if it uses the API maliciously

I hear what you are saying, but I think this comment in conjunction with the parent comment speak to the bigger issue which is how do you make something easy for both IT and the end user? Yes, a solution like this may make it easier for IT to set things up and support their users but I have had the same experience as OP with similar products at companies I’ve worked at. Logging into a system now means I have to find my phone, unlock it, open the app, scan the code, and provide a biometric (or passcode) again. That’s if everything goes smoothly I might be prompted to change my phone’s password if I’m using a company phone with a password change policy, something might happen with a redirect or the app. Now I’m completely out of the zone of what I was working on.

Or I can have SSO or a password manager and be logged-in in less time then it takes me to grab my phone. As an end user I would much prefer the latter.