sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Server stats:

599
active users

#rest

3 posts3 participants0 posts today

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.
Typically HTTP APIs speak JSON or XML, but what are some other human-readable formats folks have seen that was useful? How about text/plain and sending INI, TOML, RESP etc. for some simpler and smaller request/responses that are still self-describing? These seems nicer for languages that don't have good JSON/XML support or if they do their libraries are cumbersome and awkward to use.

#HTTP #API #REST #ContentType

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...
Continued thread

this paper cites one of my favorite publications. a first-authored paper which presented some of my work in Stanford's Radiology department.

to our knowledge, i built the world's 1st clinically-suited search engine for biomedical images (think: DICOM server) that could be searched using structured metadata provided by the radiologists reading the CT or MRI images, using open-source standards. #Ruby #RoR #REST #HTML5

link.springer.com/article/10.1

SpringerLinkManaging Biomedical Image Metadata for Search and Retrieval of Similar Images - Journal of Imaging Informatics in MedicineRadiology images are generally disconnected from the metadata describing their contents, such as imaging observations (“semantic” metadata), which are usually described in text reports that are not directly linked to the images. We developed a system, the Biomedical Image Metadata Manager (BIMM) to (1) address the problem of managing biomedical image metadata and (2) facilitate the retrieval of similar images using semantic feature metadata. Our approach allows radiologists, researchers, and students to take advantage of the vast and growing repositories of medical image data by explicitly linking images to their associated metadata in a relational database that is globally accessible through a Web application. BIMM receives input in the form of standard-based metadata files using Web service and parses and stores the metadata in a relational database allowing efficient data query and maintenance capabilities. Upon querying BIMM for images, 2D regions of interest (ROIs) stored as metadata are automatically rendered onto preview images included in search results. The system’s “match observations” function retrieves images with similar ROIs based on specific semantic features describing imaging observation characteristics (IOCs). We demonstrate that the system, using IOCs alone, can accurately retrieve images with diagnoses matching the query images, and we evaluate its performance on a set of annotated liver lesion images. BIMM has several potential applications, e.g., computer-aided detection and diagnosis, content-based image retrieval, automating medical analysis protocols, and gathering population statistics like disease prevalences. The system provides a framework for decision support systems, potentially improving their diagnostic accuracy and selection of appropriate therapies.

Introducing: BinkyLabs.OpenApi.Overlay a new library to parse and apply OpenAPI overlays in #dotnet !!! 🎉🎉🎉🎉

github.com/BinkyLabs/openapi-o

Over the last week, a good friend of mine Matthieu COSTABELLO and I have been hacking away to produce this new library. It's modeled after Microsoft.OpenAPI, parses, serializes and applies overlays to documents.

With overlays, you can maintain patches to #OpenAPI description, extremely useful when your team doesn't "own" the document but needs to maintain only a few changes. Using this library, a host of OpenAPI tools built in #dotnet will be able to support this specification and new feature!

Stay tuned for more projects from BinkyLabs!

Finished a small educational project: zserge.com/posts/pennybase - a toy clone of Firebase/Supabase/Pocketbase. In 700 lines of Go with zero dependencies it has dynamic record schemas, reasonably fast "document store" using CSV files, orthogonal REST APIs + realtime watch over SSE, authNZ with simple RBAC, pluggable hooks.
Enough to build a real-time chat app or a management system. Works well with HTMX and Go templates.
Not for serious use, of course! #golang #backend #baas #firebase #rest #csv

zserge.comPennybase: a Pound-Shop BaaSBuilding yet another single-file backend as a service. As always, we focus on simplicity, but nevertheless we try to implement as many features as we can without making it too complex.

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.