Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:
1. a short reply — directly on someone’s blog post comment form, OR
2. a longer reply — on your own blog, in-reply-to ...
tantek.com/t5Nu1
{
"type": "entry",
"published": "2023-01-18T00:26:28+00:00",
"url": "https://twitter.com/t/status/1615505867134337026",
"content": {
"text": "Replying to people on the social web used to be \u201csimple\u201d before #socialMedia, when we used blogs. You would either write:\n\n1. a short reply \u2014 directly on someone\u2019s blog post comment form, OR\n\n2. a longer reply \u2014 on your own blog, in-reply-to ...\ntantek.com/t5Nu1",
"html": "Replying to people on the social web used to be \u201csimple\u201d before <a href=\"https://twitter.com/search?q=%23socialMedia\">#socialMedia</a>, when we used blogs. You would either write:\n\n1. a short reply \u2014 directly on someone\u2019s blog post comment form, OR\n\n2. a longer reply \u2014 on your own blog, in-reply-to ...\n<a href=\"https://tantek.com/t5Nu1\">tantek.com/t5Nu1</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": "34483806",
"_source": "2773"
}
Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:
1. a short reply — directly on someone’s blog post comment form, OR
2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post
Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.
Then social media exploded and eventually everybody was replying everywhere all at once.
This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.
After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:
1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).
2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.
3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.
Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:
* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?
* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)
Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration.
As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.
This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.
← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮
^1 https://en.wikipedia.org/wiki/Internet_forum
^2 https://indieweb.org/silo
^3 https://indieweb.org/own_your_data
^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c
^5 https://indieweb.org/GitHub#POSSE_to_GitHub
^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
^7 https://indieweb.org/site-deaths
{
"type": "entry",
"published": "2023-01-17 09:05-0800",
"url": "https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post",
"category": [
"socialMedia",
"IndieWeb",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "Replying to people on the social web used to be \u201csimple\u201d before #socialMedia, when we used blogs. You would either write:\n\n1. a short reply \u2014 directly on someone\u2019s blog post comment form, OR\n\n2. a longer reply \u2014 on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post\u2019s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post\n\nAside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.\n\n\nThen social media exploded and eventually everybody was replying everywhere all at once.\n\nThis was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.\n\n\nAfter a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:\n\n1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).\n\n2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.\n\n3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.\n\n\nFollowing this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:\n\n* What is the most efficient user interface path from viewing someone else\u2019s post to writing a reply from your own site?\n\n* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)\n\nRegarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration. \n\nAs a follow-up to day 14, it\u2019s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.\n\nThis is day 16 of #100DaysOfIndieWeb #100Days, except I didn\u2019t finish writing it (mostly) til the morning after, and editing later that afternoon.\n\n\u2190 Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\n\u2192 \ud83d\udd2e\n\n\n^1 https://en.wikipedia.org/wiki/Internet_forum\n^2 https://indieweb.org/silo\n^3 https://indieweb.org/own_your_data\n^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c\n^5 https://indieweb.org/GitHub#POSSE_to_GitHub\n^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\n^7 https://indieweb.org/site-deaths",
"html": "Replying to people on the social web used to be \u201csimple\u201d before #<span class=\"p-category\">socialMedia</span>, when we used blogs. You would either write:<br /><br />1. a short reply \u2014 directly on someone\u2019s blog post comment form, OR<br /><br />2. a longer reply \u2014 on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post\u2019s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post<br /><br />Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.<br /><br /><br />Then social media exploded and eventually everybody was replying everywhere all at once.<br /><br />This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.<br /><br /><br />After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #<span class=\"p-category\">IndieWeb</span> sites:<br /><br />1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).<br /><br />2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.<br /><br />3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #<span class=\"p-category\">IndieWeb</span> record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.<br /><br /><br />Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:<br /><br />* What is the most efficient user interface path from viewing someone else\u2019s post to writing a reply from your own site?<br /><br />* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)<br /><br />Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general <a href=\"https://tantek.com/2023/014/t4/domain-first-federated-atmention\">https://tantek.com/2023/014/t4/domain-first-federated-atmention</a> though that was more of a general @-mention exploration. <br /><br />As a follow-up to day 14, it\u2019s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.<br /><br />This is day 16 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>, except I didn\u2019t finish writing it (mostly) til the morning after, and editing later that afternoon.<br /><br />\u2190 Day 15: <a href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br />\u2192 \ud83d\udd2e<br /><br /><br />^1 <a href=\"https://en.wikipedia.org/wiki/Internet_forum\">https://en.wikipedia.org/wiki/Internet_forum</a><br />^2 <a href=\"https://indieweb.org/silo\">https://indieweb.org/silo</a><br />^3 <a href=\"https://indieweb.org/own_your_data\">https://indieweb.org/own_your_data</a><br />^4 <a href=\"https://tantek.com/2023/012/t1/six-years-webmention-w3c\">https://tantek.com/2023/012/t1/six-years-webmention-w3c</a><br />^5 <a href=\"https://indieweb.org/GitHub#POSSE_to_GitHub\">https://indieweb.org/GitHub#POSSE_to_GitHub</a><br />^6 <a href=\"https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute\">https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute</a><br />^7 <a href=\"https://indieweb.org/site-deaths\">https://indieweb.org/site-deaths</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "34482914",
"_source": "2460"
}
We talked to more than two dozen Twitter employees about how Elon Musk’s takeover at the company upended their lives and the culture they knew. This is their story:
twitter.com/nymag/status/1…
Twitter’s staff spent years trying to protect the platform against impulsive billionaires who wanted to use it for their own ends — then one made himself the CEO. @Zo...
{
"type": "entry",
"published": "2023-01-17T14:16:24+00:00",
"url": "https://twitter.com/ZoeSchiffer/status/1615352340462305280",
"quotation-of": "https://twitter.com/NYMag/status/1615341133223051270",
"content": {
"text": "We talked to more than two dozen Twitter employees about how Elon Musk\u2019s takeover at the company upended their lives and the culture they knew. This is their story:\ntwitter.com/nymag/status/1\u2026",
"html": "We talked to more than two dozen Twitter employees about how Elon Musk\u2019s takeover at the company upended their lives and the culture they knew. This is their story:\n<a href=\"https://twitter.com/nymag/status/1615341133223051270\">twitter.com/nymag/status/1\u2026</a>"
},
"author": {
"type": "card",
"name": "Zo\u00eb Schiffer",
"url": "https://twitter.com/ZoeSchiffer",
"photo": "https://pbs.twimg.com/profile_images/1564799885794086914/ZU6qMT_n.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/NYMag/status/1615341133223051270": {
"type": "entry",
"published": "2023-01-17T13:31:52+00:00",
"url": "https://twitter.com/NYMag/status/1615341133223051270",
"photo": [
"https://pbs.twimg.com/media/FmrYMtxWQAczniQ.jpg"
],
"content": {
"text": "Twitter\u2019s staff spent years trying to protect the platform against impulsive billionaires who wanted to use it for their own ends \u2014 then one made himself the CEO. @ZoeSchiffer , @CaseyNewton , and @alexeheath report, in collaboration with @verge trib.al/FezDnWP",
"html": "Twitter\u2019s staff spent years trying to protect the platform against impulsive billionaires who wanted to use it for their own ends \u2014 then one made himself the CEO. <a href=\"https://twitter.com/ZoeSchiffer\">@ZoeSchiffer</a> , <a href=\"https://twitter.com/CaseyNewton\">@CaseyNewton</a> , and <a href=\"https://twitter.com/alexeheath\">@alexeheath</a> report, in collaboration with <a href=\"https://twitter.com/verge\">@verge</a> <a href=\"https://trib.al/FezDnWP\">trib.al/FezDnWP</a>"
},
"author": {
"type": "card",
"name": "New York Magazine",
"url": "https://twitter.com/NYMag",
"photo": "https://pbs.twimg.com/profile_images/2939680330/56f025f0104892f84a84c00bdb4ec812.png"
},
"post-type": "photo"
}
},
"_id": "34470934",
"_source": "2773"
}
Finished reading: Stories of Your Life and Others by Ted Chiang (ISBN 9781931520898)
{
"type": "entry",
"published": "2023-01-17 00:45-0800",
"url": "https://gregorlove.com/2023/01/finished-stories-of-your-life-and-others/",
"content": {
"text": "Finished reading: Stories of Your Life and Others by Ted Chiang (ISBN 9781931520898)",
"html": "<p>Finished reading: <span class=\"p-read-of h-cite\"><a class=\"u-url\" href=\"https://gregorlove.com/isbn/9781931520898\">Stories of Your Life and Others</a> by <span class=\"p-author\">Ted Chiang</span> (ISBN <span class=\"p-uid\">9781931520898</span>)</span></p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "note",
"_id": "34466837",
"_source": "95"
}
Have you found a good fit during eternal Caturday?
{
"type": "entry",
"published": "2023-01-17T00:07:02-0500",
"url": "https://martymcgui.re/2023/01/17/000702/",
"category": [
"Caturday"
],
"video": [
"https://res.cloudinary.com/schmarty/video/upload/vc_h264/mmmgre/fa/f0/77/b7/3f4aaecd81f54b4cd42b713b970bef2205a45ddf88f3674c43e20543.mov"
],
"content": {
"text": "Have you found a good fit during eternal Caturday?",
"html": "<p>Have you found a good fit during eternal Caturday?</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "video",
"_id": "34462553",
"_source": "175"
}
Why yes I did just paint my blank electrical plates to match the wall color because I didn't like how they stood out in white
{
"type": "entry",
"published": "2023-01-16T21:07:04+00:00",
"url": "https://twitter.com/aaronpk/status/1615093301044183040",
"photo": [
"https://pbs.twimg.com/media/Fmn2y47aEAECrxl.jpg"
],
"content": {
"text": "Why yes I did just paint my blank electrical plates to match the wall color because I didn't like how they stood out in white"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://twitter.com/aaronpk",
"photo": "https://pbs.twimg.com/profile_images/1477113672803622912/ljLUwFLP.jpg"
},
"post-type": "photo",
"_id": "34455076",
"_source": "2773"
}
Why yes I did just paint my blank electrical plates to match the wall color because I didn't like how they stood out in white
{
"type": "entry",
"published": "2023-01-16T13:06:59-08:00",
"url": "https://aaronparecki.com/2023/01/16/8/",
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/a70e81d663189f0ef76392a0c53bbc5fb4acb693a6709d366e5f872551d676e8.jpg"
],
"syndication": [
"https://twitter.com/aaronpk/status/1615093301044183040",
"https://aaronparecki.com/@aaronpk"
],
"content": {
"text": "Why yes I did just paint my blank electrical plates to match the wall color because I didn't like how they stood out in white"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "photo",
"_id": "34454912",
"_source": "16"
}
Protect your neck!!
What an awesome forge.
@Kolya728 @fellarequests @Official_NAFO @goblin__soup @Kama_Kamilia @BravoKilo6464 With his .50 Desert Eagle... your Wu-Tang Clan Fella can protect his neck while gettin'...
{
"type": "entry",
"published": "2023-01-16T19:20:17+00:00",
"url": "https://twitter.com/jgmac1106/status/1615066426280218624",
"quotation-of": "https://twitter.com/gr1mrea9er/status/1615064850459418625",
"content": {
"text": "Protect your neck!!\n\nWhat an awesome forge."
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/gr1mrea9er/status/1615064850459418625": {
"type": "entry",
"published": "2023-01-16T19:14:01+00:00",
"url": "https://twitter.com/gr1mrea9er/status/1615064850459418625",
"photo": [
"https://pbs.twimg.com/media/FmncZlHXEBkeAT8.jpg",
"https://pbs.twimg.com/media/FmncbNkWQAA0v7S.jpg"
],
"in-reply-to": [
"https://twitter.com/Kolya728/status/1614097199604043776"
],
"content": {
"text": "@Kolya728 @fellarequests @Official_NAFO @goblin__soup @Kama_Kamilia @BravoKilo6464 With his .50 Desert Eagle... your Wu-Tang Clan Fella can protect his neck while gettin' chill. Welcome to #NAFO #NAFOfellas #NAFOExpansionIsNonNegotiable!",
"html": "@Kolya728 <a href=\"https://twitter.com/fellarequests\">@fellarequests</a> <a href=\"https://twitter.com/Official_NAFO\">@Official_NAFO</a> <a href=\"https://twitter.com/goblin__soup\">@goblin__soup</a> <a href=\"https://twitter.com/Kama_Kamilia\">@Kama_Kamilia</a> <a href=\"https://twitter.com/BravoKilo6464\">@BravoKilo6464</a> With his .50 Desert Eagle... your Wu-Tang Clan Fella can protect his neck while gettin' chill. Welcome to <a href=\"https://twitter.com/search?q=%23NAFO\">#NAFO</a> <a href=\"https://twitter.com/search?q=%23NAFOfellas\">#NAFOfellas</a> <a href=\"https://twitter.com/search?q=%23NAFOExpansionIsNonNegotiable\">#NAFOExpansionIsNonNegotiable</a>!\n<a class=\"u-mention\" href=\"https://twitter.com/Kolya728\"></a>"
},
"author": {
"type": "card",
"name": "Gr1mRea9er\u2694",
"url": "https://twitter.com/gr1mrea9er",
"photo": "https://pbs.twimg.com/profile_images/1602951994427285506/JDLbOugB.jpg"
},
"post-type": "reply"
}
},
"_id": "34452797",
"_source": "2773"
}
Welcome to #NAFO @DJfromAnnapolis and here is your @fellarequests thank you for your long term support of #Ukraine, the numerous donations, and bringing the struggle to freedom to your radio show
{
"type": "entry",
"published": "2023-01-16T16:49:58+00:00",
"url": "https://twitter.com/jgmac1106/status/1615028598036959232",
"photo": [
"https://pbs.twimg.com/media/Fmm6J6MWYAAkzCm.jpg",
"https://pbs.twimg.com/media/Fmm7rNIWAAEAGK4.jpg"
],
"content": {
"text": "Welcome to #NAFO @DJfromAnnapolis and here is your @fellarequests thank you for your long term support of #Ukraine, the numerous donations, and bringing the struggle to freedom to your radio show",
"html": "Welcome to <a href=\"https://twitter.com/search?q=%23NAFO\">#NAFO</a> <a href=\"https://twitter.com/DJfromAnnapolis\">@DJfromAnnapolis</a> and here is your <a href=\"https://twitter.com/fellarequests\">@fellarequests</a> thank you for your long term support of <a href=\"https://twitter.com/search?q=%23Ukraine\">#Ukraine</a>, the numerous donations, and bringing the struggle to freedom to your radio show"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "photo",
"_id": "34449723",
"_source": "2773"
}
I always rewatch this on Martin Luther King day. The life and legacy of Martin Luther King is a topic too complicated for me to discuss in a simple note, but a Jewish and an African American group harmonizing together is not.
{
"type": "entry",
"published": "2023-01-16T15:55:05+00:00",
"url": "https://twitter.com/dshanske/status/1615014789352247298",
"content": {
"text": "I always rewatch this on Martin Luther King day. The life and legacy of Martin Luther King is a topic too complicated for me to discuss in a simple note, but a Jewish and an African American group harmonizing together is not."
},
"author": {
"type": "card",
"name": "David Shanske",
"url": "https://twitter.com/dshanske",
"photo": "https://pbs.twimg.com/profile_images/1364752349512671235/CCKrafqf.jpg"
},
"post-type": "note",
"_id": "34448366",
"_source": "2773"
}
Anyone else feels this too?
Like Governments are pressuring media to keep the extent of Russian infiltration and influence campaigns out of the news?
Anyone have any evidence, research or readings?
Or is paranoia growing?
Although there continues to be a corporate media blockade to the acknowledgement of links between global chaos and Russian active measures, in @BylineTimes authors of thi...
{
"type": "entry",
"published": "2023-01-16T13:55:33+00:00",
"url": "https://twitter.com/jgmac1106/status/1614984705434128384",
"quotation-of": "https://twitter.com/Heidi_Cuda/status/1614664542101057536",
"content": {
"text": "Anyone else feels this too?\n\nLike Governments are pressuring media to keep the extent of Russian infiltration and influence campaigns out of the news?\n\nAnyone have any evidence, research or readings?\n\nOr is paranoia growing?"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/Heidi_Cuda/status/1614664542101057536": {
"type": "entry",
"published": "2023-01-15T16:43:20+00:00",
"url": "https://twitter.com/Heidi_Cuda/status/1614664542101057536",
"in-reply-to": [
"https://twitter.com/Heidi_Cuda/status/1614663957972914180"
],
"content": {
"text": "Although there continues to be a corporate media blockade to the acknowledgement of links between global chaos and Russian active measures, in @BylineTimes authors of this article, Heidi and Matt, revealed examples of how easily and cheaply it is done.\nbylinetimes.com/2022/08/02/agi\u2026",
"html": "Although there continues to be a corporate media blockade to the acknowledgement of links between global chaos and Russian active measures, in <a href=\"https://twitter.com/BylineTimes\">@BylineTimes</a> authors of this article, Heidi and Matt, revealed examples of how easily and cheaply it is done.\n<a href=\"https://bylinetimes.com/2022/08/02/agitation-and-propaganda-russian-indicted-for-using-us-political-groups-as-foreign-agents/\">bylinetimes.com/2022/08/02/agi\u2026</a>"
},
"author": {
"type": "card",
"name": "Heidi Cuda",
"url": "https://twitter.com/Heidi_Cuda",
"photo": "https://pbs.twimg.com/profile_images/1484693697929232387/ui50IANB.jpg"
},
"post-type": "reply"
}
},
"_id": "34446158",
"_source": "2773"
}
When you publish on your #IndieWeb site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances.
We call this POSSE — for Publish on your Own Site, then Syndicate Elsewhere.^1
By prioritizing your own site, you decide whether (and when) you want to syndicate your posts (or a particular post) to a feed, to a fediverse, to a social media silo or silos, and/or to email like a newsletter.
You can make it as simple or as detailed as you want. It’s up to you.
Choose deliberately. Change your mind when things change.
You can opt out of any destination, either by not opting-in, i.e. explicitly not sending your posts to them, or blocking them if necessary.
Here are a few of the destination decisions I’ve made, and reasons why.
You can delay sending a post to an RSS or Atom feed, say 10 minutes after the time of publication, to give yourself a chance to edit your post, fix typos or links, before a classic feed reader retrieves and perhaps caches your post.
You can further delay sending to known uneditable destinations, like Twitter or email, to give yourself even longer to make further edits, corrections, updates, or improvements based on feedback to your original post.
Some destination decisions may depend on the type of post.
When you post a reply to someone else’s post, in addition to sending a webmention to that other post, it makes sense to also distribute it to where that other post was originally distributed, or a subset thereof, threading your POSSE reply with their original post POSSE copy.
https://indieweb.org/reply#POSSE_a_reply
For example, if you reply to someone’s IndieWeb note, and they’ve POSSEd that note to Twitter, you should POSSE your reply to Twitter as well, threading it with their POSSE copy, if you’re still using Twitter that is. If they did not POSSE their original note to Twitter, there may be reasons to POSSE your reply to Twitter anyway, if your reply makes sense there on its own.
https://indieweb.org/Twitter#POSSE_Replies_to_Twitter
Some destinations have content limitations^2, and you may want to take that into consideration when authoring your content, or not.
For example, you may want to more carefully copy-edit the first 256 (for now) characters of a note if you plan to POSSE to Twitter, so that the content that makes it through makes sense as an introduction, or a summary, or a hook, and perhaps has discovery features like hashtags.
https://indieweb.org/Twitter#POSSE_Notes_to_Twitter
You can use that POSSE tweet text length limitation strategically, placing content after that 256 character cut-off that you may want to edit or expand in an update, or content Twitter may mess-up, like @-domain mentions I described yesterday (day 14).
When you publish a multiphoto^3 post, if you’re POSSEing to Twitter, you may want to re-order your photos to choose which four photos show up in your POSSE tweet, e.g. if you happen to be using Bridgy Publish to cross-post your photos to Twitter. You can always re-order your original multiphoto post after POSSEing it.
If you’re POSSEing photos to Instagram, since you can only do that manually, there’s no need to edit your original to fit Instagram’s 10-photo limitation, or 2200 characters caption limit, or 30 hashtags limit, or 20 person-tags limit.
https://indieweb.org/multi-photo#How_to_POSSE
Or you can reconsider what if anything you get from syndicating to Twitter or Instagram.
Are people still seeing and interacting with your posts there? Are your friends?
If & when social media algorithms deprioritize your original posts in favor of showing more ads, you can deprioritize posting to social media.
If & when your friends quit social media silos^4, you can quit posting copies of your posts to those social media silos.
You decide what content goes where, when, why, and can change your decisions any time you want.
POSSEing to social media was always a stopgap.
As social media silos self-destruct, you can stop syndicating to them.
Thanks to Chris Aldrich (https://boffosocko.com/) for the banner image.
This is day 15 of #100DaysOfIndieWeb #100Days.
← Day 14: https://tantek.com/2023/014/t4/domain-first-federated-atmention
→ 🔮
^1 https://indieweb.org/POSSE
^2 Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach
^3 https://indieweb.org/multi-photo
^4 https://indieweb.org/silo-quits
{
"type": "entry",
"published": "2023-01-15 23:58-0800",
"url": "https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute",
"category": [
"IndieWeb",
"100DaysOfIndieWeb",
"100Days"
],
"photo": [
"https://indieweb.org/images/6/6a/fit-into-the-network.png"
],
"content": {
"text": "When you publish on your #IndieWeb site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances.\nWe call this POSSE \u2014 for Publish on your Own Site, then Syndicate Elsewhere.^1\n\nBy prioritizing your own site, you decide whether (and when) you want to syndicate your posts (or a particular post) to a feed, to a fediverse, to a social media silo or silos, and/or to email like a newsletter.\n\nYou can make it as simple or as detailed as you want. It\u2019s up to you.\n\nChoose deliberately. Change your mind when things change.\n\u00a0\nYou can opt out of any destination, either by not opting-in, i.e. explicitly not sending your posts to them, or blocking them if necessary.\n\nHere are a few of the destination decisions I\u2019ve made, and reasons why.\n\nYou can delay sending a post to an RSS or Atom feed, say 10 minutes after the time of publication, to give yourself a chance to edit your post, fix typos or links, before a classic feed reader retrieves and perhaps caches your post.\n\nYou can further delay sending to known uneditable destinations, like Twitter or email, to give yourself even longer to make further edits, corrections, updates, or improvements based on feedback to your original post.\n\nSome destination decisions may depend on the type of post.\n\nWhen you post a reply to someone else\u2019s post, in addition to sending a webmention to that other post, it makes sense to also distribute it to where that other post was originally distributed, or a subset thereof, threading your POSSE reply with their original post POSSE copy.\n\nhttps://indieweb.org/reply#POSSE_a_reply\n\nFor example, if you reply to someone\u2019s IndieWeb note, and they\u2019ve POSSEd that note to Twitter, you should POSSE your reply to Twitter as well, threading it with their POSSE copy, if you\u2019re still using Twitter that is. If they did not POSSE their original note to Twitter, there may be reasons to POSSE your reply to Twitter anyway, if your reply makes sense there on its own.\n\nhttps://indieweb.org/Twitter#POSSE_Replies_to_Twitter\n\nSome destinations have content limitations^2, and you may want to take that into consideration when authoring your content, or not.\n\nFor example, you may want to more carefully copy-edit the first 256 (for now) characters of a note if you plan to POSSE to Twitter, so that the content that makes it through makes sense as an introduction, or a summary, or a hook, and perhaps has discovery features like hashtags. \n\nhttps://indieweb.org/Twitter#POSSE_Notes_to_Twitter\n\nYou can use that POSSE tweet text length limitation strategically, placing content after that 256 character cut-off that you may want to edit or expand in an update, or content Twitter may mess-up, like @-domain mentions I described yesterday (day 14).\n\nWhen you publish a multiphoto^3 post, if you\u2019re POSSEing to Twitter, you may want to re-order your photos to choose which four photos show up in your POSSE tweet, e.g. if you happen to be using Bridgy Publish to cross-post your photos to Twitter. You can always re-order your original multiphoto post after POSSEing it. \n\nIf you\u2019re POSSEing photos to Instagram, since you can only do that manually, there\u2019s no need to edit your original to fit Instagram\u2019s 10-photo limitation, or 2200 characters caption limit, or 30 hashtags limit, or 20 person-tags limit.\n\nhttps://indieweb.org/multi-photo#How_to_POSSE\n\nOr you can reconsider what if anything you get from syndicating to Twitter or Instagram. \n\nAre people still seeing and interacting with your posts there? Are your friends?\n\nIf & when social media algorithms deprioritize your original posts in favor of showing more ads, you can deprioritize posting to social media.\n\nIf & when your friends quit social media silos^4, you can quit posting copies of your posts to those social media silos.\n\nYou decide what content goes where, when, why, and can change your decisions any time you want.\n\nPOSSEing to social media was always a stopgap. \n\nAs social media silos self-destruct, you can stop syndicating to them.\n\nThanks to Chris Aldrich (https://boffosocko.com/) for the banner image.\n\nThis is day 15 of #100DaysOfIndieWeb #100Days.\n\n\u2190 Day 14: https://tantek.com/2023/014/t4/domain-first-federated-atmention\n\u2192 \ud83d\udd2e\n\n^1 https://indieweb.org/POSSE\n^2 Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach\n^3 https://indieweb.org/multi-photo\n^4 https://indieweb.org/silo-quits",
"html": "When you publish on your #<span class=\"p-category\">IndieWeb</span> site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances.<br /><a href=\"https://indieweb.org/POSSE\"></a>We call this POSSE \u2014 for Publish on your Own Site, then Syndicate Elsewhere.^1<br /><br />By prioritizing your own site, you decide whether (and when) you want to syndicate your posts (or a particular post) to a feed, to a fediverse, to a social media silo or silos, and/or to email like a newsletter.<br /><br />You can make it as simple or as detailed as you want. It\u2019s up to you.<br /><br />Choose deliberately. Change your mind when things change.<br />\u00a0<br />You can opt out of any destination, either by not opting-in, i.e. explicitly not sending your posts to them, or blocking them if necessary.<br /><br />Here are a few of the destination decisions I\u2019ve made, and reasons why.<br /><br />You can delay sending a post to an RSS or Atom feed, say 10 minutes after the time of publication, to give yourself a chance to edit your post, fix typos or links, before a classic feed reader retrieves and perhaps caches your post.<br /><br />You can further delay sending to known uneditable destinations, like Twitter or email, to give yourself even longer to make further edits, corrections, updates, or improvements based on feedback to your original post.<br /><br />Some destination decisions may depend on the type of post.<br /><br />When you post a reply to someone else\u2019s post, in addition to sending a webmention to that other post, it makes sense to also distribute it to where that other post was originally distributed, or a subset thereof, threading your POSSE reply with their original post POSSE copy.<br /><br /><a href=\"https://indieweb.org/reply#POSSE_a_reply\">https://indieweb.org/reply#POSSE_a_reply</a><br /><br />For example, if you reply to someone\u2019s IndieWeb note, and they\u2019ve POSSEd that note to Twitter, you should POSSE your reply to Twitter as well, threading it with their POSSE copy, if you\u2019re still using Twitter that is. If they did not POSSE their original note to Twitter, there may be reasons to POSSE your reply to Twitter anyway, if your reply makes sense there on its own.<br /><br /><a href=\"https://indieweb.org/Twitter#POSSE_Replies_to_Twitter\">https://indieweb.org/Twitter#POSSE_Replies_to_Twitter</a><br /><br />Some destinations have content limitations^2, and you may want to take that into consideration when authoring your content, or not.<br /><br />For example, you may want to more carefully copy-edit the first 256 (for now) characters of a note if you plan to POSSE to Twitter, so that the content that makes it through makes sense as an introduction, or a summary, or a hook, and perhaps has discovery features like hashtags. <br /><br /><a href=\"https://indieweb.org/Twitter#POSSE_Notes_to_Twitter\">https://indieweb.org/Twitter#POSSE_Notes_to_Twitter</a><br /><br />You can use that POSSE tweet text length limitation strategically, placing content after that 256 character cut-off that you may want to edit or expand in an update, or content Twitter may mess-up, like @-domain mentions I described yesterday (day 14).<br /><br />When you publish a multiphoto^3 post, if you\u2019re POSSEing to Twitter, you may want to re-order your photos to choose which four photos show up in your POSSE tweet, e.g. if you happen to be using Bridgy Publish to cross-post your photos to Twitter. You can always re-order your original multiphoto post after POSSEing it. <br /><br />If you\u2019re POSSEing photos to Instagram, since you can only do that manually, there\u2019s no need to edit your original to fit Instagram\u2019s 10-photo limitation, or 2200 characters caption limit, or 30 hashtags limit, or 20 person-tags limit.<br /><br /><a href=\"https://indieweb.org/multi-photo#How_to_POSSE\">https://indieweb.org/multi-photo#How_to_POSSE</a><br /><br />Or you can reconsider what if anything you get from syndicating to Twitter or Instagram. <br /><br />Are people still seeing and interacting with your posts there? Are your friends?<br /><br />If & when social media algorithms deprioritize your original posts in favor of showing more ads, you can deprioritize posting to social media.<br /><br />If & when your friends quit social media silos^4, you can quit posting copies of your posts to those social media silos.<br /><br />You decide what content goes where, when, why, and can change your decisions any time you want.<br /><br />POSSEing to social media was always a stopgap. <br /><br />As social media silos self-destruct, you can stop syndicating to them.<br /><br />Thanks to Chris Aldrich (<a href=\"https://boffosocko.com/\">https://boffosocko.com/</a>) for the banner image.<br /><br />This is day 15 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span>.<br /><br />\u2190 Day 14: <a href=\"https://tantek.com/2023/014/t4/domain-first-federated-atmention\">https://tantek.com/2023/014/t4/domain-first-federated-atmention</a><br />\u2192 \ud83d\udd2e<br /><br />^1 <a href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a><br />^2 Day 5: <a href=\"https://tantek.com/2023/005/t3/indieweb-simpler-approach\">https://tantek.com/2023/005/t3/indieweb-simpler-approach</a><br />^3 <a href=\"https://indieweb.org/multi-photo\">https://indieweb.org/multi-photo</a><br />^4 <a href=\"https://indieweb.org/silo-quits\">https://indieweb.org/silo-quits</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "photo",
"_id": "34444186",
"_source": "2460"
}
When you publish on your #IndieWeb site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances.
indieweb.org/images/6/6a/fi… indieweb.org/POSSE
We call this POSSE — ...
tantek.com/t5Ns1
{
"type": "entry",
"published": "2023-01-16T11:31:25+00:00",
"url": "https://twitter.com/t/status/1614948433999302660",
"content": {
"text": "When you publish on your #IndieWeb site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances.\nindieweb.org/images/6/6a/fi\u2026 indieweb.org/POSSE\nWe call this POSSE \u2014 ...\ntantek.com/t5Ns1",
"html": "When you publish on your <a href=\"https://twitter.com/search?q=%23IndieWeb\">#IndieWeb</a> site, you can decide afterwards where to distribute your content, and when. Figure out how you want to fit into the network of sites & instances.\n<a href=\"https://indieweb.org/images/6/6a/fit-into-the-network.png\">indieweb.org/images/6/6a/fi\u2026</a> <a href=\"https://indieweb.org/POSSE\">indieweb.org/POSSE</a>\nWe call this POSSE \u2014 ...\n<a href=\"https://tantek.com/t5Ns1\">tantek.com/t5Ns1</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": "34443730",
"_source": "2773"
}
Some people are somehow still on Twitter. Why?
{
"type": "entry",
"published": "2023-01-16T08:12:36+00:00",
"url": "https://twitter.com/Johannes_Ernst/status/1614898399714869249",
"content": {
"text": "Some people are somehow still on Twitter. Why?"
},
"author": {
"type": "card",
"name": "Johannes Ernst (@j12t@social.coop)",
"url": "https://twitter.com/Johannes_Ernst",
"photo": "https://pbs.twimg.com/profile_images/1482154224800526337/NjdX1tt7.jpg"
},
"post-type": "note",
"_id": "34441257",
"_source": "2773"
}
Are you getting into the game during eternal Caturday?
{
"type": "entry",
"published": "2023-01-16T00:03:04-0500",
"url": "https://martymcgui.re/2023/01/16/000304/",
"category": [
"Caturday"
],
"video": [
"https://res.cloudinary.com/schmarty/video/upload/vc_h264/mmmgre/b9/2c/bb/51/9876a1b537d56d4aea7a12965228bc7cf4bd74abc3f58f002e2b6754.mov"
],
"content": {
"text": "Are you getting into the game during eternal Caturday?",
"html": "<p>Are you getting into the game during eternal Caturday?</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "video",
"_id": "34439660",
"_source": "175"
}
Russia celebrates genocide as a tourist attraction
Russian magazine The Village with an article about "aesthetics in Mariupol" and a "lookbook" of tourists who take photos against the backdrop of "cool abandoned buildings...
{
"type": "entry",
"published": "2023-01-16T05:09:05+00:00",
"url": "https://twitter.com/jgmac1106/status/1614852214115426305",
"quotation-of": "https://twitter.com/jonnytickle/status/1614768165904388098",
"content": {
"text": "Russia celebrates genocide as a tourist attraction"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/jonnytickle/status/1614768165904388098": {
"type": "entry",
"published": "2023-01-15T23:35:06+00:00",
"url": "https://twitter.com/jonnytickle/status/1614768165904388098",
"photo": [
"https://pbs.twimg.com/media/FmjPE5bXEAA5vIg.jpg"
],
"content": {
"text": "Russian magazine The Village with an article about \"aesthetics in Mariupol\" and a \"lookbook\" of tourists who take photos against the backdrop of \"cool abandoned buildings\"\n\nWhat the fuck? twitter.com/villagemsk/sta\u2026",
"html": "Russian magazine The Village with an article about \"aesthetics in Mariupol\" and a \"lookbook\" of tourists who take photos against the backdrop of \"cool abandoned buildings\"\n\nWhat the fuck? <a href=\"https://twitter.com/villagemsk/status/1614700485520269314\">twitter.com/villagemsk/sta\u2026</a>"
},
"author": {
"type": "card",
"name": "Jonny Tickle",
"url": "https://twitter.com/jonnytickle",
"photo": "https://pbs.twimg.com/profile_images/1125868690912808962/dUIeD8bu.jpg"
},
"post-type": "photo"
}
},
"_id": "34439314",
"_source": "2773"
}
All different fronts with the same end goal of destabilizing the truth and the idea of democratic rule.
Russia knows it can’t win on the battlefield with the West, so is engaging in covert activity to present the message that liberal democracies are failing.
Here we docu...
{
"type": "entry",
"published": "2023-01-16T02:49:32+00:00",
"url": "https://twitter.com/jgmac1106/status/1614817096893960192",
"quotation-of": "https://twitter.com/Heidi_Cuda/status/1614656230982848512",
"content": {
"text": "All different fronts with the same end goal of destabilizing the truth and the idea of democratic rule."
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/Heidi_Cuda/status/1614656230982848512": {
"type": "entry",
"published": "2023-01-15T16:10:18+00:00",
"url": "https://twitter.com/Heidi_Cuda/status/1614656230982848512",
"content": {
"text": "Russia knows it can\u2019t win on the battlefield with the West, so is engaging in covert activity to present the message that liberal democracies are failing.\n\nHere we document their destabilization efforts.-\u2066me and @MattBernardini7\u2069 in \u2066@Byline_Media open.substack.com/pub/bylinesupp\u2026",
"html": "Russia knows it can\u2019t win on the battlefield with the West, so is engaging in covert activity to present the message that liberal democracies are failing.\n\nHere we document their destabilization efforts.-\u2066me and <a href=\"https://twitter.com/MattBernardini7\">@MattBernardini7</a>\u2069 in \u2066<a href=\"https://twitter.com/Byline_Media\">@Byline_Media</a> <a href=\"https://open.substack.com/pub/bylinesupplement/p/the-rolling-insurrection-how-putin?utm_source=direct&r=cfim4&utm_campaign=post&utm_medium=web\">open.substack.com/pub/bylinesupp\u2026</a>"
},
"author": {
"type": "card",
"name": "Heidi Cuda",
"url": "https://twitter.com/Heidi_Cuda",
"photo": "https://pbs.twimg.com/profile_images/1484693697929232387/ui50IANB.jpg"
},
"post-type": "note"
}
},
"_id": "34437949",
"_source": "2773"
}
Craig Hockenberry, writing on his long-lived personal blog:
Well, it happened.
We knew it was coming.
A prick pulled the plug.
Over the weekend, Tweetbot, Twitterrific, and every other popular third-party Twitter client was unceremoniously banned. It’s a stupid petty move on Twitter’s part, executed in an impressively stupid petty way. I imagine it’s the final nail in the coffin for several high-profile Twitter hangers-on.
Most of the people I follow, though? They’re long gone.
{
"type": "entry",
"author": {
"name": null,
"url": "https://davepeck.org/micro/",
"photo": null
},
"url": "https://davepeck.org/2023/01/15/the-shit-show/",
"published": "2023-01-15T15:40:00-08:00",
"content": {
"html": "<p><a href=\"https://mastodon.social/@chockenberry\">Craig Hockenberry</a>, writing on his long-lived <a href=\"https://furbo.org/2023/01/15/the-shit-show/\">personal blog</a>:</p>\n\n<blockquote>\n <p>Well, it happened.</p>\n\n <p>We knew it was coming.</p>\n\n <p>A prick <a href=\"https://9to5google.com/2023/01/12/twitter-api-appears-to-be-down-breaking-tweetbot-and-third-party-clients/\">pulled the plug</a>.</p>\n</blockquote>\n\n<p>Over the weekend, <a href=\"https://tapbots.com/tweetbot/\">Tweetbot</a>, <a href=\"https://twitterrific.com/ios\">Twitterrific</a>, and every other popular third-party Twitter client was <a href=\"https://9to5google.com/2023/01/12/twitter-api-appears-to-be-down-breaking-tweetbot-and-third-party-clients/\">unceremoniously banned</a>. It\u2019s a stupid petty move on Twitter\u2019s part, executed in an impressively stupid petty way. I imagine it\u2019s the final nail in the coffin for several high-profile Twitter hangers-on.</p>\n\n<p>Most of the people I follow, though? They\u2019re long gone.</p>",
"text": "Craig Hockenberry, writing on his long-lived personal blog:\n\n\n Well, it happened.\n\n We knew it was coming.\n\n A prick pulled the plug.\n\n\nOver the weekend, Tweetbot, Twitterrific, and every other popular third-party Twitter client was unceremoniously banned. It\u2019s a stupid petty move on Twitter\u2019s part, executed in an impressively stupid petty way. I imagine it\u2019s the final nail in the coffin for several high-profile Twitter hangers-on.\n\nMost of the people I follow, though? They\u2019re long gone."
},
"post-type": "note",
"_id": "34437062",
"_source": "2781"
}
{
"type": "entry",
"published": "2023-01-15T23:42:35+00:00",
"url": "https://twitter.com/fluffy/status/1614770048073367552",
"content": {
"text": "furries"
},
"author": {
"type": "card",
"name": "@fluffy@plush.city",
"url": "https://twitter.com/fluffy",
"photo": "https://pbs.twimg.com/profile_images/1590630570132123648/POPyLC4l.jpg"
},
"post-type": "note",
"_id": "34435496",
"_source": "2773"
}
This is why #Russia must be stopped in #Ukraine
#Putin is demanding 1/2 the country.
In exchange he will stop bombing the people of #Ukraine
Peace talks with Putin mean death to Ukraine.
The world can not stand for such terror
Two young moms, two neighbours and friends, killed by Russians yesterday in Dnipro. Forever young and beautiful. RIP… #StopRussia #StandWithUkraine
{
"type": "entry",
"published": "2023-01-15T21:45:41+00:00",
"url": "https://twitter.com/jgmac1106/status/1614740629199667212",
"quotation-of": "https://twitter.com/Mariana_Betsa/status/1614630808618426368",
"content": {
"text": "This is why #Russia must be stopped in #Ukraine \n\n#Putin is demanding 1/2 the country. \n\n In exchange he will stop bombing the people of #Ukraine \n\nPeace talks with Putin mean death to Ukraine.\n\nThe world can not stand for such terror",
"html": "This is why <a href=\"https://twitter.com/search?q=%23Russia\">#Russia</a> must be stopped in <a href=\"https://twitter.com/search?q=%23Ukraine\">#Ukraine</a> \n\n<a href=\"https://twitter.com/search?q=%23Putin\">#Putin</a> is demanding 1/2 the country. \n\n In exchange he will stop bombing the people of <a href=\"https://twitter.com/search?q=%23Ukraine\">#Ukraine</a> \n\nPeace talks with Putin mean death to Ukraine.\n\nThe world can not stand for such terror"
},
"author": {
"type": "card",
"name": "jgregorymcverry.com",
"url": "https://twitter.com/jgmac1106",
"photo": "https://pbs.twimg.com/profile_images/1586874242913734658/3GMcjnTC.jpg"
},
"post-type": "note",
"refs": {
"https://twitter.com/Mariana_Betsa/status/1614630808618426368": {
"type": "entry",
"published": "2023-01-15T14:29:17+00:00",
"url": "https://twitter.com/Mariana_Betsa/status/1614630808618426368",
"photo": [
"https://pbs.twimg.com/media/FmhSKUcX0AA9VL5.jpg",
"https://pbs.twimg.com/media/FmhSKVCXgAEk0qA.jpg"
],
"content": {
"text": "Two young moms, two neighbours and friends, killed by Russians yesterday in Dnipro. Forever young and beautiful. RIP\u2026 #StopRussia #StandWithUkraine",
"html": "Two young moms, two neighbours and friends, killed by Russians yesterday in Dnipro. Forever young and beautiful. RIP\u2026 <a href=\"https://twitter.com/search?q=%23StopRussia\">#StopRussia</a> <a href=\"https://twitter.com/search?q=%23StandWithUkraine\">#StandWithUkraine</a>"
},
"author": {
"type": "card",
"name": "Mariana Betsa",
"url": "https://twitter.com/Mariana_Betsa",
"photo": "https://pbs.twimg.com/profile_images/1614330889181200385/Pwgn1cAs.jpg"
},
"post-type": "photo"
}
},
"_id": "34433959",
"_source": "2773"
}
