91–100 of 113 posts
Back in 1997 I was studying overseas and we didn't have internet access, but we did have e-mail access over uucp. There was a service back then which would end you a text mode version of a web page (which would probably be much harder today, as users of w3m or links could attest) and we'd have it setup to email us the scores every night. 25 year younger me would have loved this site for that. :)
Earlier quoted context omitted.
To clarify: Are you indicating that, as a user dependent on screen readers, that this site is difficult to use for you? Do other users who depend on screen readers have an experience they’re willing to share about visiting this site?
This is something that frustrates me: it's actually really hard to design for screenreaders because it's hard to actually check the results in a free/volunteer context. So you often just have to just hope you're being "semantic" enough. And I did try to use Orca but I just could not get it to work, the TTS service was sulkily disinclined to accept any requests.
I did a `curl https://plaintextsports.com/mls/standings ` and, to my surprise, got an HTML response back (rather than just plaintext data). Seems like this isn't actually plaintext (as in the mimetype `text/plain`), but is instead just "minimalist-aesthetic sports" (with the caveat that for some reason there's CSS styling to make the font unreadably small at 2560x1440, which was what led me to try `curl` in the first…
$ curl -X GET https://plaintextsports.com/ -H 'Accept: text/plain' | head
Plain Text Sports
Where do you get your data from? I've found sports data (especially odds/lines) to be overly expensive when trying to build hobby apps.
Earlier quoted context omitted.
I actually have no idea what you just said (and you can believe it). But I'll Google "local decryption proxy" and see if that's something feasible I could try with, say, my Powerbook Pismo running macOS 9.2 with no modern browsers. I'm no engineer, so please don't assume everyone here is.
This site is specifically targeted to software engineers, so it's a reasonable assumption that we can talk about the relevant topics without having to simplify things for people outside that group. For a reverse proxy, you would want a computer capable of the encryption methods the modern web's security standards demand and to install a web server on it which you can access from the older computer. The server compute…
I thought it was for VCs and founders too. And PMs.
Earlier quoted context omitted.
To clarify: Are you indicating that, as a user dependent on screen readers, that this site is difficult to use for you? Do other users who depend on screen readers have an experience they’re willing to share about visiting this site?
This is something that frustrates me: it's actually really hard to design for screenreaders because it's hard to actually check the results in a free/volunteer context. So you often just have to just hope you're being "semantic" enough. And I did try to use Orca but I just could not get it to work, the TTS service was sulkily disinclined to accept any requests.
Hey, HN! Creator here! I started building Plain Text Sports last year when I was watching an NFL playoff game in rural southwest Wisconsin. We had poor TV reception -- the image was going in-and-out -- and the local radio station was mostly static. I tried to check ESPN, but the loading bar was as frozen as the ground outside. I then had the idea for a website designed for the pure sports fan: no ads, no images, just…
Earlier quoted context omitted.
This site is specifically targeted to software engineers, so it's a reasonable assumption that we can talk about the relevant topics without having to simplify things for people outside that group. For a reverse proxy, you would want a computer capable of the encryption methods the modern web's security standards demand and to install a web server on it which you can access from the older computer. The server compute…
> This site is specifically targeted to software engineers I thought it was for VCs and founders too. And PMs.
Earlier quoted context omitted.
I actually have no idea what you just said (and you can believe it). But I'll Google "local decryption proxy" and see if that's something feasible I could try with, say, my Powerbook Pismo running macOS 9.2 with no modern browsers. I'm no engineer, so please don't assume everyone here is.
This site is specifically targeted to software engineers, so it's a reasonable assumption that we can talk about the relevant topics without having to simplify things for people outside that group. For a reverse proxy, you would want a computer capable of the encryption methods the modern web's security standards demand and to install a web server on it which you can access from the older computer. The server compute…