ZegnatAnd that is probably because we talk in here (as kevinmarks said) and because we want to have discussions take place on the actual wiki pages themselves
WubTheCaptainI was previously in another medium-to-large sized web-related channel here on freenode and they didn't seem to grasp the concepts of advanced topics such as accessibility and JSON-LD
ZegnatJSON-LD often adds redundant data to your HTML. If you already have the data and are presenting it to your visitor, why copy it into hidden meta data? Instead we would recommend adding microformats to make the data you offer human visitors also computer accessible.
WubTheCaptainWell, for example, Google dropped the suggestion to use Microdata in favor of JSON-LD. You can use one-line <link> to a .jsonld file to convey the computer accessible message, and that does not require editing your HTML at all. It is data format agnostic.
WubTheCaptainIsn't Microdata itself the hidden metadata hidden into HTML? I can understand some standardized things like rel="license" which are in the WHATWG spec
Loqiconneg is short for HTTP Content Negotiation, a method by which a browser or other web client can request content of various types from a web server, and depending on what is requested, and what the server supports, it tries to provide the best it can https://indieweb.org/Content_Negotiation
WubTheCaptainZegnat: HTTP supports "Accept" and "Accept-Lang" headers (in example) to serve the right language or file format based on client's request.
ZegnatThat might be a problem in this channel. We use Loqi for a lot of things. Querying the wiki, adding content to the wiki, giving messages to people who are offline
WubTheCaptainYeah, you can do that. In fact I do that for WebP files already, but it would be tedious to do manually for every page. e.g. index.html.en, index.html.es
WubTheCaptainSide-note: I've also noticed that common advice is to use (recursive) "if" for WebP serving, when the file extension should be mapped wiith ngx_http_map_module
WubTheCaptainYeah, something like that. I haven't thought about it for a month though, so maybe I confused myself with requirements of TCN. And well, nginx doesn't handle the 406 Not Acceptable response anyway (Apache does)...
sknebelhm, seems like there is no way to parse the accept-lang header in nginx cleanly, so doing anything more complex than checking just the first sent language seems quite difficult
WubTheCaptainSorry for nitpicking, but for future reference SSL is insecure. While the term is a commonly interexchanged with TLS, I still cringe every time I hear someone talking about "SSL" or "SSL/TLS certificates".
WubTheCaptainWell regardless, the proper terms to use are TLS (when referring to the encryption layer in HTTPS) and X.509 certificates (when referring to the certificates used for authentication in HTTPS and elsewhere)
WubTheCaptainI've seen a shift from "SSL" to "SSL/TLS" mostly in the common, with professionals using "TLS". Not comparing any person here to the example.
LoqiHTTPS is an abbreviation for Hypertext Transfer Protocol Secure, a protocol for secure communication, supported by web servers (like Apache & nginx) and browsers https://indieweb.org/TLS
LoqiHTTPS is an abbreviation for Hypertext Transfer Protocol Secure, a protocol for secure communication, supported by web servers (like Apache & nginx) and browsers https://indieweb.org/ssl
sl007aaronpk: I see a problem in the spec. for MF2 parsing for urls : It does not really give a meaning to "rel". Let's say (for example) I have two Microformats, one h-card and one h-x-app and same URL is rel="me" in the h-card but rel="author" in the h-x-app - then the parser is lost. While we can compare the URL to the "rel" array we can't be sure which one is belonging to which mf.
KartikPrabhuin any case, rel values are for things that are scoped to the whole page. So in your example above the h-x-app should use p-author not rel-author if it is supposed to be scoped only to the h-x-app
sl007ok, aaronpk and KartikPrahbu: For h-x-app I would suggest the following properties then which I could not find : "p-author", "u-license", "u-content-repository" and "u-code-repository" …
Loqi[Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML/H...
Loqi[Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML/H...
KevinMarks1"The license keyword indicates that the referenced document provides the copyright license terms under which the main content of the current document is provided. This specification does not specify how to distinguish between the main content of a document and content that is not deemed to be part of that main content. The distinction should be made clear to the user."
KevinMarks1"For a and area elements, the author keyword indicates that the referenced document provides further information about the author of the nearest article element ancestor of the element defining the hyperlink, if there is one, or of the page as a whole, otherwise."
KevinMarks1"The bookmark keyword gives a permalink for the nearest ancestor article element of the linking element in question, or of the section the linking element is most closely associated with, if there are no ancestor article elements."