Yeah the main product I'm working on (Moxie Docs) has AI generation of mermaid diagrams, I find that it works __well enough__ but I needed some strong guardrails, quality checks, and templating to make sure it doesn't generate broken diagrams (or useless ones). First few iterations it would create a diagram for everything and it was a bit zealous on when it decided diagrams would be useful.
Would you consider introducing any tooling around that? I've been building an automation setup for keeping dev docs up to date (and eventually user-facing knowledgebase docs) but would love to chat with other developers to make sure I'm doing the right thing or meeting the right needs. For me the focus was introducing easily readable / digestible docs, including mermaid diagrams where they are useful, linking to other parts of the code / docs, etc. and then a layer on top is a basic "Q&A" feature (you could do the same in any AI tool realistically) but something that surfaces docs or generates them on demand based on where the knowledge gaps are.
Have you tried any AI review tools? I've been using / trialing a few and find they do an OK job but still seem hell bent on __finding__ and issue no matter what
Built this because I'm sick of keeping documentation up to date when everyone's using AI tools now.
It will not only generate missing docs / update / remove docs as they need alignment, but you can hook up the MCP to whatever agent is being used these days and it'll inform it of codebase conventions & relevant documentation, telling it to update docs as it find them or as it makes changes (in the same PR as related work), and reduces spend on tokens by getting things right the first time without having to grep the whole codebase for context or go through 5 rounds of "follow our conventions"
It's shared standard in the sense that all implementations will be the same, AFAIK passkeys you generate on iOS systems aren't easily used on windows ones, etc. Or they'd require scanning a QR code from a phone which IMO sucks when a password manager has it in the browser already.
Also what security issues with password managers? There's some potential concerns with extension-based over OS based systems, but if your device is compromised where someone can actually access memory then they'd both be equally void to some extent, AFAIK there's nothing seriously concerning security wise on a password manager vs keychain, etc.
They're essentially certificates, so most implementations will only store them on-device, and most implementations I've seen seem to favor the phone as the device you use.
It really depends on the platform - but in short you'll either need a phone, or be locked into an ecosystem (browser, OS, etc) making using them on multiple devices & browsers difficult or impossible. A password manager supporting passkeys makes this easy as you can 1-click generate a passkey, and 1-click sign-in to services from any device or browser.
These probably won't replace password managers, just result in passkey managers... Dashlane already supports passkeys & 1password just announced intent to support soon.
I think this gives people a false sense of security, yes zero knowledge is extremely useful + cool, and certainly reduces the risk in event of a breach, but all it really means is that _all_ of your passwords are behind some encrypted blob in the open, that would be extremely difficult to decrypt. Not impossible. Certainly any average or even very high-end machine today would have a pretty much 0 percent chance at decrypting the data, it's still out there in the open forever. Imagine in 10 years we have some leaps in quantum computing or discover a flaw in the algorithms use, all a hacker would need to do is go back & decrypt the data to try some credential stuffing attack, etc.
TL;DR is short-term I wouldn't be freaking out of my password manager was hacked, but I would still definitely update all credentials at some point & treat it as an actual breach, and not an "oh no we were hacked but it's okay because zero-knowledge!".
Also how many times have they been hacked now? Who's still using last pass?
Adding to this - ISPs likely would never try any of the above, simply because it would hurt their public perception, isn't worth the time, and is potentially illegal depending on the area.
ISP's could easily stop Bitcoin, I don't really think anyone claims they can't? Bitcoin isn't mean to be an impossible to kill hydra of economic power, but a decentralized, peer-to-peer, trustworthy ledger of transactions.
ISP's could block the common ports Bitcoin uses (but that would likely break a lot of other applications), they could potentially blacklist certain IP's, but because of the decentralized nature of Bitcoin this would likely only affect discovery in a minimal manner. ISP's could also inspect packets to determine if the traffic is Bitcoin related, but potentially something like TOR could prevent that inspection, if enough ISP's inspect & block Bitcoin TOR would likely not be of help (as it simply protects the transit of data, not the entry/exit).
Definitely a lot of ways BTC could be affected. Governments could also outright ban it and that would destroy the network as it would lose a huge amount of value as a serious asset.
I've used some easter eggs to enable developer features. Like the konami code would prevent session timeouts so we could test things over a longer period, etc. Haven't introduced any fun ones yet though (may do so now!)
To be fair the claim for the money was stipulated that you must have credit monitoring already in place. The point of the cash settlement was to offset the cost of whatever you had to pay for credit monitoring. They are asking for the service now to presumably reduce the cash payouts though.
It comes in handy with economic discussions, (barters, trades, etc.) as well as general debates / arguments with peers. There's many behavioral economic games and pro-social experiments in game theory that deal with improving social perception or increasing the odds of outcomes with framing / anchoring / priming.