Something I have noticed over the years is that replies to my blog posts that are made on the blog itself, rather to the blog-post-breadcrumb on the various social media sites, are of significantly higher quality.
Maybe the difference is that people that read your blog regularly is a special subset of creative / tech people that know who are replying to and your role in tech industry, and the rest of comments that come from elsewhere are a bunch of randos which don't know you and just "shoot on sight" and reply to everything they see on their timeline.
On social media, the full text is rarely there. Most folks are responding to the title or blurb
Social media perhaps inherently contextually devalues all content, because readers see every post as one nugget in an endless stream of random information, drastically different in quality and tone. On your site, that context is much different, probably better preparing visitors for thoughtful reading.
@jxn@jwz "On social media, the full text is rarely there. Most folks are responding to the title or blurb"
I think this is a lot of it. Some people love expressing an opinion, even if they haven't made any effort to do the reading or learning, etc., that might make their opinion worth considering.
@jernej__s Every now and then someone tells me that they have site-timeout problems, but I have never seen any evidence of it. The site is hosted in AWS us-east-2b so connectivity should be just fine. CPU never goes over 50%, there are no alarms, and all of my network graphs look reasonable going back 6+ months.
There was the "Mastodon stampede" problem but I worked around that in 2022.
So if this really happens to you "most of the time" I'd love to see more details.
@jwz The weird thing is, that only my home IP (84.255.206.8) is affected; if I try from any other IP, the site opens just fine. Also, even though the HTTPS connection fails, I can ping jwz.org just fine.
Add comment