3 ms·
Show HN: Only API Web (Or with JSON). Experimental Web
- chovyfu 6y agoyaml would have been a better choice. Easily convertible to JSON and back yet human readable.
- zzo38computer 6y agoAnother possibility is just plain text (or text/gemini). JSON doesn't seem suitable for just ordinary text, although when you want to provide data, JSON (or other formats, such as CSV) would work better than using plain text or HTML, I think. APIs are also helpful, although documentation would be needed.
- sawirricardo 6y agoHi, true indeed @zzo38computer. I see that there are 192 total page visit as of this writing, 186 page hit on the home route, and 5 page hit on the about route, and 0 page hit on the subscribe route (thus, 0 subscribers :')) I don't want to come to conclusion this fast, but my prediction is that almost everyone have a hard time navigating with json view. What do you think?
- zzo38computer 6y agoYou could avoid escaping the slashes; it will be easier to use if you do that. Note that even then, backslashes and quotation marks will need escaped; for these reasons, ordinary documents probably should not use JSON like this (plain text or text/gemini is probably better). (I also don't really like mailing lists; if I am interested though, I may wish to subscribe to a NNTP.)
- sawirricardo 6y agoOh okay, I just now changed the code to avoid escaping the slashes. Though I got your point to not use JSON haha Oh that's a new vocabulary for me, the NNTP. Do you use it a lot? ( if I may know your answer)
- zzo38computer 6y agoI do use NNTP. I do not post a lot of messages (I do not have a lot to write, and I have some drafts that I have not finished writing yet), although I access it nearly every day. I also have my own NNTP server with my own newsgroups, in addition to accessing aioe for Usenet. Although you got rid of escaping the slashes, now the line breaks are missing.