Interesting idea! I have considered whether to extend the same sort of system beyond word stories and also create animated videos and things. An interactive RPG or role playing aid like you suggested would be cool though!
It's safe to say the broadband market in the UK is dominated by terrible, mass market ISPs. They lock people into long contracts, provide crappy routers, throttle speeds etc. I recently launched an alternative aimed at gamers, and I'm really trying to find out what people prioritise most.
So if you're a serious gamer, what is important to you?
Low latency?
Fast download and upload speeds?
No contract?
The ability to "tweak" your connection to minimise latency to specific game servers?
Top tier hardware provided?
Love this! It's so much better than the ones I have been using where the page is filled with ads and clutter. Will bookmark this and use it next time I need to.
Awesome thanks for trying it out! Yeah that definitely aligns with the goal of positioning this as an assistant rather than a tool that does everything for you, and I've also found the same when using it myself! I'll have a think about how I can make that page more valuable, Would maybe adding things like keyword research and predicting impressions/search volume for each of those ideas be helpful?
> I'll have a think about how I can make that page more valuable
With any idea I like to think of two things:
- how many other people will executing this idea help?
- how much will I grow in the right direction by executing this idea?
So maybe you could have the AI rate these to.
Impact on Others score. Personal growth score. Honeslty I'd probably just add like 2 - 3 other columns to https://app.getmarketerai.com/content/ideas, and continually experiment with new ideas until you have 3 great ones.
I'd almost hide every other feature/page and really hone this.
What you are helping people with is not the last mile downstream task of crafting individual idea, but the far more valuable and important and impactful upstream task of choosing among the infinite ideas one could do.
From what I can tell, most apps I use now at least enforce some kind of minimum password requirements e.g must be so many characters long, have special characters etc.
I guess the data used for this comes from security breaches, so maybe there's a bias in the data towards less secure apps that don't enforce strong passwords.
Yeah I absolutely hate that. I get why they do it from a business point of view but as an engineer, I'm instantly put off when I see something along the lines of "up to $x (depending on location)".
Ah ok, it's using Sendgrid (free tier) for the emails so perhaps that's impacting deliverability - I have found in the past the shared IPs can be hit and miss. I'll look at switching to a paid service and make sure there's a way to have the email resent if it doesn't deliver.
Sure, I'll look into cleaning up the error messages and providing a demo app next.
This functionality is how stytch and passage both started.
One raised a bajillion dollars and is continuing to push identity forward and the other was acquired by 1password, so this project could have some legs.
There are two factors to consider here, and those are "Will it work?" and "Will the UX be good?".
Will it work?
What we need to look for here is support for Webauthn, we can see here that all of the popular browsers support Webauthn - https://caniuse.com/?search=webauthn across desktop, iOS and Android, covering ~96% of all users.
Will the UX be good?
This is where we start to look at support for things like biometrics and generally, we'd prefer that user's passkeys are secured on their devices using biometrics rather than a PIN. In this area, the support is good across modern mobile devices (fingerprint and/or face id) and many newer desktop devices (e.g touchid). Probably the most obvious limitation here is a desktop device with no support for biometrics, however, Webauthn has a neat solution here where a user can link up this device with their smartphone using either bluetooth or by scanning a QR code - this then allows the user to login using a desktop device with a passkey secured on their mobile device.
Most of the popular password managers now also support passkeys, so that's another workaround that works well in many cases.
Passkeys use public key cryptography, so in this case we have a private key that remains securely on the user's device, and a public key that's stored on the server. Most modern devices are able to secure the passkey using biometrics, but users can also choose to use a password managed that supports passkeys.
The only user data required right now is either an email or mobile number, which gets verified using a code that gets sent to the email or mobile number used. The working assumption is that any consumer of this would use it alongside their own database, so there's probably no need to store anything other than the email/mobile (or username in WebAuthn terminology, this doesn't technically need to be an email or mobile, but I chose to do this so I could add a verification step to help prevent abuse of the system).
The passkey is created by the user's device and then the public key part of it is sent to the server during user registration.
