11 days ago I suggested¹ a unified Sent box of everything sent/reacji’d to all Slacks logged-in with the same email. Beyond Slack though, everything you write & send anywhere: txt, chat, email, web. A Universal Outbox of all content you create, including responses. A flat time ordered list of output across mediums. And a source of material to blog.
The phrase “Universal Outbox” seemed obvious to describe such a feature, parallel to the idea of a universal inbox that I remember first learning of as a concept from Apple’s AOCE project² in the early 1990s, but called a “single universal mailbox”.
Figuring someone must have come up with the idea, I did a web search, and found a minimal wiki page from 2011:
http://webseitz.fluxent.com/wiki/UniversalOutbox
which did vaguely describe the idea:
“a single hub where someone can find all your outbound LifeStreams?”
Except I don’t want “where someone can”, but rather “where I can”, which is an important distinction, because it would explicitly include things you send to a single person or other limited audience.
And yes, “can find”, with full personal search.
Aside: the “where someone can” use-case of the presumably more public “all your outbound LifeStreams” is essentially what an #IndieWeb site is for. One place to publish all you want, any way you want, in a composite stream.
How many times have you texted, IM’d, Slacked, or emailed nearly the same thing, maybe to different people, retyped from memory, that you could have searched, and copy & pasted instead?
Or how many times have you written similar public posts, replies, or emails, on the same topic, where you said the same thing just slightly differently?
What if you could publish such common ideas, concepts, points once, with a permalink, and then cite that permalink rather than retyping the same thing repeatedly?
The idea of a Universal Outbox feels like a logical extension of many IndieWeb practices such as owning your data³.
While all the things you post on your personal site are a part of your Universal Outbox, they are only a subset. Even if you include everything you can PESOS from other sites, that still leaves services and sites without API access, or with APIs you may not have permission to use.
Another approach that may work well is a browser add-on, which would at least be able to collect everything you type into websites. Such an add-on would be more useful than a keylogger, because a browser add-on would have a much better understanding of and access to the context of where you are entering information. An add-on could keep track of permalinks to each statement, e.g. each statement in Slack has a permalink (viewable only with login).
A modest prototype add-on could start with my initial suggestion, a universal sent box that aggregated everything you said across all Slack instances you use in that browser. This would be particularly useful for keeping a personal log of your statements across free Slack instances where everything you say disappears in 90 days.
For now, perhaps the manual-until-it-hurts answer is to periodically check the “Drafts & sent” folder in free Slacks (from the bottom upwards, since Slack’s web UI lacks the ability to sort or reverse the order of your Drafts & sent folder), one instance at a time, blogging or otherwise copy/pasting anything you want to cite, save, or remember.
This is day 31 of #100DaysOfIndieWeb #100Days
← Day 30: https://tantek.com/2023/043/t1/footnotes-unicode-links
→ 🔮
Post Glossary:
composite stream
https://indieweb.org/composite_stream
manual-until-it-hurts
https://indieweb.org/manual_until_it_hurts
permalink
https://indieweb.org/permalink
PESOS
https://indieweb.org/PESOS
reacji
https://indieweb.org/reacji
responses
https://indieweb.org/responses
¹ https://chat.indieweb.org/2023-02-02#t1675370124338700
² https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment
³ https://indieweb.org/own_your_data
{
"type": "entry",
"published": "2023-02-13 22:33-0800",
"url": "http://tantek.com/2023/044/t1/unified-sent-box-universal-outbox",
"category": [
"IndieWeb",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "11 days ago I suggested\u00b9 a unified Sent box of everything sent/reacji\u2019d to all Slacks logged-in with the same email. Beyond Slack though, everything you write & send anywhere: txt, chat, email, web. A Universal Outbox of all content you create, including responses. A flat time ordered list of output across mediums. And a source of material to blog.\n\nThe phrase \u201cUniversal Outbox\u201d seemed obvious to describe such a feature, parallel to the idea of a universal inbox that I remember first learning of as a concept from Apple\u2019s AOCE project\u00b2 in the early 1990s, but called a \u201csingle universal mailbox\u201d.\n\nFiguring someone must have come up with the idea, I did a web search, and found a minimal wiki page from 2011:\n\nhttp://webseitz.fluxent.com/wiki/UniversalOutbox\n\nwhich did vaguely describe the idea: \n\u00a0\u201ca single hub where someone can find all your outbound LifeStreams?\u201d\n\nExcept I don\u2019t want \u201cwhere someone can\u201d, but rather \u201cwhere I can\u201d, which is an important distinction, because it would explicitly include things you send to a single person or other limited audience.\n\nAnd yes, \u201ccan find\u201d, with full personal search.\n\nAside: the \u201cwhere someone can\u201d use-case of the presumably more public \u201call your outbound LifeStreams\u201d is essentially what an #IndieWeb site is for. One place to publish all you want, any way you want, in a composite stream.\n\nHow many times have you texted, IM\u2019d, Slacked, or emailed nearly the same thing, maybe to different people, retyped from memory, that you could have searched, and copy & pasted instead?\n\nOr how many times have you written similar public posts, replies, or emails, on the same topic, where you said the same thing just slightly differently?\n\nWhat if you could publish such common ideas, concepts, points once, with a permalink, and then cite that permalink rather than retyping the same thing repeatedly?\n\nThe idea of a Universal Outbox feels like a logical extension of many IndieWeb practices such as owning your data\u00b3.\n\nWhile all the things you post on your personal site are a part of your Universal Outbox, they are only a subset. Even if you include everything you can PESOS from other sites, that still leaves services and sites without API access, or with APIs you may not have permission to use.\n\nAnother approach that may work well is a browser add-on, which would at least be able to collect everything you type into websites. Such an add-on would be more useful than a keylogger, because a browser add-on would have a much better understanding of and access to the context of where you are entering information. An add-on could keep track of permalinks to each statement, e.g. each statement in Slack has a permalink (viewable only with login).\n\nA modest prototype add-on could start with my initial suggestion, a universal sent box that aggregated everything you said across all Slack instances you use in that browser. This would be particularly useful for keeping a personal log of your statements across free Slack instances where everything you say disappears in 90 days.\n\nFor now, perhaps the manual-until-it-hurts answer is to periodically check the \u201cDrafts & sent\u201d folder in free Slacks (from the bottom upwards, since Slack\u2019s web UI lacks the ability to sort or reverse the order of your Drafts & sent folder), one instance at a time, blogging or otherwise copy/pasting anything you want to cite, save, or remember.\n\n\nThis is day 31 of #100DaysOfIndieWeb #100Days\n\n\u2190 Day 30: https://tantek.com/2023/043/t1/footnotes-unicode-links\n\u2192 \ud83d\udd2e\n\n\nPost Glossary:\n\ncomposite stream\n\u00a0https://indieweb.org/composite_stream\nmanual-until-it-hurts\n\u00a0https://indieweb.org/manual_until_it_hurts\npermalink\n\u00a0https://indieweb.org/permalink\nPESOS\n\u00a0https://indieweb.org/PESOS\nreacji\n\u00a0https://indieweb.org/reacji\nresponses\n\u00a0https://indieweb.org/responses\n\u00a0\n\n\u00b9 https://chat.indieweb.org/2023-02-02#t1675370124338700\n\u00b2 https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment\n\u00b3 https://indieweb.org/own_your_data",
"html": "11 days ago I suggested<a href=\"http://tantek.com/#t5PM1_note-1\">\u00b9</a> a unified Sent box of everything sent/reacji\u2019d to all Slacks logged-in with the same email. Beyond Slack though, everything you write & send anywhere: txt, chat, email, web. A Universal Outbox of all content you create, including responses. A flat time ordered list of output across mediums. And a source of material to blog.<br /><br />The phrase \u201cUniversal Outbox\u201d seemed obvious to describe such a feature, parallel to the idea of a universal inbox that I remember first learning of as a concept from Apple\u2019s AOCE project<a href=\"http://tantek.com/#t5PM1_note-2\">\u00b2</a> in the early 1990s, but called a \u201csingle universal mailbox\u201d.<br /><br />Figuring someone must have come up with the idea, I did a web search, and found a minimal wiki page from 2011:<br /><br /><a href=\"http://webseitz.fluxent.com/wiki/UniversalOutbox\">http://webseitz.fluxent.com/wiki/UniversalOutbox</a><br /><br />which did vaguely describe the idea: <br />\u00a0\u201ca single hub where someone can find all your outbound LifeStreams?\u201d<br /><br />Except I don\u2019t want \u201cwhere someone can\u201d, but rather \u201cwhere I can\u201d, which is an important distinction, because it would explicitly include things you send to a single person or other limited audience.<br /><br />And yes, \u201ccan find\u201d, with full personal search.<br /><br />Aside: the \u201cwhere someone can\u201d use-case of the presumably more public \u201call your outbound LifeStreams\u201d is essentially what an #<span class=\"p-category\">IndieWeb</span> site is for. One place to publish all you want, any way you want, in a composite stream.<br /><br />How many times have you texted, IM\u2019d, Slacked, or emailed nearly the same thing, maybe to different people, retyped from memory, that you could have searched, and copy & pasted instead?<br /><br />Or how many times have you written similar public posts, replies, or emails, on the same topic, where you said the same thing just slightly differently?<br /><br />What if you could publish such common ideas, concepts, points once, with a permalink, and then cite that permalink rather than retyping the same thing repeatedly?<br /><br />The idea of a Universal Outbox feels like a logical extension of many IndieWeb practices such as owning your data<a href=\"http://tantek.com/#t5PM1_note-3\">\u00b3</a>.<br /><br />While all the things you post on your personal site are a part of your Universal Outbox, they are only a subset. Even if you include everything you can PESOS from other sites, that still leaves services and sites without API access, or with APIs you may not have permission to use.<br /><br />Another approach that may work well is a browser add-on, which would at least be able to collect everything you type into websites. Such an add-on would be more useful than a keylogger, because a browser add-on would have a much better understanding of and access to the context of where you are entering information. An add-on could keep track of permalinks to each statement, e.g. each statement in Slack has a permalink (viewable only with login).<br /><br />A modest prototype add-on could start with my initial suggestion, a universal sent box that aggregated everything you said across all Slack instances you use in that browser. This would be particularly useful for keeping a personal log of your statements across free Slack instances where everything you say disappears in 90 days.<br /><br />For now, perhaps the manual-until-it-hurts answer is to periodically check the \u201cDrafts & sent\u201d folder in free Slacks (from the bottom upwards, since Slack\u2019s web UI lacks the ability to sort or reverse the order of your Drafts & sent folder), one instance at a time, blogging or otherwise copy/pasting anything you want to cite, save, or remember.<br /><br /><br />This is day 31 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span><br /><br />\u2190 Day 30: <a href=\"https://tantek.com/2023/043/t1/footnotes-unicode-links\">https://tantek.com/2023/043/t1/footnotes-unicode-links</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Post Glossary:<br /><br />composite stream<br />\u00a0<a href=\"https://indieweb.org/composite_stream\">https://indieweb.org/composite_stream</a><br />manual-until-it-hurts<br />\u00a0<a href=\"https://indieweb.org/manual_until_it_hurts\">https://indieweb.org/manual_until_it_hurts</a><br />permalink<br />\u00a0<a href=\"https://indieweb.org/permalink\">https://indieweb.org/permalink</a><br />PESOS<br />\u00a0<a href=\"https://indieweb.org/PESOS\">https://indieweb.org/PESOS</a><br />reacji<br />\u00a0<a href=\"https://indieweb.org/reacji\">https://indieweb.org/reacji</a><br />responses<br />\u00a0<a href=\"https://indieweb.org/responses\">https://indieweb.org/responses</a><br />\u00a0<br /><br /><a href=\"http://tantek.com/#t5PM1_ref-1\">\u00b9</a> <a href=\"https://chat.indieweb.org/2023-02-02#t1675370124338700\">https://chat.indieweb.org/2023-02-02#t1675370124338700</a><br /><a href=\"http://tantek.com/#t5PM1_ref-2\">\u00b2</a> <a href=\"https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment\">https://en.wikipedia.org/wiki/Apple_Open_Collaboration_Environment</a><br /><a href=\"http://tantek.com/#t5PM1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/own_your_data\">https://indieweb.org/own_your_data</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "35156884",
"_source": "1",
"_is_read": false
}
@box464 There's where the #IndieWeb needs to eventually meet #Dotnet. Don't worry. I'm learning the C# language for that reason.
{
"type": "entry",
"author": {
"name": "@katmmoss",
"url": "https://social.faebornnetworks.org/@katmmoss",
"photo": null
},
"url": "https://social.faebornnetworks.org/@katmmoss/109866536635474403",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@box464\">@<span>box464</span></a></span> There's where the <a href=\"https://social.faebornnetworks.org/tags/IndieWeb\">#<span>IndieWeb</span></a> needs to eventually meet <a href=\"https://social.faebornnetworks.org/tags/Dotnet\">#<span>Dotnet</span></a>. Don't worry. I'm learning the C# language for that reason.</p>",
"text": "@box464 There's where the #IndieWeb needs to eventually meet #Dotnet. Don't worry. I'm learning the C# language for that reason."
},
"published": "2023-02-15T03:05:07+00:00",
"post-type": "note",
"_id": "35156506",
"_source": "7235",
"_is_read": false
}
Psst. Hey you, remember that blog of yours? I looked at it. You last updated it in 2018 or maybe 2015. I dunno. it's been a while.
Things have changed since then…
We’re (re)building the Open Web.
Join us.
Publish a blog post.
Don’t post things on Twitter, Facebook, or Instagram.
Fuck that corporate shit and write it in your own home!
#mastodon #fediverse #indieWeb #rss #open
{
"type": "entry",
"author": {
"name": "@rasterweb",
"url": "https://mastodon.social/@rasterweb",
"photo": null
},
"url": "https://mastodon.social/@rasterweb/109866254221865437",
"content": {
"html": "<p>Psst. Hey you, remember that blog of yours? I looked at it. You last updated it in 2018 or maybe 2015. I dunno. it's been a while.</p><p>Things have changed since then\u2026</p><p>We\u2019re (re)building the Open Web. </p><p>Join us.</p><p>Publish a blog post. </p><p>Don\u2019t post things on Twitter, Facebook, or Instagram.</p><p>Fuck that corporate shit and write it in your own home!</p><p><a href=\"https://mastodon.social/tags/mastodon\">#<span>mastodon</span></a> <a href=\"https://mastodon.social/tags/fediverse\">#<span>fediverse</span></a> <a href=\"https://mastodon.social/tags/indieWeb\">#<span>indieWeb</span></a> <a href=\"https://mastodon.social/tags/rss\">#<span>rss</span></a> <a href=\"https://mastodon.social/tags/open\">#<span>open</span></a></p>",
"text": "Psst. Hey you, remember that blog of yours? I looked at it. You last updated it in 2018 or maybe 2015. I dunno. it's been a while.Things have changed since then\u2026We\u2019re (re)building the Open Web. Join us.Publish a blog post. Don\u2019t post things on Twitter, Facebook, or Instagram.Fuck that corporate shit and write it in your own home!#mastodon #fediverse #indieWeb #rss #open"
},
"published": "2023-02-15T01:53:18+00:00",
"post-type": "note",
"_id": "35155854",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "@syam",
"url": "https://aana.site/@syam",
"photo": null
},
"url": "https://aana.site/@syam/109864842105208919",
"content": {
"html": "<p>Finally! I discovered a simple <a href=\"https://aana.site/tags/indieweb\">#<span>indieweb</span></a> CMS! That too in <a href=\"https://aana.site/tags/PHP\">#<span>PHP</span></a> </p><p><a href=\"https://github.com/neopublished/neopub\"><span>https://</span><span>github.com/neopublished/neopub</span><span></span></a></p>",
"text": "Finally! I discovered a simple #indieweb CMS! That too in #PHP https://github.com/neopublished/neopub"
},
"published": "2023-02-14T19:54:11+00:00",
"post-type": "note",
"_id": "35149072",
"_source": "7235",
"_is_read": false
}
~ #webrings watch ~
Posting a new way to connect with the indie web every day!
Day #12: Cuddler Webring
https://cuddler-webring.netlify.app/
#happyvalentinesday 💞 mincerafter42 has the perfect #webring for YOU! If you love cuddles, sign up! Show it some #love
#indieweb #website #yesterweb #web #webdev #smallweb #valentinesday #valentines
{
"type": "entry",
"author": {
"name": "@accordionpolar",
"url": "https://indieweb.social/@accordionpolar",
"photo": null
},
"url": "https://indieweb.social/@accordionpolar/109864300568053717",
"content": {
"html": "<p>~ <a href=\"https://indieweb.social/tags/webrings\">#<span>webrings</span></a> watch ~<br />Posting a new way to connect with the indie web every day!</p><p>Day #12: Cuddler Webring <br /><a href=\"https://cuddler-webring.netlify.app/\"><span>https://</span><span>cuddler-webring.netlify.app/</span><span></span></a></p><p><a href=\"https://indieweb.social/tags/happyvalentinesday\">#<span>happyvalentinesday</span></a> \ud83d\udc9e mincerafter42 has the perfect <a href=\"https://indieweb.social/tags/webring\">#<span>webring</span></a> for YOU! If you love cuddles, sign up! Show it some <a href=\"https://indieweb.social/tags/love\">#<span>love</span></a> </p><p><a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://indieweb.social/tags/website\">#<span>website</span></a> <a href=\"https://indieweb.social/tags/yesterweb\">#<span>yesterweb</span></a> <a href=\"https://indieweb.social/tags/web\">#<span>web</span></a> <a href=\"https://indieweb.social/tags/webdev\">#<span>webdev</span></a> <a href=\"https://indieweb.social/tags/smallweb\">#<span>smallweb</span></a> <a href=\"https://indieweb.social/tags/valentinesday\">#<span>valentinesday</span></a> <a href=\"https://indieweb.social/tags/valentines\">#<span>valentines</span></a></p>",
"text": "~ #webrings watch ~\nPosting a new way to connect with the indie web every day!Day #12: Cuddler Webring \nhttps://cuddler-webring.netlify.app/#happyvalentinesday \ud83d\udc9e mincerafter42 has the perfect #webring for YOU! If you love cuddles, sign up! Show it some #love #indieweb #website #yesterweb #web #webdev #smallweb #valentinesday #valentines"
},
"published": "2023-02-14T17:36:27+00:00",
"post-type": "note",
"_id": "35146662",
"_source": "7235",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "iamjaco",
"url": "https://iamja.co",
"photo": "https://www.gravatar.com/avatar/5e1905f7be027b59639edf49b72bd5ec?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://www.iamja.co/2023/02/14/discover-the-indieweb.html",
"content": {
"html": "<p><a href=\"https://indieblog.page/\">Discover the IndieWeb, one blog post at a time.</a></p>",
"text": "Discover the IndieWeb, one blog post at a time."
},
"published": "2023-02-14T12:25:40+00:00",
"post-type": "note",
"_id": "35143120",
"_source": "7224",
"_is_read": false
}
Our smarter, richer betters (in Babel times, the king’s name was Nimrod) often preach the idea of a town square, a marketplace of ideas, a centralized hub of discourse and entertainment—and we listen. But when I go back and read Genesis, I hear God saying: “My children, I designed your brains to scale to 150 stable relationships. Anything beyond that is overclocking. You should all try Mastodon.”
So many gems in this piece by Paul Ford:
The Fediverse apps are all built on a set of rules called the ActivityPub standard, which is a little like HTML had sex with a calendar invite. It’s a content polycule. The questions it evokes are the same as with any polycule: What are the rules? How big can this get? Who will create the chore chart?
{
"type": "entry",
"published": "2023-02-14T08:07:28Z",
"url": "https://adactio.com/links/19900",
"category": [
"mastodon",
"twitter",
"fediverse",
"portable",
"social",
"networks",
"portability",
"babel",
"genesis",
"bible"
],
"bookmark-of": [
"https://www.wired.com/story/god-did-us-a-favor-by-destroying-twitter/"
],
"content": {
"text": "God Did the World a Favor by Destroying Twitter | WIRED\n\n\n\n\n Our smarter, richer betters (in Babel times, the king\u2019s name was Nimrod) often preach the idea of a town square, a marketplace of ideas, a centralized hub of discourse and entertainment\u2014and we listen. But when I go back and read Genesis, I hear God saying: \u201cMy children, I designed your brains to scale to 150 stable relationships. Anything beyond that is overclocking. You should all try Mastodon.\u201d\n\n\nSo many gems in this piece by Paul Ford:\n\n\n The Fediverse apps are all built on a set of rules called the ActivityPub standard, which is a little like HTML had sex with a calendar invite. It\u2019s a content polycule. The questions it evokes are the same as with any polycule: What are the rules? How big can this get? Who will create the chore chart?",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://www.wired.com/story/god-did-us-a-favor-by-destroying-twitter/\">\nGod Did the World a Favor by Destroying Twitter | WIRED\n</a>\n</h3>\n\n<blockquote>\n <p>Our smarter, richer betters (in Babel times, the king\u2019s name was Nimrod) often preach the idea of a town square, a marketplace of ideas, a centralized hub of discourse and entertainment\u2014and we listen. But when I go back and read Genesis, I hear God saying: \u201cMy children, I designed your brains to scale to 150 stable relationships. Anything beyond that is overclocking. You should all try Mastodon.\u201d</p>\n</blockquote>\n\n<p>So many gems in this piece by Paul Ford:</p>\n\n<blockquote>\n <p>The Fediverse apps are all built on a set of rules called the ActivityPub standard, which is a little like HTML had sex with a calendar invite. It\u2019s a content polycule. The questions it evokes are the same as with any polycule: What are the rules? How big can this get? Who will create the chore chart?</p>\n</blockquote>"
},
"author": {
"type": "card",
"name": "Jeremy Keith",
"url": "https://adactio.com/",
"photo": "https://adactio.com/images/photo-150.jpg"
},
"post-type": "bookmark",
"_id": "35136104",
"_source": "2",
"_is_read": false
}
@starrwulfe
I feel especially called out on the #indieweb one. I'm on my 3rd prototype architecture in as many months trying to find a decent blog home. 😿
{
"type": "entry",
"author": {
"name": "@jlgatewood",
"url": "https://mastodon.cloud/@jlgatewood",
"photo": null
},
"url": "https://mastodon.cloud/@jlgatewood/109861536686030771",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://starrwulfe.xyz\">@<span>starrwulfe</span></a></span><br />I feel especially called out on the <a href=\"https://mastodon.cloud/tags/indieweb\">#<span>indieweb</span></a> one. I'm on my 3rd prototype architecture in as many months trying to find a decent blog home. \ud83d\ude3f</p>",
"text": "@starrwulfe\nI feel especially called out on the #indieweb one. I'm on my 3rd prototype architecture in as many months trying to find a decent blog home. \ud83d\ude3f"
},
"published": "2023-02-14T05:53:34+00:00",
"post-type": "note",
"_id": "35131752",
"_source": "7235",
"_is_read": false
}
This Saturday night is RetroStrange Movie Night! Watch some 1950s Hot Rod movies w/ us. No ads, no sign-in, no bullshit. RSMN is community-supported by our Patreon. https://retrostrange.com/2023/retrostrange-movie-night-is-february-18th/ #Movies #Streaming #IndieWeb
{
"type": "entry",
"author": {
"name": "@phil",
"url": "https://wrestling.social/@phil",
"photo": null
},
"url": "https://wrestling.social/@phil/109859033015652939",
"content": {
"html": "<p>This Saturday night is RetroStrange Movie Night! Watch some 1950s Hot Rod movies w/ us. No ads, no sign-in, no bullshit. RSMN is community-supported by our Patreon. <a href=\"https://retrostrange.com/2023/retrostrange-movie-night-is-february-18th/\"><span>https://</span><span>retrostrange.com/2023/retrostr</span><span>ange-movie-night-is-february-18th/</span></a> <a href=\"https://wrestling.social/tags/Movies\">#<span>Movies</span></a> <a href=\"https://wrestling.social/tags/Streaming\">#<span>Streaming</span></a> <a href=\"https://wrestling.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
"text": "This Saturday night is RetroStrange Movie Night! Watch some 1950s Hot Rod movies w/ us. No ads, no sign-in, no bullshit. RSMN is community-supported by our Patreon. https://retrostrange.com/2023/retrostrange-movie-night-is-february-18th/ #Movies #Streaming #IndieWeb"
},
"published": "2023-02-13T19:16:51+00:00",
"post-type": "note",
"_id": "35120645",
"_source": "7235",
"_is_read": false
}
@paulrobertlloyd @chrisbergr This project feels like a LEAP in the right direction. I admit this has been a struggle to complete - it's almost like taking a course! IndieWebifyMe and Webmentions.Rock are great but your average user has no chance with that.
I envision something like an app or application that acts as the #IndieWeb admin console, storing content locally, and then pushing it up to required services **magically** 🧙.
Making it simple and fun like https://home.omg.lol/
{
"type": "entry",
"author": {
"name": "@box464",
"url": "https://mastodon.social/@box464",
"photo": null
},
"url": "https://mastodon.social/@box464/109858670032649339",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@paulrobertlloyd\">@<span>paulrobertlloyd</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@chrisbergr\">@<span>chrisbergr</span></a></span> This project feels like a LEAP in the right direction. I admit this has been a struggle to complete - it's almost like taking a course! IndieWebifyMe and Webmentions.Rock are great but your average user has no chance with that.</p><p>I envision something like an app or application that acts as the <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> admin console, storing content locally, and then pushing it up to required services **magically** \ud83e\uddd9.</p><p>Making it simple and fun like <a href=\"https://home.omg.lol/\"><span>https://</span><span>home.omg.lol/</span><span></span></a></p>",
"text": "@paulrobertlloyd @chrisbergr This project feels like a LEAP in the right direction. I admit this has been a struggle to complete - it's almost like taking a course! IndieWebifyMe and Webmentions.Rock are great but your average user has no chance with that.I envision something like an app or application that acts as the #IndieWeb admin console, storing content locally, and then pushing it up to required services **magically** \ud83e\uddd9.Making it simple and fun like https://home.omg.lol/"
},
"published": "2023-02-13T17:44:32+00:00",
"post-type": "note",
"_id": "35118520",
"_source": "7235",
"_is_read": false
}
Working on a new #Gutenberg block for #IndieWeb-style reply contexts (https://indieweb.org/reply-context#How_to).
It’ll work much like IndieBlocks’ Context block, except that it’ll leverage InnerBlocks. No more messing with Groups and `e-content` class names in just the right places.
And because I want to make these things editable as can be, it’ll support a “transform,” not just to raw “Custom HTML,” but to a Group block (of which the first child is a Custom HTML block with just the introducory HTML).
{
"type": "entry",
"author": {
"name": "@janboddez",
"url": "https://indieweb.social/@janboddez",
"photo": null
},
"url": "https://indieweb.social/@janboddez/109858614536237776",
"content": {
"html": "<p>Working on a new <a href=\"https://indieweb.social/tags/Gutenberg\">#<span>Gutenberg</span></a> block for <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a>-style reply contexts (<a href=\"https://indieweb.org/reply-context#How_to\"><span>https://</span><span>indieweb.org/reply-context#How</span><span>_to</span></a>).</p><p>It\u2019ll work much like IndieBlocks\u2019 Context block, except that it\u2019ll leverage InnerBlocks. No more messing with Groups and `e-content` class names in just the right places.</p><p>And because I want to make these things editable as can be, it\u2019ll support a \u201ctransform,\u201d not just to raw \u201cCustom HTML,\u201d but to a Group block (of which the first child is a Custom HTML block with just the introducory HTML).</p>",
"text": "Working on a new #Gutenberg block for #IndieWeb-style reply contexts (https://indieweb.org/reply-context#How_to).It\u2019ll work much like IndieBlocks\u2019 Context block, except that it\u2019ll leverage InnerBlocks. No more messing with Groups and `e-content` class names in just the right places.And because I want to make these things editable as can be, it\u2019ll support a \u201ctransform,\u201d not just to raw \u201cCustom HTML,\u201d but to a Group block (of which the first child is a Custom HTML block with just the introducory HTML)."
},
"published": "2023-02-13T17:30:25+00:00",
"post-type": "note",
"_id": "35118112",
"_source": "7235",
"_is_read": false
}
I got auto-Unicode & linking footnotes¹ working!
In notes like this post, I can type "^1" (like after the word "footnotes" above) and the code on my server automatically:
* turns it into a Unicode superscript '¹'
* links it to the expansion at the end of my post
Similarly, I can type "^1" at the start of an expansion line (e.g. at the end of a post) and that code automatically:
* turns it into a Unicode superscript '¹'
* links it back to the inline reference
Since that code is part of my site’s CASSIS auto_link function², all previous posts with such "^n" style footnotes have also been updated, like my day 6 post³ and since.
Clicking an inline footnote reference scrolls to the line with the footnote expansion. Clicking the Unicode superscript number at the start of that expansion scrolls back to the inline footnote reference.
I decided to postpone adding the small return arrows '⮐' at the end of a footnote expansions. Linking the superscript numbers to each other works well, and seemed sufficiently discoverable without being distracting.
By using post-specific unique prefixes for the footnote reference & expansion links, those links also work even in the presence of more than one post with footnotes, e.g. on my home page⁴. They’re also in my Atom feed entries. I’m curious how the footnotes links in a post work in other contexts, like when viewing in a reader.
I also discovered that Unicode superscripts were inconsistent on some platforms, and added a bit of CSS to set an explicit font-family for footnotes numbers:
/* CSS style rule to use a specific font for footnote refs and expansions */
a[id*='_ref-'],a[id*='_note-'] { font-family:"Arial Unicode MS",system-ui; }
/* end of style rule */
I added this and some other tips to the #IndieWeb footnote page⁵.
This is day 30 of #100DaysOfIndieWeb #100Days
← Day 29: https://tantek.com/2023/037/t1/post-glossary
→ 🔮
¹ https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink
² https://tantek.com/cassis.js
³ https://tantek.com/2023/006/t1/forward-in-time-links
⁴ https://tantek.com/
⁵ https://indieweb.org/footnote
{
"type": "entry",
"published": "2023-02-12 20:06-0800",
"url": "http://tantek.com/2023/043/t1/footnotes-unicode-links",
"category": [
"IndieWeb",
"100DaysOfIndieWeb",
"100Days"
],
"content": {
"text": "I got auto-Unicode & linking footnotes\u00b9 working!\n\nIn notes like this post, I can type \"^1\" (like after the word \"footnotes\" above) and the code on my server automatically:\n* turns it into a Unicode superscript '\u00b9'\n* links it to the expansion at the end of my post\nSimilarly, I can type \"^1\" at the start of an expansion line (e.g. at the end of a post) and that code automatically:\n* turns it into a Unicode superscript '\u00b9'\n* links it back to the inline reference\n\nSince that code is part of my site\u2019s CASSIS auto_link function\u00b2, all previous posts with such \"^n\" style footnotes have also been updated, like my day 6 post\u00b3 and since.\n\nClicking an inline footnote reference scrolls to the line with the footnote expansion. Clicking the Unicode superscript number at the start of that expansion scrolls back to the inline footnote reference. \n\nI decided to postpone adding the small return arrows '\u2b90' at the end of a footnote expansions. Linking the superscript numbers to each other works well, and seemed sufficiently discoverable without being distracting.\n\nBy using post-specific unique prefixes for the footnote reference & expansion links, those links also work even in the presence of more than one post with footnotes, e.g. on my home page\u2074. They\u2019re also in my Atom feed entries. I\u2019m curious how the footnotes links in a post work in other contexts, like when viewing in a reader.\n\nI also discovered that Unicode superscripts were inconsistent on some platforms, and added a bit of CSS to set an explicit font-family for footnotes numbers:\n\n/* CSS style rule to use a specific font for footnote refs and expansions */\na[id*='_ref-'],a[id*='_note-'] { font-family:\"Arial Unicode MS\",system-ui; }\n/* end of style rule */\n\nI added this and some other tips to the #IndieWeb footnote page\u2075.\n\n\nThis is day 30 of #100DaysOfIndieWeb #100Days\n\n\u2190 Day 29: https://tantek.com/2023/037/t1/post-glossary\n\u2192 \ud83d\udd2e\n\n\n\u00b9 https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink\n\u00b2 https://tantek.com/cassis.js\n\u00b3 https://tantek.com/2023/006/t1/forward-in-time-links\n\u2074 https://tantek.com/\n\u2075 https://indieweb.org/footnote",
"html": "I got auto-Unicode & linking footnotes<a href=\"http://tantek.com/#t5PL1_note-1\">\u00b9</a> working!<br /><br />In notes like this post, I can type \"^1\" (like after the word \"footnotes\" above) and the code on my server automatically:<br />* turns it into a Unicode superscript '\u00b9'<br />* links it to the expansion at the end of my post<br />Similarly, I can type \"^1\" at the start of an expansion line (e.g. at the end of a post) and that code automatically:<br />* turns it into a Unicode superscript '\u00b9'<br />* links it back to the inline reference<br /><br />Since that code is part of my site\u2019s CASSIS auto_link function<a href=\"http://tantek.com/#t5PL1_note-2\">\u00b2</a>, all previous posts with such \"^n\" style footnotes have also been updated, like my day 6 post<a href=\"http://tantek.com/#t5PL1_note-3\">\u00b3</a> and since.<br /><br />Clicking an inline footnote reference scrolls to the line with the footnote expansion. Clicking the Unicode superscript number at the start of that expansion scrolls back to the inline footnote reference. <br /><br />I decided to postpone adding the small return arrows '\u2b90' at the end of a footnote expansions. Linking the superscript numbers to each other works well, and seemed sufficiently discoverable without being distracting.<br /><br />By using post-specific unique prefixes for the footnote reference & expansion links, those links also work even in the presence of more than one post with footnotes, e.g. on my home page<a href=\"http://tantek.com/#t5PL1_note-4\">\u2074</a>. They\u2019re also in my Atom feed entries. I\u2019m curious how the footnotes links in a post work in other contexts, like when viewing in a reader.<br /><br />I also discovered that Unicode superscripts were inconsistent on some platforms, and added a bit of CSS to set an explicit font-family for footnotes numbers:<br /><br />/* CSS style rule to use a specific font for footnote refs and expansions */<br />a[id*='_ref-'],a[id*='_note-'] { font-family:\"Arial Unicode MS\",system-ui; }<br />/* end of style rule */<br /><br />I added this and some other tips to the #<span class=\"p-category\">IndieWeb</span> footnote page<a href=\"http://tantek.com/#t5PL1_note-5\">\u2075</a>.<br /><br /><br />This is day 30 of #<span class=\"p-category\">100DaysOfIndieWeb</span> #<span class=\"p-category\">100Days</span><br /><br />\u2190 Day 29: <a href=\"https://tantek.com/2023/037/t1/post-glossary\">https://tantek.com/2023/037/t1/post-glossary</a><br />\u2192 \ud83d\udd2e<br /><br /><br /><a href=\"http://tantek.com/#t5PL1_ref-1\">\u00b9</a> <a href=\"https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink\">https://tantek.com/2023/036/t1/footnotes-unicode-hyperlink</a><br /><a href=\"http://tantek.com/#t5PL1_ref-2\">\u00b2</a> <a href=\"https://tantek.com/cassis.js\">https://tantek.com/cassis.js</a><br /><a href=\"http://tantek.com/#t5PL1_ref-3\">\u00b3</a> <a href=\"https://tantek.com/2023/006/t1/forward-in-time-links\">https://tantek.com/2023/006/t1/forward-in-time-links</a><br /><a href=\"http://tantek.com/#t5PL1_ref-4\">\u2074</a> <a href=\"https://tantek.com/\">https://tantek.com/</a><br /><a href=\"http://tantek.com/#t5PL1_ref-5\">\u2075</a> <a href=\"https://indieweb.org/footnote\">https://indieweb.org/footnote</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "http://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "35114903",
"_source": "1",
"_is_read": false
}
@box464 Interesting project.
But it says "Indiekit is for everyone" and the first step of the installation process is "npm..."
Unfortunately, still not the access to the #Indieweb for the non-expert.
{
"type": "entry",
"author": {
"name": "@chrisbergr",
"url": "https://mastodon.social/@chrisbergr",
"photo": null
},
"url": "https://mastodon.social/@chrisbergr/109857934629962899",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.social/@box464\">@<span>box464</span></a></span> Interesting project.<br />But it says \"Indiekit is for everyone\" and the first step of the installation process is \"npm...\"<br />Unfortunately, still not the access to the <a href=\"https://mastodon.social/tags/Indieweb\">#<span>Indieweb</span></a> for the non-expert.</p>",
"text": "@box464 Interesting project.\nBut it says \"Indiekit is for everyone\" and the first step of the installation process is \"npm...\"\nUnfortunately, still not the access to the #Indieweb for the non-expert."
},
"published": "2023-02-13T14:37:31+00:00",
"post-type": "note",
"_id": "35114023",
"_source": "7235",
"_is_read": false
}
There are just too many sparklies to learn in the #IndieWeb #Fediverse world. Stop creating interesting things!
https://getindiekit.com/get-started
{
"type": "entry",
"author": {
"name": "@box464",
"url": "https://mastodon.social/@box464",
"photo": null
},
"url": "https://mastodon.social/@box464/109857750344066119",
"content": {
"html": "<p>There are just too many sparklies to learn in the <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://mastodon.social/tags/Fediverse\">#<span>Fediverse</span></a> world. Stop creating interesting things!</p><p><a href=\"https://getindiekit.com/get-started\"><span>https://</span><span>getindiekit.com/get-started</span><span></span></a></p>",
"text": "There are just too many sparklies to learn in the #IndieWeb #Fediverse world. Stop creating interesting things!https://getindiekit.com/get-started"
},
"published": "2023-02-13T13:50:39+00:00",
"post-type": "note",
"_id": "35114024",
"_source": "7235",
"_is_read": false
}
This is my current #indieweb project: an application to design weaving designs for use in a floor loom. It uses #svelte and #webgl.
Lately there has been a lot of debate around React, SPA vs. MPA, but with Svelte I've managed to only 50kb of Javascript.
{
"type": "entry",
"author": {
"name": "@jrende",
"url": "https://indieweb.social/@jrende",
"photo": null
},
"url": "https://indieweb.social/@jrende/109857863231636357",
"content": {
"html": "<p>This is my current <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> project: an application to design weaving designs for use in a floor loom. It uses <a href=\"https://indieweb.social/tags/svelte\">#<span>svelte</span></a> and <a href=\"https://indieweb.social/tags/webgl\">#<span>webgl</span></a>. <br />Lately there has been a lot of debate around React, SPA vs. MPA, but with Svelte I've managed to only 50kb of Javascript.</p>",
"text": "This is my current #indieweb project: an application to design weaving designs for use in a floor loom. It uses #svelte and #webgl. \nLately there has been a lot of debate around React, SPA vs. MPA, but with Svelte I've managed to only 50kb of Javascript."
},
"published": "2023-02-13T14:19:21+00:00",
"post-type": "note",
"_id": "35114025",
"_source": "7235",
"_is_read": false
}
Screenshot of my personal site in development. Webmentions, tweets, and mastodon interactions are finally showing after a good month of banging my head against a wall.
{
"type": "entry",
"author": {
"name": "@box464",
"url": "https://mastodon.social/@box464",
"photo": null
},
"url": "https://mastodon.social/@box464/109856049499738607",
"content": {
"html": "Screenshot of my personal site in development. Webmentions, tweets, and mastodon interactions are finally showing after a good month of banging my head against a wall.",
"text": "Screenshot of my personal site in development. Webmentions, tweets, and mastodon interactions are finally showing after a good month of banging my head against a wall."
},
"published": "2023-02-13T06:38:06+00:00",
"post-type": "note",
"_id": "35106492",
"_source": "7235",
"_is_read": false
}
#Blog updated: The second part of my #gamedev work experience at Keywords Studios, and how getting fired from there was lowkey the best thing that ever happened for my career.
https://chaotic-neutr.al/posts/keywords-studios-storytime-2/
#IndieWeb
{
"type": "entry",
"author": {
"name": "@christroll",
"url": "https://peoplemaking.games/@christroll",
"photo": null
},
"url": "https://peoplemaking.games/@christroll/109853679963092066",
"content": {
"html": "<p><a href=\"https://peoplemaking.games/tags/Blog\">#<span>Blog</span></a> updated: The second part of my <a href=\"https://peoplemaking.games/tags/gamedev\">#<span>gamedev</span></a> work experience at Keywords Studios, and how getting fired from there was lowkey the best thing that ever happened for my career.</p><p><a href=\"https://chaotic-neutr.al/posts/keywords-studios-storytime-2/\"><span>https://</span><span>chaotic-neutr.al/posts/keyword</span><span>s-studios-storytime-2/</span></a></p><p><a href=\"https://peoplemaking.games/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
"text": "#Blog updated: The second part of my #gamedev work experience at Keywords Studios, and how getting fired from there was lowkey the best thing that ever happened for my career.https://chaotic-neutr.al/posts/keywords-studios-storytime-2/#IndieWeb"
},
"published": "2023-02-12T20:35:30+00:00",
"post-type": "note",
"_id": "35097662",
"_source": "7235",
"_is_read": false
}
I created some Shortcuts for #Micropub posting on iOS. Supports Like, Bookmark, Reply, Repost, Note, and Note with Image. #indieweb https://cagrimmett.com/development/2023/02/12/ios-shortcut-actions-for-micropub-posting/
{
"type": "entry",
"author": {
"name": "@cagrimmett",
"url": "https://toot.cafe/@cagrimmett",
"photo": null
},
"url": "https://toot.cafe/@cagrimmett/109853579599038404",
"content": {
"html": "<p>I created some Shortcuts for <a href=\"https://toot.cafe/tags/Micropub\">#<span>Micropub</span></a> posting on iOS. Supports Like, Bookmark, Reply, Repost, Note, and Note with Image. <a href=\"https://toot.cafe/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://cagrimmett.com/development/2023/02/12/ios-shortcut-actions-for-micropub-posting/\"><span>https://</span><span>cagrimmett.com/development/202</span><span>3/02/12/ios-shortcut-actions-for-micropub-posting/</span></a></p>",
"text": "I created some Shortcuts for #Micropub posting on iOS. Supports Like, Bookmark, Reply, Repost, Note, and Note with Image. #indieweb https://cagrimmett.com/development/2023/02/12/ios-shortcut-actions-for-micropub-posting/"
},
"published": "2023-02-12T20:09:58+00:00",
"post-type": "note",
"_id": "35097121",
"_source": "7235",
"_is_read": false
}
Morning everybody and welcome to Sunday. Phone is still playing dead. Going to try to get some sighted help to help with this, hopefully someone moderately tech-oriented.
Also on: indieweb Micro.blog
{
"type": "entry",
"author": {
"name": "Amanda Carson",
"url": "https://arush.io",
"photo": "https://www.gravatar.com/avatar/94ae98c7302aa5b10f1d9a4255cf83ba?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://arush.io/2023/02/12/248606/",
"content": {
"html": "<p>Morning everybody and welcome to Sunday. Phone is still playing dead. Going to try to get some sighted help to help with this, hopefully someone moderately tech-oriented.</p>\n<span>Also on:</span><p><span><a class=\"u-syndication\" href=\"https://indieweb.social/@arush/109852446432855614\"> indieweb</a></span><span><a class=\"u-syndication\" href=\"https://micro.blog/arush/16948464\"> Micro.blog</a></span></p>",
"text": "Morning everybody and welcome to Sunday. Phone is still playing dead. Going to try to get some sighted help to help with this, hopefully someone moderately tech-oriented.\nAlso on: indieweb Micro.blog"
},
"published": "2023-02-12T15:21:48+00:00",
"post-type": "note",
"_id": "35095521",
"_source": "7224",
"_is_read": false
}
Hmm… webmention.app appears to be no more and I get an error whenever the Netlify webmention plugin runs. I gueess I could use curl manually, but what a PITA.
🏷 #Indieweb #Netlify #Webmentions
https://www.thisdaysportion.com/notes/sending-webmentions-is-hard
{
"type": "entry",
"author": {
"name": "@leonp",
"url": "https://fosstodon.org/@leonp",
"photo": null
},
"url": "https://fosstodon.org/@leonp/109853239726227719",
"content": {
"html": "<p>Hmm\u2026 webmention.app appears to be no more and I get an error whenever the Netlify webmention plugin runs. I gueess I could use curl manually, but what a PITA.</p><p> <br /><br /> \ud83c\udff7 <a href=\"https://fosstodon.org/tags/Indieweb\">#<span>Indieweb</span></a> <a href=\"https://fosstodon.org/tags/Netlify\">#<span>Netlify</span></a> <a href=\"https://fosstodon.org/tags/Webmentions\">#<span>Webmentions</span></a><br /><a href=\"https://www.thisdaysportion.com/notes/sending-webmentions-is-hard\"><span>https://www.</span><span>thisdaysportion.com/notes/send</span><span>ing-webmentions-is-hard</span></a></p>",
"text": "Hmm\u2026 webmention.app appears to be no more and I get an error whenever the Netlify webmention plugin runs. I gueess I could use curl manually, but what a PITA. \n\n \ud83c\udff7 #Indieweb #Netlify #Webmentions\nhttps://www.thisdaysportion.com/notes/sending-webmentions-is-hard"
},
"published": "2023-02-12T18:43:32+00:00",
"post-type": "note",
"_id": "35095502",
"_source": "7235",
"_is_read": false
}
