All due to unacceptable inhumane directives from POTUS and the bible-distorting AG. Backing down to detaining whole families is still just cover for racist internment.
More families being detained. More facilities being constructed. Because of an imagined (immigrant) threat.
The parallels to WWII Japanese internment are blatant, yet here we are.
It’s long past time to have the difficult conversations with friends and family that may have voted for POTUS, and the GOP that’s sacrificed all principles to support him. Keep the pressure up and see it through to making a difference in November.
For Houdini as a whole ("CSS Houdini family features" that have published drafts per this issue), I think the most accurate current summary position is "worth prototyping".
As individual Houdini specifications technically mature (with web developer feedback & iteration) and assuming we see broader use-cases across the web, we can consider stating upgraded positions for each individual specification as appropriate, taking into account the importance of other web platform features.
If anyone has concerns about particular Houdini drafts that should block an explicit "worth prototyping" position, please speak up and we can use "under consideration" while we file issues on those drafts and iterate accordingly.
In addition, since https://github.com/surma ’s tracker was mentioned, this overall Houdini position should not be taken to apply to anything that is not yet at least a published working draft.
If an explicit position is desired for proposals in https://ishoudinireadyyet.com without a working draft, please file separate issues for those.
Happy 13th to @microformats.org! With more use of #microformats2^1, especially among the growing #indieweb^2 network of websites, we’ve iterated key^3 specs^4 for real-world needs and are seeing more active community members. More updates & posts coming up!
6 days til the 8th @IndieWebSummit gathers innovators, artists, designers, and journalists to share, make, and grow the independent web, publishing & interacting with each other using their personal websites instead of social media silos.
Yesterday: finished my first #DoubleDipsea #race in 3:59:26! 📷 IG jasonthepatsfan Felt strong, especially on the downhill finish. When I saw the guy in front slow down with maybe 20 yards to go, I sprinted extra hard to beat him by mere feet: 620th of 691 finishers.
Most recently I saw the calendar-app event example in a previous comment, which could re-use https://microformats.org/wiki/h-event as well (similarly based on the IETF iCalendar standard). Happy to present an example using LZ syntax etc with h-calendar vocabulary if that would be helpful.
All of these vocabularies have been both implemented and successfully interoperably deployed peer-to-peer across numerous websites, publishing and parsing / consuming. (stats and examples available at indiemap.org)
Happy to help answer any questions about how these vocabularies are developed and how they’re community maintained, either here or chat.indieweb.org.
Remembering last Friday, running #hillsforbreakfast with #NPSF around a #waterfall on an #island in the middle of a lake in #GoldenGatePark, snapping wildlife, at sunrise. #takemeback #StrawberryHill #optoutside #getoutside #wakeupthesun #fromwhereirun #latergram #nofilter #2018_159
Having been to @XOXO several times I highly recommend it to #independent #creatives of all backgrounds, even knowing the more people apply for it, the less chance I personaly have to go again (see blog post for details).
my #SFAllHands ⚡️intro * 8 yrs #openweb #standards@Mozilla * may know me from: #CSS #microformats #indieweb * recently: Standards Outreach w @david_bryant * editing: CSS2.2, CSS scrollbars * interesting: Vouch * controversial opinion: technical contributors @Mozilla should be actively using their own website, even if just one blog post a year
↪ In reply to aaronparecki.com’s postI think IndieAuth makes a lot of sense as the way to implement a federated login protocol to provide a "simpler UX for OAuth2" login for Gitea as this issue is named.
It would also be possible to provide support for the "with GitHub" portion (as originally noted in the issue) without having to ask / wait for GitHub to implement IndieAuth, by adding https://indieweb.org/RelMeAuth support.
In addition, why shouldn’t it apply to any use of u-* with an img?
E.g. "u-featured" on an img should also pick up any alt attribute.
In short, I’d rather NOT go through multiple proposal/consensus/prototype/changes to get "alt" to work properly. I’d rather we figure out how "alt" should work and change the parsing spec once to handle it.
Note the issue name "image alt text is lost during parsing" is not specific to u-photo. Let’s fix this for any use of any image (img) tags in the parsing spec.
Overcast at #SFRC. Shorter run today (~11.1miles), still 2100+' of climbing.
The cool weather was perfect for running, and the cloud cover provided nice diffuse lighting for the trail flowers. Made it to Muir Beach and touched the Pacific. Slowly getting faster at hills. Less than six months to ECSCA 50k.
RSVP yes to: 2018.indieweb.orggoing to IndieWeb Summit 2018! June 26-27th at the Elliot Center in Portland, Oregon! This will be the #indieweb #openweb #dweb event of the year. RSVPs limited to 100 total, sign-up before tickets sell-out: https://2018.indieweb.org/
↪ In reply to issue 3704 of GitHub project “html”Registration (on the microformats wiki) works fine. I just tried it and created a new account. If you are having trouble understanding the microformats wiki, whether with registration or anything, please state the problem as a question and check the FAQ accordingly: http://microformats.org/wiki/faq
Recommend closure of issue #3704, works for me, no changes to HTML Standard needed.