Episode Calendar

@simonbs I swear I had the same idea maybe 6 months ago 😂👌 now I don't have to build it

I’ve been working on something… and it’s now on the App Store! 👀 Introducing brrr 🚀 Push notifications to your own devices. Instantly. No signup. No dashboard. No nonsense. Link in 🧵

@mindtripai are you shutting down? Maintenance for several days

@marclou So it sold for 100 bux, if the fee is 3% ?? lol

✅ ACQUIRED Invoice management startup sold. It took 38 days.

@heygurisingh Let me fix that for you :) - Claude for coding ($100/mo) - AWS SES for emails (~$0.10/1000 emails) - WorkOS for auth (Free until 1M users) Fixing free limits on Hetzner: (Starts at $6, but $24 gets you A LOT more) - Swap Sentry with GlitchTip - Any Redis/Database(s) you want

@marclou Why not keep it running for 1-2+ years? (Assuming its mostly passive and little maintenance). Worth way more than 3k?

✅ ACQUIRED AI startup making $200/mo sold for $3,000. The founder received 8 offers, and it took 50 days from listing to closing.

@naiivememe Worth!

2 sticks of ram cost $1000 because of this shit

@amaiashalo haha great :P !

@EpisodeCalendar it's working ok now

Show images/banners are broken atm. Unfortunately I'm traveling until the 4th, and I might not get that fixed until I'm back 😭

@amaiashalo i'm sorry that you're facing issues, but its not something on our side. i've also tried using an argentinian VPN to test from your location its something with your browser/router/internet-provider :/ nothing else i can do there

@EpisodeCalendar Hi, still not working for me. I’m from Argentina.

@fakoukas awww, how sweet of you! <3 🤩

After all these years @EpisodeCalendar still remains the best. By far. Shout out to this incredible website I've been using for more than 15 years!

@amaiashalo Hi. It's working fine here. Is it still down for you?

@EpisodeCalendar the whole site is down 😭

@puppeteer_0 @evanyou @1Password And what about on your other devices and sync?

@evanyou @1Password Use Chrome's built-in password manager, it's the purest and most sandboxed option

.@1Password browser extension is injecting Prism.js *globally* on every page, which then applies its syntax highlighting logic on all blocks matching [lang=*] regardless of whether it’s meant to be compatible, thus breaking original highlighting. Terrible negligence and even more so that this made to prod while already flagged during beta. Been a user for a long time but this will def push me to an alternative if not fixed soon.