Also, on the topic of MicroZig documentation, where is the recommended place to start for consumers of the library? A lot of the documentation seems geared toward people who want to contribute to the library but I’ve had a hard time finding documentation aimed at people who want to use the library as a client.
He’s not completely wrong with most of the topics, but fundamentally the only one I care about is that passkeys in the current form are just a terrible user experience for most people who are not either using iphone + macs or a single android device.
I have 3 different OSes on my m
ain computers and an android phone. I don’t want my passwords to by synced by Google, if I can avoid it. I especially don’t want them synced to any MS Cloud and I actually trust Apple a bit more here, but not much.
If I were to accept passkeys I would need the following things:
I can add an arbitrary amount of devices, and none of them need to have a webcam, only a network connection
Nothing needs to live in any $BIGCO’s cloud sync
and yet some form of (printable/savable) backup OTP code is a bonus
Most “yay passkeys” pieces I have read so far assume I either never lose my phone, my phone never breaks, I don’t use Linux, or I want to sync my passkeys to someone else’s cloud.
And yes, losing access to my accounts is a much more real threat to me than someone stealing my long password.
Seems like Bitwarden might be of interest to you. I have had a pretty seamless experience storing and using my passkeys with it (across Linux and Android personally, and Windows for work).
You can also self-host a personal sync server if you don’t want to use theirs.
thanks for the pointer, I’v trialed vaultwarden in the past and I am not comfortable with it being exposed on the internet, or me having to run a VPN, and in general KeePass has worked out better for me.
I find that my individual side projects are what scratch this itch, for freedom from corporate incentives and requirements.
A lot of the code I write in my spare time is hyper-specific to me. It doesn’t look nice, it usually isn’t very good, but that doesn’t matter. I am the only user. If I get fed up with it, I can just shut it down, or completely rewrite it.
I guess we have to work a lot on our docs and presentation, as MicroZig ships a pretty nice SSD1306 driver already!
But it’s nice to see people are using MicroZig in the wild!
That’s great to hear! It’s wouldn’t have been half as much fun for me, but it’s cool to see the barrier of entry being constantly lowered.
I think I might have actually been doing this before the official driver was available, if this is the commit. I’ll update the title with the year.
Direct link for anyone curious:
https://github.com/ZigEmbeddedGroup/microzig/blob/ce28cf330a1e290a63eb3f9961c3c85f4eb2e02b/drivers/display/ssd1306.zig
Also, on the topic of MicroZig documentation, where is the recommended place to start for consumers of the library? A lot of the documentation seems geared toward people who want to contribute to the library but I’ve had a hard time finding documentation aimed at people who want to use the library as a client.
I guess the best we have right now is just checkout out the examples in the MicroZig repository
I like this idea, even if only for creating a proper changelog.
He’s not completely wrong with most of the topics, but fundamentally the only one I care about is that passkeys in the current form are just a terrible user experience for most people who are not either using iphone + macs or a single android device.
I have 3 different OSes on my m ain computers and an android phone. I don’t want my passwords to by synced by Google, if I can avoid it. I especially don’t want them synced to any MS Cloud and I actually trust Apple a bit more here, but not much.
If I were to accept passkeys I would need the following things:
Most “yay passkeys” pieces I have read so far assume I either never lose my phone, my phone never breaks, I don’t use Linux, or I want to sync my passkeys to someone else’s cloud.
And yes, losing access to my accounts is a much more real threat to me than someone stealing my long password.
Seems like Bitwarden might be of interest to you. I have had a pretty seamless experience storing and using my passkeys with it (across Linux and Android personally, and Windows for work).
You can also self-host a personal sync server if you don’t want to use theirs.
thanks for the pointer, I’v trialed vaultwarden in the past and I am not comfortable with it being exposed on the internet, or me having to run a VPN, and in general KeePass has worked out better for me.
This post has inspired me to pare down my bloated nvim config, and get back to the speed and productivity that I switched for in the first place!
As a side note, what is the font that you are using? It looks really nice.
Looks to be Input Mono. It is indeed a really nice font.
Awesome to hear! Good luck on the quest.
The blog fonts are Inter and IBM Plex Mono. The terminal font (in Alacritty) is Jetbrains Mono.
I find that my individual side projects are what scratch this itch, for freedom from corporate incentives and requirements.
A lot of the code I write in my spare time is hyper-specific to me. It doesn’t look nice, it usually isn’t very good, but that doesn’t matter. I am the only user. If I get fed up with it, I can just shut it down, or completely rewrite it.
Especially when that side project is in go. Just go be direct, it’ll be fine.
Off-topic, but I love the UI for playing audio files on this site!
I can’t recommend the videos from Sebastian Lague and Freya Holmér enough!!
+100 for Sebastian Lague!
Missing from this history: at some point in 2023 the attacker makes artwork https://tukaani.org/artwork.html
The level of effort borders on this.
Wasn’t sure what you meant since the xz logo has since been removed, was visible in the last IA snapshot: https://web.archive.org/web/20240402213236/https://tukaani.org/artwork.html
This seems an odd thing to do for someone seeking to add a backdoor.
The only thing I can think of is to gain some more credibility, but at this point they were already a fully established maintainer.