mastodon.gamedev.place is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server focused on game development and related topics.

Server stats:

5.1K
active users

#rest

5 posts5 participants0 posts today

I don't like it when someone decides that in order to do HTTP correctly, we need to adhere to arbitrary consistencies that don't actually make sense. A common one is that a successful DELETE should always return a 204 response. A 200 response with information about what was deleted is a perfectly compliant response. Another one is that a successful POST should have a 201 response. But a POST doesn't always create something, so often a 200 response is correct. Don't do this, folks.
#HTTP #REST

Tuesday is coming! \o/💃💐🎉

… when I take a break from what seems like *years* of political watchfulness, set some additional mastodon filters, & get back to enjoying the serendipity of social interaction here. Can't wait 🤗

Eventually I'll have to check in on what our politicians are doing. And some of it will find its way thru the filters. But my May priorities do NOT include activism. Just #rest, #artmaking, and work.🤞

That's hoping that #DougFordIsCorruptAF plays along 😖 #theBestLaidPlans

A lot of people with chronic illness are flaring right now due to the stress of the state of the world.

Living through end stage capitalism and escalating fascism takes a tremendous toll.

It’s important we all resist at our own pace. Don’t be afraid to rest. Unplug. Recharge.

disabledginger.com/p/spoon-sav

The Disabled Ginger · Spoon Saving Social Media Tips and How to Resist OnlineBy Broadwaybabyto

I'm developing a demo app to be called #Winsome to show how to use my #dweb #RESTful APIs for the decentralised #Autonomi network.

I struggle with raw HTML, CSS & JS and am much happier with Svelte but this is going to be an app in a single HTML file so it's taken a while but the hard part is done!

Thinking about next steps has clarified what else I need in the #REST API and how to provide a neat security model for p2p web apps!

I do love code!

I've been lax at updates to the dweb REST API which now supports most #Autonomi data types.

Web apps can POST/GET immutable data such as files and Archives (public and private), do multipart uploads of file(s), POST/PUT/GET Pointers (mutable references to other types) and POST/PUT/GET Scratchpads which are mutable storage for encrypted or public data.

To view #dweb #REST APIs:
- get rust
- cargo install dweb-cli
- dweb serve
In another terminal:
- dweb openapi-docs

#RESTful #API design advice wanted.

I'm blundering my way through my first #REST API implementation (for a #decentralized storage network.)

I have several APIs working but still unsure about how these should work to support different client styles and use cases.

For example, someone suggested custom headers for metadata which I wasn't aware was an option! How to code binary data in a JSON payload is another of many questions I have.

Can you point to design guides or best practice examples?

Using Jenkins deeply has reminded me that one of the pros of the original REST API intent was "You don't have to write your HTML handling logic twice." As in: if you use honest-to-God forms, and those forms access your app via your own REST API, you aren't writing one handler for form inputs and one for API calls (which had been the style at the time when REST hit the scene).

Nowadays, it's pretty much all JSON under the hood (i.e. barely anyone uses raw forms anymore; if you have a form on a page, it's bundling its fields into JSON and making an XmlHttpRequest), so this benefit is overlooked.