“Ever since I learned about confirmation bias I’ve been seeing it everywhere!”
The raging, “I don’t like this, so it must have been written by an LLM!” comments on HN have gotten so tiresome that I find when I see them I just down-vote them and move to the next thread. (Most of the time. You’re witches comment captured my attention and prompted a response. Well done — the comment must have been written by a human.)
— No tokens were harmed in the production of this comment. —
I don’t like humans throwing accusations that something was written by an LLM if they don’t like it. The constant insinuations that us machines are the ones with poor taste is fookin’ tiresome.
If the provider is worth its salt¹ it will prefix the stored password with the hash that was used. That way it can update the hash when the user next logs in if it is out of date.
I see what you did there, but I assume you mean "prefix the stored hash with the algorithm that was used", right?
I still don't know how this would help with a migration, though. They would still need to run both auth systems in parallel until every single user has logged in again - or force everyone to create a new password. Right?
Assuming you get get access to the hashed passwords the other party used as part of the migration data, and you know what hash was used for them, then there's nothing to stop you using them yourself.
But in reality, I doubt they would release either of those things.
I'm still using Mercurial whenever I can (including work!). The Tortoisehg GUI is good for doing reviews, and the command line is comfortable.
I grew up on CVS and then Subversion. Played with Bazaar a little, mainly because it could use an SFTP location as the back-end.
And I still avoid Git if I can help it. I would/do figure it out when I have to, but it never feels comfortable. Such is my avoidance that I'm dabbling with Jujutsu although I'll still need to really sit down and read through it some more to grok the way it works.
When I tried Fossil it had things weirdly separated.
I was expecting when I make a commit, I would have the facility to specify what issues it addressed and it would close them for me automatically. It seemed there is so much opportunity there to "close the loop" when the issue tracker, etc and integrated in your VCS, but it wasn't taken.
This is a current architectural limitation, manifests (defining check-ins) and tickets are different types of artifacts and you cannot combine the card types into the same artifact. Changing this would likely break backwards compatibility with previous Fossil versions and I'd expect resistance. It may still be worth bringing up on the Fossil forum if you desire the feature.
Personally speaking though, I don't want things automagically closed GitHub-style based on parsing a check-in comment. An issue ought to be closed with intention.
> I don't want things automagically closed GitHub-style based on parsing a check-in comment.
Sure, I get that. I was just disappointed that none of the project management stuff seemed terribly integrated in any way from my brief review. It seemed like opportunities there that were not taken.
I wanted to host our company wiki in Fossil, but there is no way to import it because Fossil completely separates versioned project docs and the built-in Wiki function. Our git-based wiki could be imported into Fossil as "docs" but would not receive the nice formatting, GUI editor or dedicated page that the Wiki function does. There is also no benefit to manually converting it all to Fossil Wiki as some of our wiki editors work on raw markdown.md files and commit changes by git which is not possible with the Fossil Wiki; everyone would be forced to use the online editor only, whereas currently we have a choice of markdown or Gitea's editor.
My mum's dementia has recently worsened to the point that she cannot figure out how to use the phone to ring people. She just finds it confusing and has caused her a great deal of distress.
I ended up installing Big Launcher[1] as an alternative android launcher and configured it so it has buttons to ring three people. That's it. Even then, then confirmation yes/no dialogue when she presses "End Call" gave her a lot of anxiety initially.
I recently had to setup access to a local streaming service on my step-dad's TV recently. The amount of hoops necessary, including installing their stupid app on a phone, and entering passwords for several different accounts, several times, was absolutely ridiculous. Being technologically adept I found it an absolute PITA. It was a complete non-starter for him.
My point is that your, "If he can afford a season pass, he can afford a smartphone," comment comes across almost as callow as the attitude of the Dodger Stadium management towards the very real issues of getting old in a world that is moving faster and faster technologically.
reply