shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

269
active users

#rest

3 posts2 participants0 posts today

Hey #GetFediHired,
After some layoffs in my current company, I am looking for some #softwaredevelopment job, #remote only. I can work in the #EU or would be able to travel some weeks during the year.

I am fluent in #PHP, #Symfony, #Golang, #gRPC, #REST and #GraphQL #API, #Docker, #Ansible, Event Streaming and modern software development in general with experience of over 15 years in various roles - from senior engineer to CTO. I value good software architecture, tests, documentation in combination with valuable communication and discussions.

Find my CV here: codedge.de/cv

If that sounds like something, drop me a message or reply. Cheers!

code and society | codedgeCV
More from tH

Setting up a sector-wide #PeerTube pilot instance on behalf of Dutch higher ed & research using #SSO via #SAML, so no local usernames/passwords…

Anyone with experience uploading videos using the #REST #API for system integration purposes? No classic #OAuth flow here… or is it possible?!

💚➡️ #Framasoft #Fediverse #OpenSource #Education #Science #askfedi

👩🏽‍🎓 video.edu.nl/

video.edu.nlvideo.edu.nlVideo.edu.nl, is een PeerTube pilot videoplatform van SURF.

Been feeling sad for the past 3 days. Don't know why. There is no changing my mood, and this sucks. Nothing particular going on.

I have too low energy to do anything in this heat. Very uninspiring. Not interested in going out, running, or anything else for that matter.

I think I'm just going to lounge today.

I got back to #WebIDAMd, a #systemd-userdbd-based system for using #OAuth / #OIDC / #REST identity providers for #Linux system authentication.

And I can now show off a first demo (no #PAM authentication yet, but user and group listing):

asciinema.org/a/728567

In contrast to #sssd's recent OIDC module, WebIDAMd is fully provider-agnostic and integrates transparently with userdbd, the current/upcoming standard in most Linux distributions instead of requiring a full separate software stack.

asciinema.orgWebIDAMd – First working userdb demoThis is the first working demo of [WebIDAMd](https://codeberg.org/Bergblau/webidamd) It demonstrats how WebIDAMd can be used to provide Linux system user accounts and groups from a backend that spe...

This is great. I love seeing that a journalism team—a great one at that—is taking a week off. (As an animal rights activist, I’d prefer they don’t go fishing, but we’ll save that tangent for another time.)

Good on you for bucking the capitalist system, @404mediaco. Enjoy your week off!

404media.co/introducing-404-me

404 Media · Gone Fishin': 404 Media Summer Break 2025404 Media is closed this week. School's out.

Looking to build a #REST #API on top of #nextJS and #prisma. I am not dead set on HAL, JSON-LD or JSON:API but would like to not have to do much work to support either.

I just came across zenstack.dev/ and this seems like a well supported and appears to automate a lot of the effort. Good choice, other options I should look into ..?

zenstack.devZenStack - Simplified Full-Stack Development with Prisma ORM | ZenStackA TypeScript toolkit that enhances Prisma ORM with flexible Authorization and auto-generated, type-safe APIs/hooks, simplifying full-stack development.
Continued thread

CouchDB also seems to be a technically simple solution—although it seems more difficult to use. And it's built with erlang!

1. Automatically generating OpenAPI documentation for your web resources doesn't seem doable, but there's perhaps CouchDB's own form of API documentation.
2. HTTP OPTIONS requests are accepted although poorly documented from what I could find.

It'd be nice if CouchDB supported learning about it's API through OpenAPI documentation.

#CouchDB#HTTP#REST

Suppose you want to publish some web resources or, in other words, make your data available on the web. Additionally, suppose you want interaction with your resources discoverable, documented, and at-least somewhat doable by machine.

Then you'd likely turn to creating an HTTP-based, RESTful API that supports all the standard CRUD operations. Firstly, you'd ensure the API is well documented using, the OpenAPI standard; secondly, you'd point to that documentation in the HTTP OPTIONS.