Finally had a chance to catch up with Renee and Chris on the @theelecticradicalshow
bit.ly/3ZbNv6E
Renee knows so much more then most on campaign finance laws.
I relied on Renee a ton to understand how PACs work.
Citizens United opened up the flood gates.
{
"type": "entry",
"published": "2023-02-21T13:56:40+00:00",
"url": "https://twitter.com/jgmac1106/status/1628030948792049665",
"content": {
"text": "Finally had a chance to catch up with Renee and Chris on the @theelecticradicalshow\n\nbit.ly/3ZbNv6E\n\nRenee knows so much more then most on campaign finance laws.\n\nI relied on Renee a ton to understand how PACs work.\n\nCitizens United opened up the flood gates.",
"html": "Finally had a chance to catch up with Renee and Chris on the @theelecticradicalshow\n\n<a href=\"https://bit.ly/3ZbNv6E\">bit.ly/3ZbNv6E</a>\n\nRenee knows so much more then most on campaign finance laws.\n\nI relied on Renee a ton to understand how PACs work.\n\nCitizens United opened up the flood gates."
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1617853032296759297/a0oAyyvh.jpg"
},
"post-type": "note",
"_id": "35307128",
"_source": "2773"
}
{
"type": "entry",
"published": "2023-02-21T13:26:11+00:00",
"url": "https://twitter.com/jgmac1106/status/1628023278739636224",
"content": {
"text": "Can I ask an old guy on the Internet question/\n\nWhat does rAnDOm CaPITaliZaTiON supposed to signify to the audience?\n\n#nafo #disinfo #literacies",
"html": "Can I ask an old guy on the Internet question/\n\nWhat does rAnDOm CaPITaliZaTiON supposed to signify to the audience?\n\n<a href=\"https://twitter.com/search?q=%23nafo\">#nafo</a> <a href=\"https://twitter.com/search?q=%23disinfo\">#disinfo</a> <a href=\"https://twitter.com/search?q=%23literacies\">#literacies</a>"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1617853032296759297/a0oAyyvh.jpg"
},
"post-type": "note",
"_id": "35306403",
"_source": "2773"
}
{
"type": "entry",
"published": "2023-02-21T12:12:36+00:00",
"url": "https://twitter.com/jgmac1106/status/1628004759092207617",
"content": {
"text": "Who has a link to text of Putin's speech he gave in The Russia?"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1617853032296759297/a0oAyyvh.jpg"
},
"post-type": "note",
"_id": "35305161",
"_source": "2773"
}
Each of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users.
Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others:
#LinkedDataNotifications (LDN) #WebSub
To be fair, LDN was only one building block in what eventually became SoLiD², the basis of Tim Berners–Lee’s startup Inrupt.
However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted³, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either.
The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite⁴, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time.
One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose?
As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing other approaches.
We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully.
From 15+ different approaches, or projects, or efforts that were brought⁵ to the working group, we narrowed them down to about 2.5 which I can summarize as:
1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites
2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc.
2.5 "something with Linked Data (LD)" — expressed as a 0.5 because there wasn’t anything user-visible “social web” with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two.
As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else’s approach.
It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions.
I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked.
I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space.
I’m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on.
With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed⁶.
Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services.
Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety⁷ of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way.
There’s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day.
For now, if you’re curious for more, I strongly recommend diving into the group’s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there.
If you’re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations⁸.
If you’re not sure, pop by the indieweb-dev chat and ask anyway!
The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group.
{
"type": "entry",
"published": "2023-02-20 19:16-0800",
"url": "https://tantek.com/2023/051/t1/five-years-ago-w3c-social-web",
"category": [
"fediverse",
"IndieWeb:",
"Webmention",
"Micropub",
"ActivityStreams2",
"ActivityPub",
"LinkedDataNotifications",
"WebSub",
"IndieWeb",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "Five years ago last Monday, the @W3C Social Web Working Group officially closed\u00b9.\n\nOperating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb:\n\n#Webmention\n#Micropub\n#ActivityStreams2\n#ActivityPub\n\nEach of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users.\n\nTwo additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they\u2019re both fairly invisible \"plumbing\" (as most specs should be) or they haven\u2019t picked up widespread use like the others:\n\n#LinkedDataNotifications (LDN)\n#WebSub\n\nTo be fair, LDN was only one building block in what eventually became SoLiD\u00b2, the basis of Tim Berners\u2013Lee\u2019s startup Inrupt.\n\nHowever, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted\u00b3, \u201cnobody ran to the \u2019web3\u2019 platforms\u201d, and nobody ran to SoLiD either.\n\nThe other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite\u2074, WebSub\u2019s adoption hasn\u2019t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time.\n\n\nOne of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose?\n\nAs one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing other approaches.\n\nWe (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully.\n\nFrom 15+ different approaches, or projects, or efforts that were brought\u2075 to the working group, we narrowed them down to about 2.5 which I can summarize as:\n\n1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites\n\n2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc.\n\n2.5 \"something with Linked Data (LD)\" \u2014 expressed as a 0.5 because there wasn\u2019t anything user-visible \u201csocial web\u201d with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two.\n\n\nAs chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else\u2019s approach.\n\nIt was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions.\n\nI saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked.\n\nI also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space.\n\nI\u2019m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on.\n\nWith hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed\u2076. \n\nMillions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services.\n\nChoosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety\u2077 of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way.\n\nThere\u2019s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day.\n\nFor now, if you\u2019re curious for more, I strongly recommend diving into the group\u2019s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there.\n\nIf you\u2019re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations\u2078.\n\nYou can find the various IndieWeb building blocks living specifications here:\n* https://spec.indieweb.org/\nAnd discussions thereof in the development chat channel:\n* https://chat.indieweb.org/dev\n\nIf you\u2019re not sure, pop by the indieweb-dev chat and ask anyway!\n\nThe IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group.\n\n\nThis is day 33 of #100DaysOfIndieWeb #100Days\n\n\u2190 Day 32: https://tantek.com/2023/047/t1/nineteen-years-microformats\n\u2192 \ud83d\udd2e\n\n\nPost Glossary:\n\nActivityPub\n\u00a0https://www.w3.org/TR/activitypub/ \nActivityStreams2\n\u00a0https://www.w3.org/TR/activitystreams-core/\n\u00a0https://www.w3.org/TR/activitystreams-vocabulary/\nLinked Data Notifications\n\u00a0https://www.w3.org/TR/ldn/\nMicropub\n\u00a0https://micropub.spec.indieweb.org/\nWebmention\n\u00a0https://webmention.net/draft/\nWebSub\n\u00a0https://www.w3.org/TR/websub/\n\n\nReferences:\n\u00b9 https://www.w3.org/wiki/Socialwg\n\u00b2 https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid\n\u00b3 https://mastodon.cloud/@anildash/109299991009836007\n\u2074 https://websub.rocks/\n\u2075 https://indieweb.org/Social_Web_Working_Group#History\n\u2076 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed\n\u2077 https://indieweb.org/plurality\n\u2078 https://indieweb.org/use_what_you_make",
"html": "Five years ago last Monday, the <a class=\"h-cassis-username\" href=\"https://twitter.com/W3C\">@W3C</a> Social Web Working Group officially closed<a href=\"https://tantek.com/#t5PU1_note-1\">\u00b9</a>.<br /><br />Operating for less than four years, it standardized several foundations of the #<span class=\"p-category\">fediverse</span> & #<span class=\"p-category\">IndieWeb:</span><br /><br />#<span class=\"p-category\">Webmention</span><br />#<span class=\"p-category\">Micropub</span><br />#<span class=\"p-category\">ActivityStreams2</span><br />#<span class=\"p-category\">ActivityPub</span><br /><br />Each of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users.<br /><br />Two additional specifications also had several implementations as of the time of their publication as a W3C Recommendations (which you can find from the Implementation Report linked near the top of each spec). However today they\u2019re both fairly invisible \"plumbing\" (as most specs should be) or they haven\u2019t picked up widespread use like the others:<br /><br />#<span class=\"p-category\">LinkedDataNotifications</span> (LDN)<br />#<span class=\"p-category\">WebSub</span><br /><br />To be fair, LDN was only one building block in what eventually became SoLiD<a href=\"https://tantek.com/#t5PU1_note-2\">\u00b2</a>, the basis of Tim Berners\u2013Lee\u2019s startup Inrupt.<br /><br />However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted<a href=\"https://tantek.com/#t5PU1_note-3\">\u00b3</a>, \u201cnobody ran to the \u2019web3\u2019 platforms\u201d, and nobody ran to SoLiD either.<br /><br />The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite<a href=\"https://tantek.com/#t5PU1_note-4\">\u2074</a>, WebSub\u2019s adoption hasn\u2019t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time.<br /><br /><br />One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose?<br /><br />As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing other approaches.<br /><br />We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully.<br /><br />From 15+ different approaches, or projects, or efforts that were brought<a href=\"https://tantek.com/#t5PU1_note-5\">\u2075</a> to the working group, we narrowed them down to about 2.5 which I can summarize as:<br /><br />1. #<span class=\"p-category\">IndieWeb</span> building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites<br /><br />2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc.<br /><br />2.5 \"something with Linked Data (LD)\" \u2014 expressed as a 0.5 because there wasn\u2019t anything user-visible \u201csocial web\u201d with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two.<br /><br /><br />As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else\u2019s approach.<br /><br />It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions.<br /><br />I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked.<br /><br />I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space.<br /><br />I\u2019m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on.<br /><br />With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed<a href=\"https://tantek.com/#t5PU1_note-6\">\u2076</a>. <br /><br />Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services.<br /><br />Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety<a href=\"https://tantek.com/#t5PU1_note-7\">\u2077</a> of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way.<br /><br />There\u2019s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day.<br /><br />For now, if you\u2019re curious for more, I strongly recommend diving into the group\u2019s wiki <a href=\"https://www.w3.org/wiki/Socialwg\">https://www.w3.org/wiki/Socialwg</a> and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there.<br /><br />If you\u2019re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations<a href=\"https://tantek.com/#t5PU1_note-8\">\u2078</a>.<br /><br />You can find the various IndieWeb building blocks living specifications here:<br />* <a href=\"https://spec.indieweb.org/\">https://spec.indieweb.org/</a><br />And discussions thereof in the development chat channel:<br />* <a href=\"https://chat.indieweb.org/dev\">https://chat.indieweb.org/dev</a><br /><br />If you\u2019re not sure, pop by the indieweb-dev chat and ask anyway!<br /><br />The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group.<br /><br /><br />This is day 33 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span><br /><br />\u2190 Day 32: <a href=\"https://tantek.com/2023/047/t1/nineteen-years-microformats\">https://tantek.com/2023/047/t1/nineteen-years-microformats</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Post Glossary:<br /><br />ActivityPub<br />\u00a0<a href=\"https://www.w3.org/TR/activitypub/\">https://www.w3.org/TR/activitypub/</a> <br />ActivityStreams2<br />\u00a0<a href=\"https://www.w3.org/TR/activitystreams-core/\">https://www.w3.org/TR/activitystreams-core/</a><br />\u00a0<a href=\"https://www.w3.org/TR/activitystreams-vocabulary/\">https://www.w3.org/TR/activitystreams-vocabulary/</a><br />Linked Data Notifications<br />\u00a0<a href=\"https://www.w3.org/TR/ldn/\">https://www.w3.org/TR/ldn/</a><br />Micropub<br />\u00a0<a href=\"https://micropub.spec.indieweb.org/\">https://micropub.spec.indieweb.org/</a><br />Webmention<br />\u00a0<a href=\"https://webmention.net/draft/\">https://webmention.net/draft/</a><br />WebSub<br />\u00a0<a href=\"https://www.w3.org/TR/websub/\">https://www.w3.org/TR/websub/</a><br /><br /><br />References:<br /><a href=\"https://tantek.com/#t5PU1_ref-1\">\u00b9</a> <a href=\"https://www.w3.org/wiki/Socialwg\">https://www.w3.org/wiki/Socialwg</a><br /><a href=\"https://tantek.com/#t5PU1_ref-2\">\u00b2</a> <a href=\"https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid\">https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid</a><br /><a href=\"https://tantek.com/#t5PU1_ref-3\">\u00b3</a> <a href=\"https://mastodon.cloud/@anildash/109299991009836007\">https://mastodon.cloud/@anildash/109299991009836007</a><br /><a href=\"https://tantek.com/#t5PU1_ref-4\">\u2074</a> <a href=\"https://websub.rocks/\">https://websub.rocks/</a><br /><a href=\"https://tantek.com/#t5PU1_ref-5\">\u2075</a> <a href=\"https://indieweb.org/Social_Web_Working_Group#History\">https://indieweb.org/Social_Web_Working_Group#History</a><br /><a href=\"https://tantek.com/#t5PU1_ref-6\">\u2076</a> <a href=\"https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed\">https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed</a><br /><a href=\"https://tantek.com/#t5PU1_ref-7\">\u2077</a> <a href=\"https://indieweb.org/plurality\">https://indieweb.org/plurality</a><br /><a href=\"https://tantek.com/#t5PU1_ref-8\">\u2078</a> <a href=\"https://indieweb.org/use_what_you_make\">https://indieweb.org/use_what_you_make</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "35303085",
"_source": "2460"
}
{
"type": "entry",
"published": "2023-02-21T09:39:54+00:00",
"url": "https://twitter.com/t/status/1627966333274177538",
"content": {
"text": "Five years ago last Monday, the @W3C Social Web Working Group officially closed^1.\n\nOperating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb:\n\n#Webmention\n#Micropub\n#ActivityStreams2\n#ActivityPub\n\nEach of ...\ntantek.com/t5PU1",
"html": "Five years ago last Monday, the <a href=\"https://twitter.com/w3c\">@W3C</a> Social Web Working Group officially closed^1.\n\nOperating for less than four years, it standardized several foundations of the <a href=\"https://twitter.com/search?q=%23fediverse\">#fediverse</a> & <a href=\"https://twitter.com/search?q=%23IndieWeb\">#IndieWeb</a>:\n\n<a href=\"https://twitter.com/search?q=%23Webmention\">#Webmention</a>\n<a href=\"https://twitter.com/search?q=%23Micropub\">#Micropub</a>\n<a href=\"https://twitter.com/search?q=%23ActivityStreams2\">#ActivityStreams2</a>\n<a href=\"https://twitter.com/search?q=%23ActivityPub\">#ActivityPub</a>\n\nEach of ...\n<a href=\"https://tantek.com/t5PU1\">tantek.com/t5PU1</a>"
},
"author": {
"type": "card",
"name": "Tantek",
"url": "https://twitter.com/t",
"photo": "https://pbs.twimg.com/profile_images/423350922408767488/nlA_m2WH.jpeg"
},
"post-type": "note",
"_id": "35302630",
"_source": "2773"
}
{
"type": "entry",
"published": "2023-02-20T22:01:17-08:00",
"url": "https://beesbuzz.biz/blog/14543-Transformative-Meditations",
"name": "Transformative Meditations",
"content": {
"text": "I decided to start an experimental meditation podcast after thinking about the concept for the past few weeks. I have a few episodes planned already and am working on a topic/prompt generator that will hopefully give me unlimited possibilities for where to take it. It\u2019s still an experiment, though.Hopefully it\u2019s something I can keep going, because I love the idea, at least.Hopefully I can also get it listed on the various podcast directories and apps. Right now the big one that\u2019s missing is Apple, because their podcast directory account signup thing is broken EDIT: it\u2019s working now, and I\u2019m just waiting for them to process the submission, yay EDIT2: it\u2019s available on Apple now. But it should already be on Amazon/Audible, Spotify, iHeartRadio, and Stitcher, and I can see about adding it to other directories if people want them.Also, eventually the public podcast will be monetized, but I\u2019ll always have ad-free versions over on my Patreon, and I hope to get a few more episodes done by the end of February, in which case they\u2019ll be over on the itch.io page that exists for Reasons.",
"html": "<p>I decided to start <a href=\"https://anchor.fm/transformative-meditation\">an experimental meditation podcast</a> after thinking about the concept for the past few weeks. I have a few episodes planned already and am working on a topic/prompt generator that will hopefully give me unlimited possibilities for where to take it. It\u2019s still an experiment, though.</p><p>Hopefully it\u2019s something I can keep going, because I love the idea, at least.</p><p>Hopefully I can also get it listed on the various podcast directories and apps. Right now the big one that\u2019s missing is Apple, because <del>their podcast directory account signup thing is broken</del> EDIT: it\u2019s working now, and I\u2019m just waiting for them to process the submission, yay EDIT2: <a href=\"https://podcasts.apple.com/us/podcast/transformative-meditations/id1673239458\">it\u2019s available on Apple now</a>. But it should already be on <a href=\"https://music.amazon.com/podcasts/f7bfb8a0-3708-47b9-a929-5e21ce711883/transformative-meditations\">Amazon/Audible</a>, <a href=\"https://open.spotify.com/show/1eLv6561lyDy0gfd5lmq37\">Spotify</a>, <a href=\"https://iheart.com/podcast/109278340/\">iHeartRadio</a>, and <a href=\"https://www.stitcher.com/show/1058538\">Stitcher</a>, and I can see about adding it to other directories if people want them.</p><p>Also, eventually the public podcast will be monetized, but I\u2019ll always have ad-free versions over on <a href=\"https://beesbuzz.biz/patreon\">my Patreon</a>, and I hope to get a few more episodes done by the end of February, in which case they\u2019ll be over on <a href=\"https://fluffy.itch.io/transformative-meditations\">the itch.io page that exists for Reasons</a>.</p>"
},
"author": {
"type": "card",
"name": "fluffy",
"url": "https://beesbuzz.biz/",
"photo": "https://beesbuzz.biz/static/headshot.jpg"
},
"post-type": "article",
"_id": "35302490",
"_source": "2778"
}
I teach my #edtechchat classes same in Kindergarten and College
get a space online
tell your story (really a text structure lesson shhh)
Learn something
Teach something
Do something
you can adapt that to any tool or introduce tool as buffet and they choose a dish for portfolio
{
"type": "entry",
"published": "2023-02-21T01:39:10+00:00",
"url": "https://twitter.com/jgmac1106/status/1627845352840654851",
"content": {
"text": "I teach my #edtechchat classes same in Kindergarten and College\n\nget a space online\ntell your story (really a text structure lesson shhh)\nLearn something\nTeach something\nDo something\n\nyou can adapt that to any tool or introduce tool as buffet and they choose a dish for portfolio",
"html": "I teach my <a href=\"https://twitter.com/search?q=%23edtechchat\">#edtechchat</a> classes same in Kindergarten and College\n\nget a space online\ntell your story (really a text structure lesson shhh)\nLearn something\nTeach something\nDo something\n\nyou can adapt that to any tool or introduce tool as buffet and they choose a dish for portfolio"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1617853032296759297/a0oAyyvh.jpg"
},
"post-type": "note",
"_id": "35296749",
"_source": "2773"
}
Now I am familiar how the right loves trans allegory of red pill and blue pill
Has anyone heard of White Pill?
I am old and not hip to new Internet lingo
Is it like white flag like Libertarian Party surrenders to Russia?
Or white flag as in White Power?
#NAFO do you know?
Today was wild! At one point I had @RonPaul @TulsiGabbard @scotthortonshow @jimmy_dore and @angela4LNCChair all within a 10 foot radius of me. Talk about a white pill! Th...
{
"type": "entry",
"published": "2023-02-20T23:49:17+00:00",
"url": "https://twitter.com/jgmac1106/status/1627817698619977731",
"quotation-of": "https://twitter.com/bk2forMaryland/status/1627472450400272384",
"content": {
"text": "Now I am familiar how the right loves trans allegory of red pill and blue pill\n\nHas anyone heard of White Pill?\n\nI am old and not hip to new Internet lingo\n\nIs it like white flag like Libertarian Party surrenders to Russia?\n\nOr white flag as in White Power?\n\n#NAFO do you know?",
"html": "Now I am familiar how the right loves trans allegory of red pill and blue pill\n\nHas anyone heard of White Pill?\n\nI am old and not hip to new Internet lingo\n\nIs it like white flag like Libertarian Party surrenders to Russia?\n\nOr white flag as in White Power?\n\n<a href=\"https://twitter.com/search?q=%23NAFO\">#NAFO</a> do you know?"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1617853032296759297/a0oAyyvh.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/bk2forMaryland/status/1627472450400272384": {
"type": "entry",
"published": "2023-02-20T00:57:23+00:00",
"url": "https://twitter.com/bk2forMaryland/status/1627472450400272384",
"photo": [
"https://pbs.twimg.com/media/FpXxkWWXoAYJQnX.jpg"
],
"content": {
"text": "Today was wild! At one point I had @RonPaul @TulsiGabbard @scotthortonshow @jimmy_dore and @angela4LNCChair all within a 10 foot radius of me. Talk about a white pill! Thank you @RageAgainstWar_ for the honor!",
"html": "Today was wild! At one point I had <a href=\"https://twitter.com/RonPaul\">@RonPaul</a> <a href=\"https://twitter.com/TulsiGabbard\">@TulsiGabbard</a> <a href=\"https://twitter.com/scotthortonshow\">@scotthortonshow</a> <a href=\"https://twitter.com/jimmy_dore\">@jimmy_dore</a> and <a href=\"https://twitter.com/angela4LNCChair\">@angela4LNCChair</a> all within a 10 foot radius of me. Talk about a white pill! Thank you <a href=\"https://twitter.com/RageAgainstWar_\">@RageAgainstWar_</a> for the honor!"
},
"author": {
"type": "card",
"name": "Brian W. Kunkoski II",
"url": "https://twitter.com/bk2forMaryland",
"photo": "https://pbs.twimg.com/profile_images/1627687259095851015/iGQbNpv3.jpg"
},
"post-type": "photo"
}
},
"_id": "35295517",
"_source": "2773"
}
{
"type": "entry",
"published": "2023-02-20T17:41:00+00:00",
"url": "https://twitter.com/jgmac1106/status/1627725018263060484",
"content": {
"text": "I need a new book. What was your favorit space opera of the last few years?\n\n#scifi #writingcommunity #nctevillage",
"html": "I need a new book. What was your favorit space opera of the last few years?\n\n<a href=\"https://twitter.com/search?q=%23scifi\">#scifi</a> <a href=\"https://twitter.com/search?q=%23writingcommunity\">#writingcommunity</a> <a href=\"https://twitter.com/search?q=%23nctevillage\">#nctevillage</a>"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1617853032296759297/a0oAyyvh.jpg"
},
"post-type": "note",
"_id": "35287882",
"_source": "2773"
}
Umbrella
bent
into
cold Winter
rain, listless
shield
held
firmly
into winds
pelting at
misery's scars
A monument of
futility
stone carved by
sideways
shrapnel striking
with bitter
cold
Forlorn and
soaked
she marches
on
#smallpoems#mastoprompt
{
"type": "entry",
"author": {
"name": null,
"url": "https://herestomwiththeweather.com/",
"photo": null
},
"url": "https://herestomwiththeweather.com/2023/02/19/toews-has-long-covid/",
"published": "2023-02-19T21:36:21+00:00",
"content": {
"html": "<p>Today we learned that <a href=\"https://en.wikipedia.org/wiki/Jonathan_Toews\">a 34 year old hockey player</a>, a 6x all-star in the NHL\u2019s list of 100 greatest players of all time, <a href=\"https://www.cbc.ca/sports/hockey/nhl/jonathan-toews-nhl-roundup-feb19-1.6753912\">stopped playing hockey several weeks ago due to Long Covid</a>.</p>\n\n<p>The covid minimizer that now owns <a href=\"https://en.wikipedia.org/wiki/Twitter\">Twitter</a> intentionally allows misinformation to spread. <a href=\"https://www.staples.com/3m-aura-n95-particulate-respirator-white-20-pack-9205p-20-dc/product_24503827\">Mask up</a>.</p>",
"text": "Today we learned that a 34 year old hockey player, a 6x all-star in the NHL\u2019s list of 100 greatest players of all time, stopped playing hockey several weeks ago due to Long Covid.\n\nThe covid minimizer that now owns Twitter intentionally allows misinformation to spread. Mask up."
},
"name": "Toews has long covid",
"post-type": "article",
"_id": "35277258",
"_source": "246"
}
Today we learned that a 34 year old hockey player, a 6x all-star in the NHL's list of 100 greatest players of all time, stopped playing hockey several weeks ago due to #LongCovid
The covid minimizer that now owns this site intentionally allows misinformation to spread. Mask up.
{
"type": "entry",
"published": "2023-02-20T03:00:19+00:00",
"url": "https://twitter.com/tomwiththeweath/status/1627503386294734848",
"content": {
"text": "Today we learned that a 34 year old hockey player, a 6x all-star in the NHL's list of 100 greatest players of all time, stopped playing hockey several weeks ago due to #LongCovid \n\nThe covid minimizer that now owns this site intentionally allows misinformation to spread. Mask up.",
"html": "Today we learned that a 34 year old hockey player, a 6x all-star in the NHL's list of 100 greatest players of all time, stopped playing hockey several weeks ago due to <a href=\"https://twitter.com/search?q=%23LongCovid\">#LongCovid</a> \n\nThe covid minimizer that now owns this site intentionally allows misinformation to spread. Mask up."
},
"author": {
"type": "card",
"name": "herestomwiththeweather",
"url": "https://twitter.com/tomwiththeweath",
"photo": "https://pbs.twimg.com/profile_images/52629372/flickr.jpg"
},
"post-type": "note",
"_id": "35274504",
"_source": "2773"
}
{
"type": "entry",
"published": "2023-02-19T16:45:51-0500",
"url": "https://martymcgui.re/2023/02/19/this-week-in-the-indieweb-audio-edition--february-11th---17th-2023/",
"category": [
"podcast",
"IndieWeb",
"this-week-indieweb-podcast"
],
"audio": [
"https://media.martymcgui.re/a7/84/66/43/7902a7a5e1d8a413bd3a2262a02b736d4e00881370ae34e3977cea22.mp3"
],
"name": "This Week in the IndieWeb Audio Edition \u2022 February 11th - 17th, 2023",
"content": {
"text": "Show/Hide Transcript\n \n Rel you? Rel me. It\u2019s the audio edition for This Week in the IndieWeb for February 11th - 17th, 2023.\nYou can find all of my audio editions and subscribe with your favorite podcast app here: martymcgui.re/podcasts/indieweb/.\nMusic from Aaron Parecki\u2019s 100DaysOfMusic project: Day 85 - Suit, Day 48 - Glitch, Day 49 - Floating, Day 9, and Day 11\nThanks to everyone in the IndieWeb chat for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!",
"html": "Show/Hide Transcript\n \n <p>Rel you? Rel me. It\u2019s the audio edition for <a href=\"https://indieweb.org/this-week/2023-02-17.html\">This Week in the IndieWeb for February 11th - 17th, 2023</a>.</p>\n<p>You can find all of my audio editions and subscribe with your favorite podcast app here: <a href=\"https://martymcgui.re/podcasts/indieweb/\">martymcgui.re/podcasts/indieweb/</a>.</p>\n<p>Music from <a href=\"https://aaronparecki.com/\">Aaron Parecki</a>\u2019s <a href=\"https://100.aaronparecki.com/\">100DaysOfMusic project</a>: <a href=\"https://aaronparecki.com/2017/03/15/14/day85\">Day 85 - Suit</a>, <a href=\"https://aaronparecki.com/2017/02/06/7/day48\">Day 48 - Glitch</a>, <a href=\"https://aaronparecki.com/2017/02/07/4/day49\">Day 49 - Floating</a>, <a href=\"https://aaronparecki.com/2016/12/29/21/day-9\">Day 9</a>, and <a href=\"https://aaronparecki.com/2016/12/31/15/\">Day 11</a></p>\n<p>Thanks to everyone in the <a href=\"https://chat.indieweb.org/\">IndieWeb chat</a> for their feedback and suggestions. Please drop me a note if there are any changes you\u2019d like to see for this audio edition!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "audio",
"_id": "35271997",
"_source": "175"
}
