Yep, but I made mine first 😬 I believe we were both inspired by the work of Karakurist.
Yep, but I made mine first 😬 I believe we were both inspired by the work of Karakurist.
Yes, absolutely. Just needs one motor per digit.
The video exagerates it a bit. But it is audible. Of course the clock will only move once a minute.
It is digital because it has digits instead of pointers. It is also digital in the sense that it has discrete states.
This obviously falls into the “documentaries and essays” category
In the cases you describe it should fail by ruining the print, not the build plate though. If there is something between the nozzle and the plate, it will be too far away from it after calibration, not too close.
The Github UX is amazing if you ever had to use gitlab or bitbucket
jreg
There is no snapping, but the geneva drive will stay locked in position when it is not moving. The thing that I haven’t figured out is how to get the 3 to go back to 0 after 23:59, it needs to skip the numbers 4 to 9.
I’m testing a geneva drive (you can see it in the front in the photo), that should allow me to reduce the number of motors even further. I think I can get it down to two, maybe even one.
This video was the inspiration for my project!
Yes! 🤓
I like using AntennaPod for podcasts and Spotify for music.
Nobody knows if and when programming will be automated in a meaningful way. But once we have the tech to do it, we can automate pretty much all work. So I think this will not be a problem for programmers until it’s a problem for everyone.
Thank you for writing the explanation! I still think that this doesn’t need a blockchain. Instances could broadcast user creation, so each instance could validate user age on its own (or ask other trusted instances when they first “saw” that user).
Fundamentally, blockchain solves the problem that there is no central source of trust, but in the Fediverse people necesarily trust the instance that they sign up, so a blockchain can’t add much in my opinion.
I see. I’m not convinced that proving the account creation date makes much of a difference here. Obviously the instance records when you sign up, so you would only need this to protect against malicious instances. But if a spammer is manipulating their instance to allow them to spam more, you have a much bigger problem than reliably knowing their account creation date.
this account holder has this name on that instance
How would that help? A spam bot could just make lots of blockchain wallets.
you get all sorts of unspoofable benefits from that
what are the benefits? I struggle to come up with any benefits.
I got that idea from this design.