[tantek]yes thanks for the GitHub issue prior discussion reference. looks like there was no determination that ASF received actual "permission" so we must presume appropriation (whether intentional or not, even without explicit mal-intent) until proven otherwise
@kixiQuupdate: since I complained about #webmentions yesterday after a fruitless evening of research, let me share the best two resources I found today: (twitter.com/_/status/1274527436537905152)
LoqiIt looks like we don't have a page for "webmention implementations" yet. Would you like to create it?_ (Or just say "webmention implementations is ____", a sentence describing the term)
LoqiAndroid is an open source operating system for mobile devices (AOSP) combined with a set of proprietary cloud services provided by Google, which some use to post to their IndieWeb sites https://indieweb.org/Android
jackylong term hope is to also do a wrapper library for iOS and Android in NativeScript so I can smoothly build apps without having to worry about partiy
LoqiIt looks like we don't have a page for "NativeScript" yet. Would you like to create it? (Or just say "NativeScript is ____", a sentence describing the term)
LoqiIt looks like we don't have a page for "React Native" yet. Would you like to create it? (Or just say "React Native is ____", a sentence describing the term)
jacky!tell swentel it begins! https://github.com/swentel/indigenous-android/issues/379 I'll begin working on this _slowly_ because I've finished sketching out what my idea for a mobile IndieWeb experience would look like but I'm also using this as a chance to contribute :)
ZegnatPutting this here because I did not want to contribute to more dev talk in #indieweb. Re: accessibility/semantic HTML elements instead of divs and the like.
ZegnatNot sure about the one-right-way. (Other than copying whatever WordPress has, because the more websites are exactly the same, the easier it is to browse the web ;)) But you can use something like https://github.com/matatk/landmarks to test navigating your own site through accessibility landmarks (those that are created by using elements other than div)
Loqiarchive in the context of the indieweb refers to date-grouped (often monthly) sets of posts (AKA personal historical archives, a common form of navigation), but can sometimes mean archival copy, a copy of a web page made (often by someone other than the author) at a particular point in time https://indieweb.org/archives
LoqiIt looks like we don't have a page for "archived posts" yet. Would you like to create it? (Or just say "archived posts is ____", a sentence describing the term)
[jgmac1106]my rules of accessibility, if your HTML is good and proper, you don't style with Headers (problem I see teachers doing the most in WYSIWYG editors you are fine
[jgmac1106]I do use new semantic organizing tags like article and section....but that is more for me...easier to see the legos when they are different colors rather than just all painted div
[jgmac1106]though for some reason I can't figure out how selectors cascade correctly and often fall back on divs...because article, footer, I mess up when trying to style
LoqiIt looks like we don't have a page for "deleted posts" yet. Would you like to create it? (Or just say "deleted posts is ____", a sentence describing the term)
LoqiIt looks like we don't have a page for "archived post" yet. Would you like to create it? (Or just say "archived post is ____", a sentence describing the term)
jackyI don't know yet if it merits a whole page only because I don't know who does it with their site (at least for me, it's done using the deleted flow)
[tantek]archived post is a feature on some [[social media]] silos that allows a user to make a post private only to themselves, removing it from their feed / stream / timeline or other listings of their posts.[[Instagram]] supports arching posts. No known IndieWeb Examples.
petermolnarre landmarks: the part that's still not clear to me is ok, the page (as in html document) should have semantic structuring, but should that cascade? Should (not could, should) <main> have <header>, <footer>, and another <main> or <article>? Etc.
[jgmac1106]how I handle it is I ask my students who use screen readers and also people in the IndieWeb community and ask what they like...Amanda and Marco always so helpful
petermolnar> and not use divs at all - that sounds way too similar to the anti-tables movement, which then ended up using divs for tables. Everything has it's place :)
ZegnatThere is no standard for how to markup your content because there is no standard for how to write content? Landmarks are assistive tools. If you want to know if you are using them right, see if you can navigate your site using them or not? I am not sure there is more of an answer than that *shrug*
petermolnar> because there is no standard for how to write content - the German inside me wants a manual :D (a while ago, when the internet had a lot if "what's your internal citizenship?" tests I always ended up with German somehow)
[Murray]Semantic HTML does have better fall-back support if CSS doesn't load as well. <ul> and <ol> are the obvious examples in terms of browser default rendering, but even stuff like <p> gain benefits. I guess HTML5 landmarks don't really have much of this (<header>, <footer> etc.) but they do make browsing a codebase _much_ easier IMO, so you get improved access for people using non-mouse/touch interfaces and better DX
[Murray]Actually, on that last point, I think people really underestimate how useful landmarks are for all the more modern, edge-case internet browsing that's going on. Things like accessing sites via smart devices, audio assistants, or even stuff like Safari's reader mode/tools like Verblr. Landmarks help them accurately navigate your site too
petermolnarfascinating: I have a virtual windows XP for some old games, and a godforsaken inner voice told me to check my site with IE8. So I did. And my front page loads surprisingly well, once a html5 shiv was added - but nothing else does. And there's no difference. It literally uses the exact same template.
nickodd, [jgmac1106], Rixon, [tantek] and [KevinMarks] joined the channel
[scottgruber]I was in a indieweb meetup and a participant asked for help debugging layout issues in a site using bootstrap. My thought to present about HTML energy and CSS would be a return to the future. Hand crafted websites. An issue I thought about that may make the topic out of scope for an indieweb camp is that it doesn’t include javascript or other programming helpful to integrate features like webmentions and micropub. On the other hand maybe
[scottgruber]someone could present about it for total beginners or junior dev. Kind of a back to the basic thematic structure, if that makes sense. Thoughts?
[scottgruber]i forgot to mention we all had some trouble figuring out how to solve the bootstrap layout challenge because it was pretty complex jangle for divs and classes.
[scottgruber]I’ve led some workshops to go over foundational skills about html and css, web servers and http protocols, git and ftp, though a hands on exercise to build a github pages site. (adding a javascript snippet for web mentions is nice add too)
[chrisaldrich][scottgruber] There's only so much you can begin to cover in a session, so you'll obviously have to leave some parts out, but the idea you've framed could certainly make a good one. Having a starting place for people is a great idea. You could always finish up with a list of "things for the future" with some links to additional resources or jumping off points.
[chrisaldrich][scottgruber] depending on who shows up for day two and their level of experience, something like what you're talking about might also make sense to do an actual "hands on session" to follow up the conversation/introduction on day one.
[Murray][scottgruber] by landmarks I mean HTML elements that are "purely" for semantics, like <header>, <footer>, <nav> etc. I guess ARIA roles are an extension of that, in that they allow custom elements or non-semantic elements to be classed as landmarks, but in most cases a native HTML element should be sufficient 😊