3 ms·
I don't track people in the first place on my websites, but third party content is a good point. I generally will self host all of my assets, but occasionally e
by Sir_Cmpwn 9y ago
I don't track people in the first place on my websites, but third party content is a good point. I generally will self host all of my assets, but occasionally embed a YouTube video or something. I should probably put it behind a click-to-enable thing. I removed Disqus comments from my blog a while ago, too, because a platform for flamewars isn't worth tracking visitors over.
- hughw 9y agoA non-tracking, embeddable comments widget would be a Good Thing. I wonder if anyone would pay $12 a year for that service, and whether that would be enough to support it.
- Sir_Cmpwn 9y agoWhy? A 12 line open source JavaScript library would do the same thing and wouldn't have to hit up external services in the first place.
- hughw 9y agoOh off the top of my head: - You have to persist comments right? 12 lines of JS? - You generally want some sort of (cross-site) user management - Spam - Moderation Seems a bit more complex than 12 lines of js. [Edited to add 'cross-site']
- Sir_Cmpwn 9y ago12 lines of JS to display a button that dumps arbitrary HTML into the page when clicked (i.e. the third party widget). But I see now that you were talking about a non-tracking comment engine - my bad. I personally wouldn't pay for such a thing. The current model I have post-Disqus is to have private comments emailed to me and public comments written in the form of blog posts that I'll link to at the bottom of the article.
- myrion 9y agoWell, you can use something like Isso, perhaps: https://github.com/posativ/isso https://github.com/posativ/isso
- hughw 9y agoThat's pretty good. I guess the idea that you would want cross-site identity is, really, tracking. The only benefit to the user would be some universal name and photo that remains the same across all sites. But that's a really marginal benefit. This isso project gets 98% of usefulness.