veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

134
active users

#rest

5 posts5 participants1 post today

📍 Rejoignez-nous pour échanger, découvrir et partager
• RPLL à Lyon – 15 mai 2025

échangez avec notre équipe et assistez à des démonstrations live
🔗 rpll.fr/#

• Assises CSIESR 2025 – du 19 au 22 mai
L’occasion idéale pour découvrir nos dernières intégrations.
🔗 assises.csiesr.eu/2025/

#rpll2025 #iam #rest #api #opensource #workflow #supann #cycledevie #orchestrator @plossra_a @cnll_frlow #supann #cycledevie #notifications #orchestrator @plossra_a @cnll_fr

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.

This is the longest I’ve ever gone without publishing an article, and the stress of not having anything ready is weighing heavy on my heart

It’s ironic considering how often I write about the importance of resting and listening to your body when it needs a break.

I’m so grateful for the Disabled Ginger community, but my body and brain clearly need a break.

I sit down to write everyday, and so far all I have is 30+ drafts with titles, a few images and (at best) two lines of actual content.

This is the harsh reality of chronic illness. It doesn’t matter how much you WANT to do something… if your body says “No”… Its a No.

You can’t try harder your way out of it. You can’t play through the pain.

The more you try to fight your body, the harder and longer the crash.

If you’re struggling to rest right now, take this as a sign to unplug. Relax. Recharge. Give your body what it’s crying out for and do it without the guilt.

We will all be here for you when you’re ready.

Sharing my article on radical rest from the archives, because I need the reminder & maybe so does someone else:

disabledginger.com/p/its-time-

The Disabled Ginger · It's Time to Throw Away the 'Coulda, Woulda, Shouldas' and Practice Radical RestBy Broadwaybabyto