This has been a long dream of mine, since I added JSON support in #fs2-data. And it has never been so close to become true: the PR adding support for #JSON queries (think #jq) is ready! It allows for declarative streaming extraction and transformation of JSON data, emitting data as soon as some piece of output has been built, discarding input that has been consumed, on the go. I must admit, that I am super proud of this one! https://github.com/gnieh/fs2-data/pull/426
I'm not the best at #introduction (s) but here goes nothin :002blush:
hoi, I'm mana, also known as momo. I'm an FC leader in #ffxiv and I play on Primal DC. I'm shy, but one of those people who won't shut up once you get to know me. I have a tendency to be introspective/keep to myself when I'm really depressed. I have #cptsd and am #neurodivergent. Also, I'm disabled from #rheumatoidarthritis and #ehlersdanlossyndrome and #fibromyalgia. Most days are good days, but the bad ones are pretty bad :blobcat_notlikethiscry:
I like modding/coding games so I've been learning #blender and #json to facilitate that. idk what else to say butt hi everyone, thanks for reading this if you did! let's be friends?:sbahri_question:
If you're implementing DNS-over-HTTP JSON client and wondering what Accept header media type to use… 👀
There's RFC8427, "Representing DNS Messages in JSON"; it defines the JSON structure. You can ignore it. No DoH JSON API provider I tested implements it.
It also defines the application/dns+json media type, registered with IANA. You can ignore it as well. Only CloudFlare cares about the media type — and insists on application/dns-json (yes, with a "-"). 🙄
That's the Json, I'd like 'Orgre' and 'Purple' to display as entities with the number being the data. Nothing I try seems to work. Is there a simple addon I can use from #HACS?
In which I think out loud for a bit about #JsonLD, it's place, and what compromises need to be made:
First, the vision of JSON-LD is essentially this (and yes I will use entirely #ArmoredCore6 references, this is me talking to myself after all :p ):
A request comes in to Handler Walter (HW) for a mission for C4-621 (Raven) to assault a dam and blow up some generators along with G4 and G5, troops under G1 Michigan, part of a squad called the "Red Guns"
Using a library that "does #JsonLD" and later discovering that some of these modern specs only sort of comply with the JSON-LD spec, or use subsets already, so you end up with a heavyweight library that's slow, memory inefficient, and difficult to use.
If such a library even exists on your platform.
3. Adding a set of directives that are sort of JSON-LDish on top of a JSON library.
Do you have a preferred #knowledgebase (if that's the right term) type app on Windows 10? I'm currently toying with #ObsidianMD but I'm wondering if there's something better.
My planned use case is keeping track of a few #collections (digital and physical) along with their purchase information etc.
Local storage in something readily exchanged, like #Markdown, #JSON or #YAML is a must, preferably without needing a separate manual import/export step.
Thibaut Arnoud will give you to an overview of validation in API Platform. In his talk, we will see how it's possible to validate requests before deserialization, thanks to #JSON Schema.
#XML is a great configuration language. Yes, I'm not joking. It has a terrible syntax, and it hasn't been in vogue for many years, but semantically it's better suited than #JSON and #YAML for many tasks.
With YAML/JSON you have to choose between arrays (nesting) and maps (keys). XML gives you both nesting and keys for every single element in the config. It's a much cleaner abstraction since it's all nodes all the way down. But it's rather ugly!
I have a #Java app that loads user created #JSON. I also have a JSON file that describes the content of this format, which I’m using to to validate the content of the user created JSON. This lets me determine if the user forgot to include some properties or if they’re of the wrong type or out of range. I can then display some errors accordingly.
Is there a library that would do this for me? I guess it’s the equivalent of #XML and XSDs.
🤔 Occasionally, I land on JSON Patch as the best way to solve a problem that has been bugging me for a while. Tonight, this plagued me again, and I'm really tempted. https://jsonpatch.com/
It just really continues to feel like #w3c is trying push #JsonLD into everything and the kitchen sink… regardless of if it fits and doing a "beat to fit paint to match" when it doesn't, the JSON-LD working groups and such are busy trying to figure out how to do a #YamlLD, and the rest of us are trying to figure out how to do this practically in production in a way that doesn't ignore all of JSON-LD, or just doing "JSON + a weird context obj."
This also ties into the inherent disadvantage of the #fediverse compared to centralized services: processing and cost.
If I have n servers the absolute minimum number of messages that will need to be exchanged is Θ(n), all of that is in a #Json format that must be fully parsed and that is slow to parse even compared to other JSON formats. They each then need to store it individually.
A centralized social service doesn't need to do that and that is a big cost savings.