Notices tagged with openweb

CSS Basic User Interface Module Level 3 (#CSS3UI) is now a@W3CRecommendation!
Congrats fellow co-editor@frivoaland thanks to the@CSSWGfor all the hard work (and patience) for so many years. #openweb@CSS3UI
https://www.w3.org/TR/2018/REC-css-ui-3-20180621/

Previously:https://twitter.com/css3ui/status/941695566194597889
andhttp://tantek.com/2015/189/b1/css-basic-user-interface-level-3

The 8th annual@IndieWebSummitis in 2 weeks!

Want to
* Own your identity on the web
* Reply to #Mastodontoots with your own website
* Grow the practical user-centric #decentralizedweb#dweb
* Build with@W3C+ #IndieWebstandards & experts

RSVP:https://2018.indieweb.org/

Learn, get inspired, brainstorm, design, create, make, and help grow the present & future of the independent #openweb!

my #SFAllHands⚡️intro
* 8 yrs #openweb#standards@Mozilla[1]
* may know me from #CSS[2] #microformats[3] #indieweb[4]
* recently Standards Outreach w@david_bryant
* editing CSS2.2, #CSSscrollbars
* interesting Vouch[5]
* controversial opinion: technical contributors@Mozillashould be actively using their own website, even if just one blog post a year

[1]https://wiki.mozilla.org/Standards
[2]https://wiki.mozilla.org/CSS
[3]microformats.org
[4]https://indieweb.org/
[5]https://indieweb.org/Vouch- vouching as a practical decentralized solution to commenting, with some trust without requiring a hard-identity, designed to reduce abuse etc. as we have seen in centralized social media, but distributed across the web peer-to-peer

Remote participating in the@W3CABmeeting in China meant staying up til ~26:30 (2:30am) the past two nights. On the bright side, I could still access Twitter & GitHub URLs as needed for discussions.

Now for a circadian reset. #openweb#2018_071#2018_072

“To PESOS or to POSSE?”https://dri.es/to-pesos-or-to-posse

Great post@Dries! #openweb#indieweb

Go for it. POSSEing to Twitter^1 and Facebook^2 works quite well.

Whether notes^3 / status updates (since 2010), or photos^4 (since 2015), it’s totally doable, and brings incredible peace of mind and a greater sense of ownership & control over your content.

You may also want to look into POSSEing replies^5, owning your comments as it were.

This comment for example, was originally posted ontantek.comas a single post, a multi-reply^6, automatically POSSEd to Twitter where it was auto-ellipsed & threaded^7 with your tweet, and only manually cross-posted on your original post.

Lots more on the IndieWeb wiki, and plenty of friendly folks ready and willing to share cross-platform/language development experience implementing all this stuff in the #indieweb-dev channel:
*https://chat.indieweb.org/dev

Drop by and say hi anytime!

Tantek

1^https://indieweb.org/Twitter#POSSE_to_Twitter
2^https://indieweb.org/POSSE_to_Facebook
3^https://indieweb.org/note
4^https://indieweb.org/photo
5^https://indieweb.org/reply
6^https://indieweb.org/multiple-reply
7^https://indieweb.org/Twitter#original_has_POSSE_tweet

.@beephttps://ethanmarcotte.com/wrote/seven-into-seven/
&@adactiohttps://adactio.com/journal/13035
I.e. #AMPis #openwashingnot #openweb, similar to #schemabefore it.

It has appearances or aspects of being open (e.g. with defensive statements like "non-google committers"), but in practice is proprietarily controlled/governed (free community labor for corporate leaders), and designed to bias an ecosystem in practice towards a single company or small anti-competitive oligopoly.

Previously, previously, previously:
*tantek.com/2017/261/t2/open-alternatives-googleamp
*tantek.com/2017/262/t1/amp-yourself-worse-than-html
*tantek.com/2017/262/t2/amp-worse-than-html-subset
*tantek.com/2017/263/t1/open-html-subset-interacts-quickly
*tantek.com/2015/280/t1/js-dr-amp-not-include-javascript
*tantek.com/2015/280/t2/make-amp-smaller-ban-jsonld-schema-org

More:https://indieweb.org/AMP

#IndieWebSummit is in ONE WEEK!
only 4 tickets left!
Want to grow the #OpenWeb?
Join us:https://2017.indieweb.org/