mrbn

Sounds like they need a camera to watch the camera so they can catch the guy.

"gonna paint our wagon, gonna paint it red!" I sing this part to myself frequently.

If you are looking to do something like Github's Personal Access Tokens (PAT) then it is easiest to just think about it like a password:

• Create a high entropy (secure) string
• Store the hash of the string in a database table
• Store the permissions and other metadata with the PAT's hash
• Validate the PAT (permissions, revoke status, etc) on each request to the server

Storing the hash of the token, like you do with passwords, is a good practice in case your db is ever compromised as it wont leave the tokens accessible and reusable without a lot of effort.

Yeah, unfortunately that stuff is almost impossible to estimate. Inform your client that fixing the build will be a game of whack-a-mole where you'll fix one thing and 5 new errors will show up. I would give yourself lots of time since you've never worked on Maui (? You didn't say that in your post but if you've never heard of xamarin, i'll assume maui is new).

I would break your work down into two milestones: a) compile and run, b) fix all the busted views. It should come to no surprise that a) will be hard to estimate so give yourself lots of time, and b) will be easier to estimate because you'll be able to review each View and determine what kind of fixes you need to make.

Good luck

Yes. The transition from Xamarin to Maui has been similar to transition from .net framework to .net core.

A few things you will run into:

• namespaces have changed
• certain things will be deprecated but still currently work (ie FillAndExpand)
• platform specific setup has changed (you'll need to convert to the new way, but code will likely remain the same)
• upgrade your nuget packages to the Maui equivalents (the ones we used had Maui versions so we didn't have to change any of them)
• certain ways of doing things have change slightly, like how to run things on the main UI thread (you'll see warnings)
• your xaml code will remain mostly unchanged but your layout may need to be fixed (especially if your dependencies changed their interfaces)

That's all I can think of right now. There's no easy way to do it and it's going to suck. Focus on getting it to build with all your dependencies upgraded and then go from there.

Election day is Monday, April 28, 2025

https://www.elections.ca/home.aspx

You will speak the version that you learned. You will mostly notice regional differences in the idioms and synonyms of the words you know might be used more commonly in one region vs the other.

For example, in London you might hear people use boot instead of trunk.

But the majority of the words will be the same regardless of region.

That means one of the options could be Trump's resignation. Right? Right?

"Copilot I'm losing this match, aim for me"

Kind of a nothing burger.

These repositories, belonging to more than 16,000 organizations, were originally posted to GitHub as public, but were later set to private, often after the developers responsible realized they contained authentication credentials allowing unauthorized access or other types of confidential data. Even months later, however, the private pages remain available in their entirety through Copilot.

The repo was listed as public and archived. It's not clear from the article but I suspect that the "private" information is just a copy of what was made public and not the information added after it was made private.

I thought of Crysis also when I read the title. But first, I'm down for Quake and more specifically QuakeTF (team fortress). I spent way too much of my youth playing quake and qtf (honorable mention to UTF).

I read and upvoted this meme for the glory of the empire!