3 ms·

If it's still not working for you without JS, that's either a bug in my site or your browser (the noscript includes a link to the text version and GitHub), not

If it's still not working for you without JS, that's either a bug in my site or your browser (the noscript includes a link to the text version and GitHub), not a design decision on my part. Can you access this link? https://anderspitman.net/txt/17 https://anderspitman.net/txt/17

FroshKiller 7y ago
Yes, but linking to the text version instead of simply providing the text is hostile to the user. You know what resource I requested. You know where that resource is. Give me the resource.
- anderspitman 7y ago
  I agree it would be ideal to return a static HTML file for direct requests. I'm working on adding that back in. But I think the /txt version of the site is still valuable. I tried to come up with a way to return it without requiring a separate URL, but short of doing magic on the server (such as detecting user agent) couldn't think of a way to do it without having nasty HTML in the result. Any suggestions? EDIT: I updated it to HTML-redirect to /txt/feed for noscript users. Still not ideal if you're trying to find a specific post, but it includes instructions to help. I think it's a reasonable compromise.
  - FroshKiller 7y ago
    Yeah, that works. I'm glad you're willing to put in the work, but I have to tell you, if you'd just focused on delivering the content and followed the principle of progressive enhancement, you'd be delivering a better experience for probably the same amount of effort at this point.
    - anderspitman 7y ago
      I think something that got lost in the conversation is that a big part of my personal site is experimenting with different ways of delivering content. My current experiment was to see if I could serve a git repo as-is without any build step, and what the trade-offs would look like. Unfortunately everyone just assumed I was ignorant or lazy.

3 ms·

If it's still not working for you without JS, that's either a bug in my site or your browser (the noscript includes a link to the text version and GitHub), not

by anderspitman 7y ago

FroshKiller 7y ago
Yes, but linking to the text version instead of simply providing the text is hostile to the user. You know what resource I requested. You know where that resource is. Give me the resource.
- anderspitman 7y ago
  I agree it would be ideal to return a static HTML file for direct requests. I'm working on adding that back in. But I think the /txt version of the site is still valuable. I tried to come up with a way to return it without requiring a separate URL, but short of doing magic on the server (such as detecting user agent) couldn't think of a way to do it without having nasty HTML in the result. Any suggestions? EDIT: I updated it to HTML-redirect to /txt/feed for noscript users. Still not ideal if you're trying to find a specific post, but it includes instructions to help. I think it's a reasonable compromise.
  - FroshKiller 7y ago
    Yeah, that works. I'm glad you're willing to put in the work, but I have to tell you, if you'd just focused on delivering the content and followed the principle of progressive enhancement, you'd be delivering a better experience for probably the same amount of effort at this point.
    - anderspitman 7y ago
      I think something that got lost in the conversation is that a big part of my personal site is experimenting with different ways of delivering content. My current experiment was to see if I could serve a git repo as-is without any build step, and what the trade-offs would look like. Unfortunately everyone just assumed I was ignorant or lazy.