CIRCLE WITH A DOT

@cwebber My XKCD-style password is so strong you can’t crack it: “undefined reference begin document”

Password Strength

xkcd (xkcd.com)

@cwebber I was quite curious LLMs, but I recently had a disappointing experience. I had a common latex problem, but with a more unusual technology stack. It went to “Do this — I get an error — OK do that —…” for a few rounds, nothing surprising. At some point I crossed a line, and it went “OK there’s no way to do what you want with this tech”. As usual, 30 seconds of grepping around in the source code gave me the solution.
Anyway, I wouldn’t trust it for summarize and explore.

@csarven Now things get blurred: if I parse both RDFa and Microformats2, and if I accept both webmentions and AP inbox, I might one day be able to speak both indieweb and fediverse.

HTML document to ActivityPub object using RDFa · Issue #40 · swicg/activitypub-html-discovery

The draft describes object discovery via embedded JSON-LD, but I think RDFa may also come in handy especially if you only need to embed part of of the object (which I guess is a common use case since consumers usually want to verify the ...

GitHub (github.com)

@trwnh as a paranoid person, I sometimes wonder what would happen if schema.org received a court order to partially censor its schema in certain regions of the world. Or inject a backdoor key. If it prevents people from sending memes across the geofence, it’s bad.

@evan @trwnh @cwebber @kopper @hongminhee I think it would be great to have everything expanded besides the required as2 context.
The results of the compaction algorithm would change if new things migrate into schema.org, so technically a document could become invalid or break without being modified, but this would be a lot better otherwise I guess.

@evan @cwebber @kopper @hongminhee Couldn’t we agree to standardize on expanded json-ld? We would not need any json-ld processor, we would not need to fetch or cache any context. There would be no way to shadow properties.

Right now I like the #indieweb #webmentions / #microformats more than #activitypub / #jsonld, because the author chooses which replies appear below their post. I think it would be better if there was an expectation to regularly validate the webmentions (we have HTTP caching for that), and also for #xhtml instead of html. I’m not familiar with the LD markup languages, but maybe there exists something more interoperable than microformats (with proper URIs for properties).