Neocities – Developers API
neocities.org
neocities.org
(And, of course, as it generally goes without saying when someone labels something a "REST API", this is not REST, but that's a different topic.)
I feel like almost every API could have this footnote.
But this is pedantry. REST has become a generic term for "shoving JSON around," for better or worse.
What's REST? What makes most APIs not REST?
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
real world systems might have to change actual ids. like the article. or say you grow to some other use case not covered before because of new regulation etc... 301 is the only rest way.
From my experience using nginx for amateur reasons, this seems like the wrong way to go about this. Not to mention the distaste I have for caching redirects, like 301. (they make fixing your config annoying, since browsers will redirect (and switch the verb to GET) before even hitting the server)
Just google around, read some w3schools, type it into a textarea at neocities and woa, your own site.
Obviously this is only interesting for relatively nerdy types, but i don’t at all understand all the “why don’t people just <twenty cumbersome steps and tools>” comments that are here currently.
I know no place that makes having your own, self-built website, easier. And it’s free!
Also, in my case, a matter of branding. While I'm not trying to promote my content (a bunch of short stories and illustrations) so heavily, it just felt wrong for them to reside in Github/Gitlab subdomain. The closest I would've considered Git* pages is if I was doing sci-fi stories and that is still a "maybe". At the time I started my project, I was also worried I might run afoul of some content policy these Git platforms might have given that my website is not exactly for their demographic.
Once you know how git/hub works, it seems much easier to me to use github, but I understand that not all people do; while all the other sites (squarespace, wix etc) are too much of "website builders". Fine thanks
https://docs.github.com/en/authentication/securing-your-acco...
I’ve spun up so many one offs
I make a lot of lil one offs, and I want a static page, and neocities (from main account) simply has an input box for a new site name, so I "spin up" w/o registration
neocities is cute, the spirit of it. I have no idea if they're still accepting $100 of btc, it was just appealing when I noticed once upon a time
And in another generation, it'll be something else.
And with Neocities, you also don’t need to understand what it means for files to be “local” or “on a server” because you just get a textarea that you can type your HTML into. (until you get to stuff like using your own images that is)
To do “basic git usage” you need to pretty deeply grok all of that before you can even begin to learn git itself. Just to publish a website!
The difference: You can fuck up an HTML tree and most browsers can still display your page[1], you can still get your message across. You fuck up a git history tree and you can somehow summon Cthulhu.
Not to mention, even if you can manage to stay away from branch confusion, just dealing with diffs is already a huge barrier for newbies.
[1] See "Where HTML 'beats' C" - Computerphile https://www.youtube.com/watch?v=-csXdj4WVwA
To me, just being able to save versions and look at them later (like saves in a video game) is such a huge boon that any of the more complicated features don't even need to be touched for git to be worth it.
The following are also cool projects, but not included in my "cheap" web list due to too much javascript:
[3] https://mmm.page
Neocities (sans neocities.org-subdomains):
https://search.marginalia.nu/search?query=as%3Aneocities+-si...
c.f. Squarespace:
https://search.marginalia.nu/search?query=as%3Asquarespace&p...
(disclosure: I built this search engine)
They give you a free subdomain with HTTPS (Let's Encrypt). If you want, you can bring your own domain too.
There was once a HTTP standard called WebDav IIRC but it seems rarely implemented. Why haven't these sites tried that direction if they wanted HTTP-Backed security measures?
Upload/Delete as REST is usable though.
WebDAV is still a valid thing, and used quite more often than most people know. Its not known because it lives deeply embedded within apps and systems, and not something that is often visible to users. Case in point, a little thing called Google Drive makes use of WebDAV, so does NextCloud, etc.
WebDAV's not dead yet! (With apologies to Monty Python. ;-)