401–408 of 408 posts
Earlier quoted context omitted.
You have a curated directory of actually decent stuff, and you list the item there. Don't wrestle with the pigs.
What do you do with the other two wishes from the genie?
Earlier quoted context omitted.
Consider that Hacker News does not advertise, and yet somehow you are here.
Hacker News does not depend on me buying products from it for it's survival. If you can't see the difference in why a company cannot depend on word of mouth, then you're just really not trying to have an honest conversation.
Earlier quoted context omitted.
The issue is that (some) smart devices are known to bypass local DNS servers entirely. They either use a public DNS server or hardcoded IPs. The best thing would be not to connect any "smart" TV to the Internet. These are closed firmware devices with cameras and microphones and they just can't be trusted.
>bypass local DNS servers There are easy ways to fix that at the router level, but DNS-over-HTTPS clowns ruined this.
I don't like DoH due to the central gatekeepers its current implementation in browsers encourages but I don't think it really changes anything here.
Mailing lists are still the superior format. The barrier to entry is a feature and not a bug.
They are not suitable for one-off comments on a blog post. In particular, I'm not even sure how you could make it possible for a normal user using a standard mail client to reply to a comment that was posted before they came across the blog post.
I used to use Disqus on my blog a long time ago, but dropped it with one of the many reboots. Having comments on a blog still seems like a good idea but I'm still half minds over on-page vs fediverse-based discussion, or maybe even both. Spam is a constant problem. One alternative I've come across while researching this was https://cusdis.com/ - has anyone tried this?
Earlier quoted context omitted.
What do you do with the other two wishes from the genie?
If no one chooses to be the change they want to see in the world then things can only keep getting worse.
How would that make the world better?
Earlier quoted context omitted.
Your implementation might be static json files, but it's not impossible to force other filetypes in there. This in itself makes it high risk? Allowing force-push is considered an antipattern for Git, and generally best avoided. It's a safeguard against lost history and prevents data loss. That aside, the comments are the history. Git is the wrong tool for the job. Why would you choose a generic version-control system…
> it's not impossible to force other filetypes in there. This in itself makes it high risk you mean other files will bloat the repo and slow down the performance? Yes it's a very valid concern, but this system targets personal blogs, which I assume had very few comment traffic. > Git is the wrong tool for the job ..... A database ... is a far superior choice in just about every possible way the same argument applies…
I still wouldn't put them into Git along with the rest of the site, that's a definitely no-no. A separate Git? Also no for me. Filesystem does seem viable on reflection, and I feel inspired to explore this now.
Earlier quoted context omitted.
Right? I'm confused. Saying "oh the ads are in the audio file" is exactly like saying that "the ads are in the html file." It's not like the client app is inserting them. I mean, I guess I can imagine an exceptionally-scummy podcast app, but that's not what we're talking about here.
Hosting services drop them in. You sign an agreement with them and they have agreement with advertisers who drop their spots into your show using DAI. Often it’s a straight up bid-system but the podcasters are not part of the process, or the podcasters can do the read and hand it over to be inserted. This means that podcasters in a lot of situations don’t actually know what ads are being run on their show. These ads…