3 ms·

I like Cassidy James' idea of linking a blog post to a Mastodon post[1], and showing the corresponding social interactions as a comments section at the bottom o

• jszymborski 2y ago
  Shameless plug, but I wrote a post on the pros/cons/implications of using Mastodon to power a comments section: https://jszym.com/blog/mastodon_blog_comments/ https://jszym.com/blog/mastodon_blog_comments/
  • jefftk 2y ago
    I do this too, and I like it a lot: https://www.jefftk.com/p/mastodon-replies-as-comments https://www.jefftk.com/p/mastodon-replies-as-comments > Using Mastodon to power our comments means that every time someone visits the blog post, the user’s browser makes a request to your Mastodon instance. ... I’d proxy these requests through my server, but it’s yaks all the way down. I do proxy these, and it's not too much work [1]. A major reason to proxy is so you can cache: if a blog post gets HN'd it could easily get more traffic than your Mastodon instance would like to receive. [1] https://github.com/jeffkaufman/webscripts/blob/master/comment_requester_wsgi.py#L414 https://github.com/jeffkaufman/webscripts/blob/master/commen...
    • aethertron 2y ago
      I would simply throttle those requests. Update comments once an hour. Or once a day. Not everything needs to be realtime.
      • xd1936 2y ago
        I think by "proxy the requests", they mean, these are usually on a static site and the browser is directly pulling in the Mastodon content client-side. They want to be good citizens and add a caching layer that they run.