Post Aqe21h5spTaaDgCP8C by raphael@mastodon.communick.com
(DIR) More posts by raphael@mastodon.communick.com
(DIR) Post #AqdkgMoJLhNy0fDycq by silverpill@mitra.social
2025-01-31T11:48:35.776411Z
1 likes, 0 repeats
@licho @helge I think @context might be useful for documenting properties and types. But that's it. JSON-LD processing doesn't seem to solve any problem developers face in the real world, and I know several cases where developers started with JSON-LD-first approach and then regretted it :)
(DIR) Post #AqdleN6LOeAYHqGuCO by sun@shitposter.world
2025-01-31T11:59:41.676636Z
1 likes, 2 repeats
@silverpill I tried starting with json-ld-first and regretted it. i really gave it a serious try.it is TOO "flexible" for parsing if you assume you are going to take any valid json-ld. matching on expanded form is also awful.
(DIR) Post #Aqdls5T5kjQ7eXS4fI by lain@lain.com
2025-01-31T12:02:09.139348Z
1 likes, 2 repeats
@silverpill @licho @helge i have yet to find a single reason to actually engage with the LD part, it's completely useless. There's no situation I ever heard about where it would be useful (on the fediverse).
(DIR) Post #AqdnBm1Zqzwh5wX7Tc by fentiger@zotum.net
2025-01-31T12:13:57Z
0 likes, 1 repeats
This was my experience too.It also doesn't play very well in practice with JCS canonicalisation, as used by FEP-8b32 signatures: #^https://zotum.net/channel/fentiger?mid=d9557d63-a9e5-4bba-a39d-e2ee785def42Trying to treat messages as "JSON-LD first" has taken me a very long way down a blind alley, and cost me a lot of time.:(
(DIR) Post #AqdnXht5unFSdT1Y4O by i@declin.eu
2025-01-31T12:20:43.146785Z
0 likes, 0 repeats
@lain @licho @silverpill @helge it would still be nice if the network had an actual IDL to work from, there's no way to know what you'll get or what to send, without fuzzing out some subset between the different implementations like https://funfedi.dev/support_tables/generated/score/
(DIR) Post #Aqdz5rnKgbWyhfoudE by raphael@mastodon.communick.com
2025-01-31T13:48:25Z
0 likes, 0 repeats
@sun @silverpill What programming language are you using? Pretty much any RDF library can parse JSON-LD.
(DIR) Post #Aqdz5sZXnM5z7CNPmK by sun@shitposter.world
2025-01-31T14:30:16.414917Z
0 likes, 1 repeats
@raphael @silverpill Elixir, but I glossed over a lot of details about issues I was having. I actually found a big problem with the json-ld library in Elixir I was using but was able to code around it.A lot of the issues were honestly problems with activitypub and json-ld, like it doesn't matter if you use json-ld, you have to assume that your recipients do not so you have to write custom code to force your output to something that mastodon recognizes.I tried to find a database for storing json-ld (or rdf or turtle) and then lets you query on it and there are few options and they all suck.There is zero benefit to json-ld and lots of unnecessary cost. I tried really hard to make it work.
(DIR) Post #Aqe21h5spTaaDgCP8C by raphael@mastodon.communick.com
2025-01-31T13:15:32Z
0 likes, 0 repeats
@silverpill @licho @helge > JSON-LD processing doesn't seem to solve any problem developers face in the real worldTo me, it's the opposite. Without JSON-LD, my application needs to have a bunch of parsing/serializing code in order to talk with everyone else. With JSON-LD, we could just rely on any RDF library and get the data structures that we need right away.By avoiding JSON-LD, you end up dealing with *more* complexity, not less.
(DIR) Post #Aqe21iUjcZ3uZ2plVQ by silverpill@mitra.social
2025-01-31T15:02:45.922225Z
1 likes, 0 repeats
@raphael I don't have any issues with parsing data. Maybe JSON-LD makes it easier to parse different kinds of values (string vs object vs array), but in the grand scheme of things this is not a significant advantage, which is dwarfed by interop issues, poor performance and increased cognitive load. Moreover, the problem with value variability is the problem that was created by JSON-LD in the first place (and which can be fixed by standard JSON schemas).@licho @helge