Isnt email blacklisting/actually getting mails to inbox infamously hard? I otherwise think the rest of the stack is indeed solved, but its probably cheaper to pay Amazon SES or whatever for getting your emails to an inbox reliably
Email receivers (be it Gmail or your local council) don't differentiate if you're self hosting or a business. So long as small businesses can manage (who have like one part-time sysadmin that also manages a ton of other IT stuff; email doesn't take much of their time), so can you. If you set up the usual suspects like SPF and DMARC, the domain is not a known spammer, and the IP not in a blocked address range, it's mostly hands-off (source: I self host my email)
If you need it to really be super reliable, yeah, you need to send through one of the big companies who have not just a dedicated sending IP address but entire ranges dedicated to email sending, as well as staff that will respond to delivery issues 24/7. Microsoft rejecting email from Google and vice versa isn't unheard of, so there aren't guarantees anywhere, but that would be your best bet. For my personal use, that extra nine of reliability isn't needed
Copyrights protect the literal text of your program and binaries. Not the design and functionality. Getting Sherlocked is having your functionality duplicated, independent of the code itself.
No one thinks Apple violated Sherlock copyright. They just made it (nearly) functionally redundant.
vercel-labs/emulate [1], has stripe and twilio (their emulators are much more shallow generally like their AWS one can't really be compared to floci here, but i've made custom ones for stuff like emulating hardware devices (airplay/google play) with much success so you can basically extend their base framework with custom emulators or their own provided ones to your needs on a fork.
for modelling and testing a CI software i was working on, i had to extend their github emulator in several places for example. but it was great to already have a working base.
Usually also, and more so nowadays, a few of the public sources of data left, even after the recent USGov intention of defund and close as much of them as possible, im guessing would be precisely, government websites!
You could have local caches of the users recently watched videos on their machines as available seeds. bittorrent now also supports http based init seeds so you could create torrents with a verified sha of a youtube mp4 downloaded once or something like that.
if someone is seeding that video cause they recently watched it and it remains on their local cache, you could get the bits from there vs hitting youtube servers
That works if you fix everything to a single quality and codec. YouTube videos tend to have something like 20+ variants that can get dynamically switched between while the video is playing (adaptive streaming).
The client can pick the optimal encoding and quality which makes that quite a bit more difficult. A user on a modern device that can hardware decode HDR av1 will have a file cached completely useless to a browser that can only do SDR h264.
I think there is a sort of network effect needed to make it become reasonable.
Why is that the right tradeoff? It seems like the Plex/Jellyfin ecosystem has landed on keeping high quality persisted and hardware accelerated transcoding for everything else. Put another way, transcoding capable caches.
I'd be interested in seeing data that supports this.
Netflix reported in 2025 something like 30% of traffic was av1. I think smartphone and PC support are fairly robust but under the impression streaming devices are still quite terrible unless it's a Chromecast.
AVC/h.264 is the only thing I know of that's pretty much universally supported at this point. I found a Facebook/Meta report citing some consultant provided data that VP9 was a close second. Limiting to devices from the last few years, HEVC might work.
reply