HN user

eaplmx

12 karma

https://eapl.mx

An engineer creating stuff for humans

Guadalajara, MX

Posts0
Comments12
View on HN
No posts found.

Nice question! Let's see...

CLI - TOTP/2FA tool with fuzzy search - A script on top of timetrap, to type a number and change your current activity (emulating a Timeflip) - A simple view of % of time spent for each activity - A few scripts on Python, PHP or Go to automate stuff at work

CLI/Web - http://gemugami.com/week/ Get the current ISO week

Web - A site to ask people of their preferred time for a meeting, trying to find one working for all (quite difficult :) - https://eapl.mx/price/ Compare price and sizes/weights of 2 products to know which one is 'more' convenient - https://eapl.mx/twtxt/ A public view of my twtxt microblogging, and a single-user admin view - http://gemugami.com/time/ Get your browser's timezone

Not tools, but quite interesting - http://gemugami.com/hexclock/ An hexadecimal clock - http://gemugami.com/clock/ A decimal clock ('hours' from 0 to 1000) - http://gemugami.com/kcolc/ Time goes in reverse from 24h to 0 - http://gemugami.com/solar/ Shifts the time to be 7am at sunrise, based on your location - http://gemugami.com/holmes/ A scoring app for a board game

And a bunch of game prototypes, mostly to learn new stuff and game design

Something overwhelming of WebAuthn/U2F/FIDO2/Passkeys is that it has many different modes and settings [0] So, my understanding is that you need to find the settings to 'upgrade' the modes from 2FA to a Passwordless alternative. Not all devices are supported.

I like this explanation in Ruby [1] [2] of all the process between the server and the browser. It also has an example you can try on your browser to see if your devices/OS are supported. Look at the bottom the distinction between Passwordless and 2FA.

I'm making a proof of concept of WebAuthn the only login option, for a toy project in PHP [0] with this library [1] It has been an interesting exercise to understand the tricky parts of it.

[0] https://webauthn.lubu.ch/_test/client.html

[1] https://betterprogramming.pub/implement-a-passwordless-authe... [2] https://archive.ph/SyaEW

[2] https://eapl.mx/twtxt/ [3] https://github.com/lbuchs/WebAuthn

A problem with open and free projects (to oversimplify the ideological differences) is the source of time and purpose.

The production cost is subsidized as a Hobbie not as a profession, so it's hard to expect a 'consumer product'. When you put external money and corporate interest in your hobbies, something breaks.

Not saying open products don't have to exist, we all love them. They cover different creative needs, and usually are a gift for the community.

https://apenwarr.ca/log/20211229 - The Gift of It's your problem now

Web3 is the solution to all our problems!... obviously not

But something I've seen is that is making mainstream using private and public keys. We have Client certificates but those are hard to create and use, and not really compatible with mobile.

I think a good workflow will be something similar to connecting to SSH, instead of a static password you sign a challenge with your key pair.

I have a few weeks thinking of replacing the social login (FB, Twt, OAuth) with wallet login https://github.com/amaurym/login-with-metamask-demo

It happened similar to us. A payment arrived late and everything was deleted. I promised to never use DO again, but the low price makes sense for a small project being made by an indie games company, so here we are again.

Luckily for us we added redundancy on payments and alerts, so I hope we won't be in the same case again.