> Not being content with alienating only the general purpose #JSON#API enthusiasts, let me now proceed to also alienate my erstwhile #hypermedia enthusiast allies by saying:
> I don’t think #contentNegotiation is typically the right approach to returning both JSON and #HTML for most applications.
Ingenuity Mars Helicopter has sent data for its short flight (number 66). No images yet, but it completed the 0.50 meter flight in
23 seconds. Total flight duration is currently 1 hour, 58 minutes and 49 seconds. Data compiled from JPL's JSON URL's
Has anybody migrated from #Marshmallow to #msgspec for #JSON request/response serialization/deserialization and validation? Or at least given msgspec a try with #Flask?
@sos#Boost is the worst piece of library I have ever seen.
I once wanted to make a teeny tiny tool that interfaced with a remote #WebSocket#API. And since I'm familiar with it, I decided to write it in C++. When looking for a library that can do #WebSockets and #JSON everyone recommended Boost.
Yeah, I had to download 180 MB of source code(!) and spend several minutes building the damn thing just to integrate it into my single file program. It was so convoluted and complicated to use that I just gave up.
On top of that the only promising part of Boost that I was actually interested in, Boost.UI, was removed from it years ago. Thanks for nothing.
If I read between the lines on the software design for #ActivityPub, I don't think there are actually supposed to be servers per se, or more precisely that servers are supposed to be very simple passthroughs that have some forwarding/processing logic?
If so then this makes some sense, since when AP was being written was a big time for BaaS (Backend as a Service; https://en.wikipedia.org/wiki/Backend_as_a_service ) and that influenced a lot of ideas.
@hrefna
Having seen this movie several times before, IMHO, it's a case of adopting a spec because it can be interoperable and then having it spin out of control when adoption explodes.
I've seen it happen with #smtp#http#html#json#javascript
and because the solution started with a limited scope, it was hard to refactor without breaking things.
Semi-quarterly shoutout to #FloatRates which provides "free online JSON data feed(s) with latest foreign exchange rates which updates daily (once in 12 hours at 12 AM/PM)“.
Fast, reliable, free, and current enough for (my) personal pet projects. Recommended!
For the JSON-LD experts out there... does the Compaction algorithm ever produce a document with a null property value in the document body? I know that a null-valued property is treated as if it doesn't exist, but I can't identify the step in the Compaction algo where they are removed (given a null in the pre-compacted document). JSON-LD Playground removes the nulls, but I don't know if this is the normative behavior for all processors or not. #json-ld #activitypub
Back at the crumbling Nazi bar, author and trainer brian d foy still occasionally posts about #Perl. This morning, he quipped that he’d like #JSON and #YAML parsing in the @Perl core distribution this decade.
The original is probably safe, but I never feel comfortable pasting sensitive #JSON data to an online webpage, so I made this to be sure. Also very handy to have locally in the browser I think.
Data from the Mars Helicopter flight #62 during Sol 940 (October 12, 2023) Stretching the envelope continues with a new speed record of 10 meters per second (22.37 mph).
I just released a bugfix version of #fs2-data addressing a problem with object field selection in #JSON query and default values. Now it should work properly (including the documentation example, which I broke earlier).
FSON: file system object notation. A binary encoding more backwards compatible than you can possibly imagine.
A .fson file is a tar of a directory structure where folders are objects and folder contents are the attributes and functions.
Hundreds of tools have already been written to inspect and manipulate this format!
And they support compression, binaries, large files, indexing, and more!
Jeffson is a #FSON file that can be mapped 1⇄1 to #JSON (or, if your name is Jeff, your son).
Golang json encoding tip: a []uint8 or []byte slice will encode as a base64 string, but a fixed-length array of the same type will encode as a list of numbers.
Relevant line in package docs:
"Array and slice values encode as JSON arrays, except that []byte encodes as a base64-encoded string" https://pkg.go.dev/encoding/json#Marshal
Anyone hacking #golang code aware of any #JSON marshaller implementation that will let me have any say in what's "pretty"? The default one is waaay to spacious for anything but the most simple of objects. I can't believe I'm coming up with nothing searching for this. Kinda hoping it's just me being a boomer with no idea about how to use the internet? Please say it's so.