: A couple of days ago in an informal discussion in the #indieweb chat channel about how different people view #Mastodon, the #fediverse, or #Bluesky, and services like #Bridgy & #BridgyFed quite differently, I noted¹ that one big unspoken difference was how things on the web last over time, from the traditional persistent web, vs the newer and growing ephemeral web.There is the publicly viewable #OpenWeb that many of us take for granted, meaning the web that is persistent, that lasts over time, and thanks to being #curlable, that the Internet Archive archives, and that a plurality of search engines see and index (robots.txt allowing). The HTML + CSS + media files declarative web.Then there are the https APIs that return JSON "web", the thing that I’ve started calling the ephemeral web, the set of things that are here today, briefly, gone tomorrow. I’ve previously used the more provocative phrase js;dr (JavaScript required, Didn’t Read) for this #ephemeralWeb, yet like many things, it turns out there is a spectrum from ephemeral to persistent.One popular example on that spectrum that’s closer to the ephemeral edge is anything on a Mastodon server running v4 (or later as of this writing) of the software. (I’m not bothering to discuss the examples of walled garden social media silos because I expect we will continue to see their demise² over time.)For example, the Internet Archive version of the shutdown notice for the queer(.)af Mastodon server, is visibly blank:https://web.archive.org/web/20240112165635/https://queer.af/@postmaster/111733741786950083Note: only a single Internet Archive snapshot was made of that post.However if you View Source, you can find the entirety of that #queerAF post duplicated across a couple of invisible-to-the-user meta tags inside the raw HTML: "**TL;DR: Queer[.]AF will close on 2024-04-12** …" [.] added to avoid linking to a dead domain.Note: such meta tags in js;dr pages were part of the motivation to specify metaformats.To be clear, the shutdown of queer(.)af was a tragedy and not the fault of the creators, administrators etc., but rather one of the unfortunate outcomes of using some ccTLDs, country-code top level domains, that risk sudden draconian rules, domain renewal price hikes, or other unpredictable risks due to the politics, turmoil, regime changes etc. of the countries that administrate such domains.Nearly the entirety of every Mastodon server, every post, every reply, is ephemeral.When a Mastodon server shuts down, all its posts disappear from the surface of the web, forever.Perhaps internet archeologists of the future will discover such dead permalinks, check the Internet Archive, find apparent desolation, and a few of them will be curious enough to use View Source tools to unearth parts of those posts, unintentionally preserved inside ceremonial meta tags next to dead scripts disconnected from databases and an empty shell of a body. All reply-contexts of and replies to such posts and conversations lost, like threads unraveled from an ancient tapestry, scattered to the winds.If you’re reading this post in your Mastodon reader, on either the website of your Mastodon account, or in a proprietary native client application, you should be able to click through, perhaps on the date-time stamp displayed to you, to view the original post on my website, where it is served in relatively simple declarative HTML + CSS with a bit of progressive enhancement script.Because I serve declarative content, my posts are both findable across a variety of services & search engines, and archived by the Internet Archive. Even if my site goes down, snapshots or archives will be viewable elsewhere, with nearly the same fidelity of viewing them directly on my site.This design for longevity is both deliberate, and the default for which the web was designed. It’s also one of the explicit principles in the IndieWeb community.If that resonates with you, if creating, writing, & building things that last matter to you, choose web tools, services, and software that support the persistence & longevity of your work.#persistentWeb #longWeb #LongNowThis is post 10 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available→ 🔮Post glossary:API (Application Programming Interface) https://indieweb.org/APIBluesky https://indieweb.org/BlueskyBridgy https://brid.gy/Bridgy Fed https://fed.brid.gy/ccTLD (country-code top level domain) https://indieweb.org/ccTLDcurlable https://indieweb.org/curlabledeclarative web https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativewebInternet Archive https://archive.org/js;dr (JavaScript required; Didn’t Read) https://tantek.com/2015/069/t1/js-dr-javascript-required-deadJSON https://indieweb.org/JSONlongevity https://indieweb.org/longevityMastodon https://indieweb.org/Mastodonmetaformats https://microformats.org/wiki/metaformatspermalink https://indieweb.org/permalinkprinciples in the IndieWeb community https://indieweb.org/principlesprogressive enhancement https://indieweb.org/progressive_enhancementreply https://indieweb.org/replyreply-context https://indieweb.org/reply-contextrobots.txt https://indieweb.org/robots_txtsocial media https://indieweb.org/social_mediasilo https://indieweb.org/siloView Source https://firefox-source-docs.mozilla.org/devtools-user/view_source/index.html¹ https://chat.indieweb.org/2024-02-13#t1707845454695700² https://indieweb.org/site-deaths
's status on Thursday, 15-Feb-2024 16:18:00 EST
A couple of days ago in an informal discussion in the #indieweb chat channel about how different people view #Mastodon, the #fediverse, or #Bluesky, and services like #Bridgy & #BridgyFed quite differently, I noted¹ that one big unspoken difference was how things on the web last over time, from the traditional persistent web, vs the newer and growing ephemeral web. There is the publicly viewable #OpenWeb that many of us take for granted, meaning the web that is persistent, that lasts over time, and thanks to being #curlable, that the Internet Archive archives, and that a plurality of search engines see and index (robots.txt allowing). The HTML + CSS + media files declarative web. Then there are the https APIs that return JSON "web", the thing that I’ve started calling the ephemeral web, the set of things that are here today, briefly, gone tomorrow. I’ve previously used the more provocative phrase js;dr (JavaScript required, Didn’t Read) for this #ephemeralWeb, yet like many things, it turns out there is a spectrum from ephemeral to persistent. One popular example on that spectrum that’s closer to the ephemeral edge is anything on a Mastodon server running v4 (or later as of this writing) of the software. (I’m not bothering to discuss the examples of walled garden social media silos because I expect we will continue to see their demise² over time.) For example, the Internet Archive version of the shutdown notice for the queer(.)af Mastodon server, is visibly blank: https://web.archive.org/web/20240112165635/https://queer.af/@postmaster/111733741786950083 Note: only a single Internet Archive snapshot was made of that post. However if you View Source, you can find the entirety of that #queerAF post duplicated across a couple of invisible-to-the-user meta tags inside the raw HTML: "**TL;DR: Queer[.]AF will close on 2024-04-12** …" [.] added to avoid linking to a dead domain. Note: such meta tags in js;dr pages were part of the motivation to specify metaformats. To be clear, the shutdown of queer(.)af was a tragedy and not the fault of the creators, administrators etc., but rather one of the unfortunate outcomes of using some ccTLDs, country-code top level domains, that risk sudden draconian rules, domain renewal price hikes, or other unpredictable risks due to the politics, turmoil, regime changes etc. of the countries that administrate such domains. Nearly the entirety of every Mastodon server, every post, every reply, is ephemeral. When a Mastodon server shuts down, all its posts disappear from the surface of the web, forever. Perhaps internet archeologists of the future will discover such dead permalinks, check the Internet Archive, find apparent desolation, and a few of them will be curious enough to use View Source tools to unearth parts of those posts, unintentionally preserved inside ceremonial meta tags next to dead scripts disconnected from databases and an empty shell of a body. All reply-contexts of and replies to such posts and conversations lost, like threads unraveled from an ancient tapestry, scattered to the winds. If you’re reading this post in your Mastodon reader, on either the website of your Mastodon account, or in a proprietary native client application, you should be able to click through, perhaps on the date-time stamp displayed to you, to view the original post on my website, where it is served in relatively simple declarative HTML + CSS with a bit of progressive enhancement script. Because I serve declarative content, my posts are both findable across a variety of services & search engines, and archived by the Internet Archive. Even if my site goes down, snapshots or archives will be viewable elsewhere, with nearly the same fidelity of viewing them directly on my site. This design for longevity is both deliberate, and the default for which the web was designed. It’s also one of the explicit principles in the IndieWeb community. If that resonates with you, if creating, writing, & building things that last matter to you, choose web tools, services, and software that support the persistence & longevity of your work. #persistentWeb #longWeb #LongNow This is post 10 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available → 🔮 Post glossary: API (Application Programming Interface) https://indieweb.org/API Bluesky https://indieweb.org/Bluesky Bridgy https://brid.gy/ Bridgy Fed https://fed.brid.gy/ ccTLD (country-code top level domain) https://indieweb.org/ccTLD curlable https://indieweb.org/curlable declarative web https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativeweb Internet Archive https://archive.org/ js;dr (JavaScript required; Didn’t Read) https://tantek.com/2015/069/t1/js-dr-javascript-required-dead JSON https://indieweb.org/JSON longevity https://indieweb.org/longevity Mastodon https://indieweb.org/Mastodon metaformats https://microformats.org/wiki/metaformats permalink https://indieweb.org/permalink principles in the IndieWeb community https://indieweb.org/principles progressive enhancement https://indieweb.org/progressive_enhancement reply https://indieweb.org/reply reply-context https://indieweb.org/reply-context robots.txt https://indieweb.org/robots_txt social media https://indieweb.org/social_media silo https://indieweb.org/silo View Source https://firefox-source-docs.mozilla.org/devtools-user/view_source/index.html ¹ https://chat.indieweb.org/2024-02-13#t1707845454695700 ² https://indieweb.org/site-deaths
: at a fascinating #Threads meetup hosted by Meta in San Francisco, with a handful of great #dataportability #fediverse #indieweb #openweb folks, learning about and providing feedback to Threads folks about their #federation #ActivityPub and other #openStandards support plans.Chatham House rule¹ means we can quote and talk about what’s being discussed (I’m taking notes), however no attribution, which I’m extending to not saying (or @-@-mentioning) who else is here.If you’re also here, feel free to reply to this post or use one of the below hashtags. And since I’m publishing this, feel free to @-me as well.#DataDialogue #Threadiverse (unofficial hashtag suggestion from a participant)¹ https://en.wikipedia.org/wiki/Chatham_House_rule
's status on Thursday, 07-Dec-2023 20:09:00 EST
at a fascinating #Threads meetup hosted by Meta in San Francisco, with a handful of great #dataportability #fediverse #indieweb #openweb folks, learning about and providing feedback to Threads folks about their #federation #ActivityPub and other #openStandards support plans. Chatham House rule¹ means we can quote and talk about what’s being discussed (I’m taking notes), however no attribution, which I’m extending to not saying (or @-@-mentioning) who else is here. If you’re also here, feel free to reply to this post or use one of the below hashtags. And since I’m publishing this, feel free to @-me as well. #DataDialogue #Threadiverse (unofficial hashtag suggestion from a participant) ¹ https://en.wikipedia.org/wiki/Chatham_House_rule
: I was traveling when I heard the news about Molly Holzschlag (@mholzschlag).https://www.tucsonsentinel.com/local/report/090523_molly_holzschlag/tucsons-molly-holzschlag-known-as-the-fairy-godmother-web-dead-60/Her #CSS #accessibility #OpenWeb contributions are well documented. May she be at peace. Appreciated @Zeldman.com’s (@Zeldman) note: https://twitter.com/zeldman/status/1699395939792822335
's status on Sunday, 10-Sep-2023 15:08:00 EDT
I was traveling when I heard the news about Molly Holzschlag (@mholzschlag). https://www.tucsonsentinel.com/local/report/090523_molly_holzschlag/tucsons-molly-holzschlag-known-as-the-fairy-godmother-web-dead-60/ Her #CSS #accessibility #OpenWeb contributions are well documented. May she be at peace. Appreciated @Zeldman.com’s (@Zeldman) note: https://twitter.com/zeldman/status/1699395939792822335
: 10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹.2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first² "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !"When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴.Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmentionUnfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first.This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated→ 🔮Glossaryfederation https://indieweb.org/federationh-entry https://microformats.org/wiki/h-entryPingback https://indieweb.org/Pingbackreply post https://indieweb.org/replyReferences¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html² https://tantek.com/2023/014/t4/domain-first-federated-atmention³ https://aaronparecki.com/2013/04/19/3/indieweb⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread⁵ https://aaronparecki.com/2013/05/21/4/xkcd
's status on Wednesday, 19-Apr-2023 20:48:00 EDT
10 years ago today the first #federated #IndieWeb comment thread was published and collected peer-to-peer IndieWeb replies across websites without any intermediary, silo or otherwise¹. 2013-04-19 @eschnou.com posted a brief note on his personal site with #atMentions of a few domains (putting an '@' sign immediately before a domain name to indicate an explicit cross-web @-mention), which itself was also a first² "Testing #indieweb federation with @waterpigs.co.uk, @aaronparecki.com and @indiewebcamp.com !" When @aaronpk.com was notified and replied from his site within minutes³, it became the first peer-to-peer federated IndieWeb comment thread, at the time using h-entry and Pingback. I blogged about it a few days later⁴. Earlier this year I blogged more observations of all the user interactions that happened on that day and shortly thereafter to make this all work: https://tantek.com/2023/014/t4/domain-first-federated-atmention Unfortunately Laurent Eschnou’s original post is no longer up, and we only have the Internet Archive copy. However most of the IndieWeb reply posts are still up including Barnaby’s: https://waterpigs.co.uk/notes/1334/ The oldest still working federated post and comment thread was second overall, unsurprisingly from @aaronparecki.com⁵, a whole 40 days after Laurent’s first. This is day 37 of #100DaysOfIndieWeb. #100Days #OpenWeb #federation #fediverse ← Day 36: https://tantek.com/2023/100/t1/auto-linked-hashtags-federated → 🔮 Glossary federation https://indieweb.org/federation h-entry https://microformats.org/wiki/h-entry Pingback https://indieweb.org/Pingback reply post https://indieweb.org/reply References ¹ https://web.archive.org/web/20130427010301/http://eschnou.com/entry/testing-indieweb-federation-with-waterpigscouk-aaronpareckicom-and--62-24908.html ² https://tantek.com/2023/014/t4/domain-first-federated-atmention ³ https://aaronparecki.com/2013/04/19/3/indieweb ⁴ https://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread ⁵ https://aaronparecki.com/2013/05/21/4/xkcd
: Imminent end of free use^1 of the Twitter API likely also means the end of free Log in with Twitter^2 delegated signin service^3.If you use [Sign in with Twitter]^4, consider replacing it with Web sign-in^5, implementing #RelMeAuth^6 & #IndieAuth^7 (OAuth for the #openWeb^8) ASAP!If you already have your own domain (got get one^9), add a link from your home page to your GitHub profile with rel=me^10, and then test it by using your domain to sign-in to:* https://indielogin.com/* https://indieweb.org/Any challenges or questions? Ask in #IndieWeb chat: https://chat.indieweb.org/devThis is day 27 of #100DaysOfIndieWeb #100Days← Day 26: https://tantek.com/2023/032/t1/years-relmeauth-replace-openid→ 🔮^1 https://www.theverge.com/2023/2/2/23582615/twitter-removing-free-api-developer-apps-price-announcement^2 https://indieweb.org/Log_in_with_Twitter^3 https://indieweb.org/silo_sign-in^4 https://indieweb.org/Log_in_with_Twitter#Button^5 https://indieweb.org/Web_sign-in^6 https://tantek.com/2023/032/t1/years-relmeauth-replace-openid^7 https://indieauth.spec.indieweb.org/^8 https://indieauth.net/^9 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb^10 https://indieweb.org/How_to_set_up_web_sign-in_on_your_own_domain#How_to_setup_RelMeAuth
's status on Friday, 03-Feb-2023 02:59:00 EST
Imminent end of free use^1 of the Twitter API likely also means the end of free Log in with Twitter^2 delegated signin service^3. If you use [Sign in with Twitter]^4, consider replacing it with Web sign-in^5, implementing #RelMeAuth^6 & #IndieAuth^7 (OAuth for the #openWeb^8) ASAP! If you already have your own domain (got get one^9), add a link from your home page to your GitHub profile with rel=me^10, and then test it by using your domain to sign-in to: * https://indielogin.com/ * https://indieweb.org/ Any challenges or questions? Ask in #IndieWeb chat: https://chat.indieweb.org/dev This is day 27 of #100DaysOfIndieWeb #100Days ← Day 26: https://tantek.com/2023/032/t1/years-relmeauth-replace-openid → 🔮 ^1 https://www.theverge.com/2023/2/2/23582615/twitter-removing-free-api-developer-apps-price-announcement ^2 https://indieweb.org/Log_in_with_Twitter ^3 https://indieweb.org/silo_sign-in ^4 https://indieweb.org/Log_in_with_Twitter#Button ^5 https://indieweb.org/Web_sign-in ^6 https://tantek.com/2023/032/t1/years-relmeauth-replace-openid ^7 https://indieauth.spec.indieweb.org/ ^8 https://indieauth.net/ ^9 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb ^10 https://indieweb.org/How_to_set_up_web_sign-in_on_your_own_domain#How_to_setup_RelMeAuth
: #indieweb 🤝 #fediverse✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd)✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indiewebPreviously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
's status on Friday, 02-Dec-2022 15:01:00 EST
#indieweb 🤝 #fediverse ✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd) ✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/ ✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb Previously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
: Published today: https://webvision.mozilla.org/Years of working with co-workers @Mozilla, and something I’m proud of. #OpenWeb #IndieWeb fans & #webdevs see https://webvision.mozilla.org/full/ with #HTML #CSS #JS, nods to nascent #OpenUI @CSSWG #sustainability #s12y efforts, and a lot more.
's status on Wednesday, 23-Mar-2022 12:32:00 EDT
Published today: https://webvision.mozilla.org/ Years of working with co-workers @Mozilla, and something I’m proud of. #OpenWeb #IndieWeb fans & #webdevs see https://webvision.mozilla.org/full/ with #HTML #CSS #JS, nods to nascent #OpenUI @CSSWG #sustainability #s12y efforts, and a lot more.
: Sometimes with months of nearly weekly meetings with co-workers & colleagues at other companies debating things, and building upon lots of prior hard work, you can help ship a pretty cool #openweb collaborationhttps://twitter.com/mozhacks/status/1499442686293647363#Interop2022 blog posts:* https://hacks.mozilla.org/2022/03/interop-2022/* https://webkit.org/blog/12288/working-together-on-interop-2022/* https://bocoup.com/blog/interop-2022* https://web.dev/interop-2022* https://www.igalia.com/news/interop2022.html* https://aka.ms/microsoft-interop2022Really appreciated the time and thoughtfulness that everyone across companies put into this. It was great working together with so many folks that also care deepy about the open web and collectively making the web better for authors & developers.
's status on Thursday, 03-Mar-2022 20:35:00 EST
Sometimes with months of nearly weekly meetings with co-workers & colleagues at other companies debating things, and building upon lots of prior hard work, you can help ship a pretty cool #openweb collaboration https://twitter.com/mozhacks/status/1499442686293647363 #Interop2022 blog posts: * https://hacks.mozilla.org/2022/03/interop-2022/ * https://webkit.org/blog/12288/working-together-on-interop-2022/ * https://bocoup.com/blog/interop-2022 * https://web.dev/interop-2022 * https://www.igalia.com/news/interop2022.html * https://aka.ms/microsoft-interop2022 Really appreciated the time and thoughtfulness that everyone across companies put into this. It was great working together with so many folks that also care deepy about the open web and collectively making the web better for authors & developers.
: Posting notes on your site is the “Hello World” of the independent web.If you speak to the ideals of the #openWeb #decentralizedWeb #distributedWeb #federatedWeb #indieWeb or even #smallWeb, walk your talk: post your notes somewhere you control. Whether static HTML, server-generated from storage, or a service supporting your domain, choose a method that works sustainably for you, and stick to it.Questions about options and when or why to choose one or another?Ask: https://chat.indieweb.org/
's status on Sunday, 02-Jan-2022 19:00:00 EST
Posting notes on your site is the “Hello World” of the independent web. If you speak to the ideals of the #openWeb #decentralizedWeb #distributedWeb #federatedWeb #indieWeb or even #smallWeb, walk your talk: post your notes somewhere you control. Whether static HTML, server-generated from storage, or a service supporting your domain, choose a method that works sustainably for you, and stick to it. Questions about options and when or why to choose one or another? Ask: https://chat.indieweb.org/
: Ten years ago today I started working with Mozilla on #webStandards.https://tantek.com/2010/146/t1/work-with-mozilla-advancing-web-standardshttps://twitter.com/t/status/14764431903Still @Mozilla (now @W3C AC Rep), still working for a more #OpenWeb, and for an #IndieWeb that puts users in control instead of #BigTech.
's status on Tuesday, 26-May-2020 16:24:00 EDT
Ten years ago today I started working with Mozilla on #webStandards. https://tantek.com/2010/146/t1/work-with-mozilla-advancing-web-standards https://twitter.com/t/status/14764431903 Still @Mozilla (now @W3C AC Rep), still working for a more #OpenWeb, and for an #IndieWeb that puts users in control instead of #BigTech.
: Wrapped @IndieWebCamp SF and with that we completed:a record 12 IndieWebCamps this year in 11 cities! https://indieweb.org/citiesWatch https://2020.indieweb.org/ for more and sign-up for Austin & Summit in Portland!See you in 2020!#indieweb #openweb
's status on Sunday, 08-Dec-2019 19:21:00 EST
Wrapped @IndieWebCamp SF and with that we completed: a record 12 IndieWebCamps this year in 11 cities! https://indieweb.org/cities Watch https://2020.indieweb.org/ for more and sign-up for Austin & Summit in Portland! See you in 2020! #indieweb #openweb
: Here @IndieWebCamp SF day 2 we’re about to start demos any minute!Video feed is live *now*https://zoom.us/j/4955358768#indieweb #openweb
's status on Sunday, 08-Dec-2019 16:46:00 EST
Here @IndieWebCamp SF day 2 we’re about to start demos any minute! Video feed is live *now* https://zoom.us/j/4955358768 #indieweb #openweb
: #NewYorkCity friends! Going to the @IndieWebCamp #NYC pre-meetup/social at Stone Street Tavern @stonesttavern http://stonestreettavernnyc.com/ Come have eats & drinks with us! (@schmarty et al!) #indieweb #openweb(Be there in ~15 minutes!)
's status on Friday, 04-Oct-2019 18:01:00 EDT
#NewYorkCity friends! Going to the @IndieWebCamp #NYC pre-meetup/social at Stone Street Tavern @stonesttavern http://stonestreettavernnyc.com/ Come have eats & drinks with us! (@schmarty et al!) #indieweb #openweb (Be there in ~15 minutes!)
: IndieWebCamps open for sign-ups!❌ Amsterdam 9/28-29 before #ViewSource https://indieweb.org/2019/Amsterdam🏫 Oxford 9/28 https://indieweb.org/2019/Oxford🗽 NYC 10/5-6 https://indieweb.org/2019/NYC🎪 Brighton 10/19-20 before #MozFest https://indieweb.org/2019/Brighton#indieweb #openweb
's status on Friday, 09-Aug-2019 17:52:00 EDT
IndieWebCamps open for sign-ups! ❌ Amsterdam 9/28-29 before #ViewSource https://indieweb.org/2019/Amsterdam 🏫 Oxford 9/28 https://indieweb.org/2019/Oxford 🗽 NYC 10/5-6 https://indieweb.org/2019/NYC 🎪 Brighton 10/19-20 before #MozFest https://indieweb.org/2019/Brighton #indieweb #openweb
: Hello #Austin!Any Austin friends out & about downtown tonight?Looking forward to #IndieWebCamp Austin tomorrow morning at Capital (in the Omni lobby)Still a few spots available: https://2019.indieweb.org/austin#indieweb #openweb #dweb #independentweb
's status on Saturday, 23-Feb-2019 00:04:00 EST
Hello #Austin! Any Austin friends out & about downtown tonight? Looking forward to #IndieWebCamp Austin tomorrow morning at Capital (in the Omni lobby) Still a few spots available: https://2019.indieweb.org/austin #indieweb #openweb #dweb #independentweb
: 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@CSS3UIhttps://www.w3.org/TR/2018/REC-css-ui-3-20180621/Previously:https://twitter.com/css3ui/status/941695566194597889andhttp://tantek.com/2015/189/b1/css-basic-user-interface-level-3
's status on Thursday, 21-Jun-2018 13:47:00 EDT
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 & expertsRSVP:https://2018.indieweb.org/Learn, get inspired, brainstorm, design, create, make, and help grow the present & future of the independent #openweb!
's status on Tuesday, 12-Jun-2018 14:55:00 EDT
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
's status on Monday, 11-Jun-2018 16:45:00 EDT
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
's status on Wednesday, 14-Mar-2018 16:29:00 EDT
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-posseGreat post@Dries! #openweb#indiewebGo 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/devDrop by and say hi anytime!Tantek1^https://indieweb.org/Twitter#POSSE_to_Twitter2^https://indieweb.org/POSSE_to_Facebook3^https://indieweb.org/note4^https://indieweb.org/photo5^https://indieweb.org/reply6^https://indieweb.org/multiple-reply7^https://indieweb.org/Twitter#original_has_POSSE_tweet
's status on Tuesday, 06-Feb-2018 13:36:00 EST
“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
: Today is the 1 year anniversary of the Webmention REC from the @W3C @SocialWebWG! https://www.w3.org/TR/2017/REC-webmention-20170112/And over 1 million webmentions have been sent peer-to-peer on the #openweb https://snarfed.org/1-million-webmentionsCome celebrate! 2018-01-24: https://indieweb.org/events/2018-01-24-homebrew-website-club
's status on Saturday, 13-Jan-2018 00:42:00 EST
Today is the 1 year anniversary of the Webmention REC from the @W3C @SocialWebWG! https://www.w3.org/TR/2017/REC-webmention-20170112/ And over 1 million webmentions have been sent peer-to-peer on the #openweb https://snarfed.org/1-million-webmentions Come celebrate! 2018-01-24: https://indieweb.org/events/2018-01-24-homebrew-website-club
: When:2017-12-13 18:30…19:30-0600Where:Halcyon AustinHost:Manton ReeceLast minute but if you’re in Austin, whether usually or here for @Mozilla #yallhands, come on by for an informal #indieweb meetup for practicing enthusiasts of the #openweb! A few topics:Net Neutrality!IndieWebCamp Austinhighlights!2018-01-01-commitmentsJan 20-21: IndieWebCamp Baltimorecoming up!Demos of personal website breakthroughs. Create or update your personal web site!Join a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!Any questions? Ask in#indieweb Slack or IRCMore information:IndieWeb Wiki Event Pagepost anindie RSVPon your own site! First three may get a special prize! (must attend to get, void where prohibited etc.:)
's status on Wednesday, 13-Dec-2017 18:04:00 EST
When:2017-12-13 18:30…19:30-0600Where:Halcyon AustinHost:Manton Reece Last minute but if you’re in Austin, whether usually or here for @Mozilla #yallhands, come on by for an informal #indieweb meetup for practicing enthusiasts of the #openweb! A few topics: Net Neutrality! IndieWebCamp Austinhighlights! 2018-01-01-commitments Jan 20-21: IndieWebCamp Baltimorecoming up! Demos of personal website breakthroughs. Create or update your personal web site! Join a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web! Any questions? Ask in#indieweb Slack or IRC More information:IndieWeb Wiki Event Page post anindie RSVPon your own site! First three may get a special prize! (must attend to get, void where prohibited etc.:)
: .@beephttps://ethanmarcotte.com/wrote/seven-into-seven/&@adactiohttps://adactio.com/journal/13035I.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-orgMore:https://indieweb.org/AMP
's status on Tuesday, 31-Oct-2017 00:20:00 EDT
.@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/
's status on Friday, 16-Jun-2017 19:23:51 EDT
#IndieWebSummit is in ONE WEEK! only 4 tickets left! Want to grow the #OpenWeb? Join us:https://2017.indieweb.org/
bobjonkmanformer: #Best_Practices would say "Block everything, allow only what's necessary" implying that outbound ping sh http://sn.jonkman.ca/notice/393918
bobjonkmanformer's status on Friday, 13-Jun-2014 12:30:30 EDT
#Best_Practices would say "Block everything, allow only what's necessary" implying that outbound ping sh…
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca