russellballestrini/russell.ballestrini.net
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

modified: content/2025-03-21-introducing-slop.rst

Browse source
This commit is contained in:
Russell Ballestrini 2025-03-21 14:30:42 -04:00
parent cce13a9420
commit b3bf006d02
1 changed files with 10 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

16
content/2025-03-21-introducing-slop.rst
View file

@ -39,18 +39,21 @@ Ideally a SLOP server will be created in every programming language and placed i
As long as your code in your slop server knows how to dispatch the process and return a result it may be used in agentic flows!
Yes, this includes that narly ffmpeg bash script you still use sometimes.
- **/memory**: Store and retrieve key-value pairs. CRUD lifecycle (create-read-update-delete).
- **/memory**:
Store and retrieve key-value pairs. CRUD lifecycle (create-read-update-delete).
- **/models**: RFC in developemnt could be moved to /info/models (html) or /info/models.[html,xml,json,yaml,etc]
- **/models**: list of models & types upstream to the SLOP server.
RFC in developemnt could be moved to /info/models (html) or /info/models.[html,xml,json,yaml,etc]
right now I have a Python algorythm that dynamically determines a list of models the upstream SLOP server can provide in my implementation.
People have ask for us to also keep track of the type of model, for example embeddings or image or video or various hybrid enums.
Right now it's a simple list returned in JSON.
- **/resources**: Manage structured data or knowledge bases. Supports PUT to create new records (but currently no delete)
- **/resources**: Manage structured data or knowledge bases.
Supports PUT to create new records (but currently no delete)
We are currently RFC the ability to grab a list of resources by a prefix.
- **/info**: RFC in development
- **/info**: RFC in development
- **/pay**: Simulate transactions (for fun or future monetization).
@ -64,7 +67,7 @@ I’ve donated the first full Python implementation of SLOP to the community wri
I plan to create mimimal SLOP servers fro all the Python frameworks: Flask, Pyramid, FastAPI, etc.
You can fork the public domain code here: `https://git.unturf.com/engineering/unturf/slop.unturf.com <https://git.unturf.com/engineering/unturf/slop.unturf.com>`_. At the moment, we use a file-based memory store (`data/memory.json`, `data/resources.json`), and is deployed via `uWSGI` for production readiness.
You can fork the public domain code here: `https://git.unturf.com/engineering/unturf/slop.unturf.com <https://git.unturf.com/engineering/unturf/slop.unturf.com>`_. At the moment, we use a file-based memory store (``data/memory.json``, ``data/resources.json``), and is deployed via ``uWSGI`` for production readiness.
Here’s a quick example of chatting with it using curl:
@ -131,7 +134,8 @@ SLOP is about democratizing AI interaction. Whether you’re a developer, a tink
What's Next?
-------------------
Stateless HTTP for the win. ; )
Our biggest open source competitor is MCP, we aim to be more open & transparent & organic & grass roots from the bottom up not dropped from the ivory tower.
If this vibes with you start building SLOP integrations whenever you reach for an MCP integration so that we can grow both communities & learn from each other.
Stateless HTTP for the win. ; )