That's true, provided that all activity (comments, voting) here is still coming from actual humans. That's no longer the case for community websites, I'm afraid.
It's an experiment made for the web of 2026, where you can no longer tell if the users are humans or bots.
If nobody's interested in that idea, I accept that.
I submitted a somewhat similar project yesterday to Show HN (didn’t resonate), although mine is purely based on AI scoring, with zero community features.
I call it bubblewire. Funny. I had no prior knowledge of bubbles.town until seeing it here now.
bubbles.town looks nice! Hope to see more projects that aim to bring back the good old web.
Yes. I run a niche webapp[1] that extracts exif and xmp (Lightroom edits) from images. At one point I tried to write my own exif parser. It's not that complicated, but very quickly you'll run into weird legacy, vendor-specific nuances (apart from what the parent mentioned, you have to handle both big & little endian exif). And the long tail of those edge cases is, well, very long. Exiftool handles pretty much all of that.
I have a TODO.txt and it’s the only productivity system that I’ve ever been able to stick with. Just a list of stuff I need to do, what’s done gets moved down or deleted. Maybe there’s value in having an archive (a DONE.txt?) but I’ve found that after a while most notes/items lose the context and often it’s hard to decipher what they were about.
One thing I haven’t figured out yet: I’d love to be able to keep this file open at all time, have it pop up with a hotkey. Currently it’s just a TextMate window that I often close by accident.
You make some good points. What I was trying to say is that even though there is the RFC, it's quite common to modify the alphabet or use other variants like Crockford's (mainly to avoid random profanity, e.g. in the URL identifiers).
When you see a Base64 string, you can be pretty certain that it's the standard version. With Base32, it's not obvious which variant was used.
Many languages don't provide a stdlib Base32 implementation (Ruby doesn't), but Base64 is pretty much always included. Maybe this influenced my perception of the lack of a universal standard.
Anyway, I should work on that section to communicate my point better.
It's a micro-SaaS for photographers who edit in Lightroom. Lets you reverse-engineer Lightroom edits from JPG files and download them as presets that you can apply on your own photos.
Took a month or two to reach $2k/mo, riding the wave of instagram's popularity in 2017-2018, plus the project went viral initially. However, the niche is ultimately too small to grow the revenue significantly. Still chugging along, almost 6 years later, though.
Taleb's Incerto (Fooled by Randomness, Black Swan, Antifragile, Skin in the Game).
Opens your eyes to a wide array of fallacies that govern our daily life (unknown unknowns, "experts" explaining past events as obvious in retrospect, the news, predictions, survivorship bias, confirmation bias, iatrogenics and a lot, lot more) — almost to a fault, i.e. if you take it too far, you'll see these fallacies everywhere and things like stories of success/failure, biographies (or history in general) etc. will no longer make the same impression.
OP here, thanks for clarifying this - I can imagine it's a super complex problem and I truly appreciate all the work that you (and other contributors) have put into this project.
My only point (and a source of confusion) here is that I never anticipated the cascading effect that installing a single package can have on seemingly unrelated parts of the system. I've been using homebrew for many years and as far as I remember, the only time anything broke like this was when I explicitly ran update/upgrade.
I'm going to try HOMEBREW_NO_INSTALL_UPGRADE/HOMEBREW_NO_AUTO_UPDATE — it does seem like a more intuitive default, but again, I don't know anything about how homebrew works under the hood.
C in Polish is pronounced as ts/tz and 'ck' is an interesting case in Polish-American surnames: American pronunciation turns 'ck' into 'kk' and Polish speakers will often have a hard time recognizing the original spelling.
Listening to audio mentioning Susan Wojcicki, I could never figure out the spelling of her name... BTW, Polish pronunciation for Wójcicki (notice the 'ó') is Vooy-chits-ki
Agree, this is a huge pain point when dealing with multiple clusters. I wrote a wrapper for `kubectl` that displays the current context for `apply` & `delete` and prompts me to confirm the command. It's not perfect, but it's saved me a lot of trouble already — but encouraging other members of the team to have a similar setup is another story.
Totally agree. Docker for Mac performance is just unbearable when dealing with a semi-large webapp. I recently moved to remote development – macOS with Ubuntu running in VM (VMware) via Vagrant. I edit code using VSCode & Vim (via SSH & tmux tabs in iTerm2).
Based on my benchmarks it's more than twice as fast as Docker for Mac – and only minimally slower than native Docker running on a Dell XPS.
I'm enjoying this setup so much that I'm considering moving all my dev-related tools to a VM (which will hopefully allow me to get rid of homebrew too).
Implemented this recently in my SaaS app, replacing passwords with magic links and it was a mistake. Sure, it has some obvious benefits: it forces users to always provide a valid email and logging in confirms that the email address is valid, without any additional logic.
But moving auth logic to email links has increased my customer support work significantly: "I can't log in", "I didn't get the link" complaints are quite common now. People use email they didn't sign up with, messages go to spam, arrive with a delay - or recently, gmail outage caused messages to hard-bounce. These are only some of the issues I've had to deal with in the last few weeks, that never came up when I had password auth.
Also, I've found that some email clients automatically follow links included in the message and that meant login link was invalidated before user got a chance to click it. I've solved it by adding a button on the page, but it's not ideal.
Magic links were supposed to be convenient, but they cause a lot of frustrations for some users. Keep that in mind.