@TYLTK Mine's back up, and from what I see in the Known chat, you should be back too. Details about the issue here: https://chat.indieweb.org/known/2021-01-29#t1611887103870200
{
"type": "entry",
"published": "2021-01-29T20:55:36+00:00",
"url": "http://stream.boffosocko.com/2021/tyltk-mines-back-up-and-from-what-i-see-in",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1355258862182543362"
],
"in-reply-to": [
"https://twitter.com/TYLTK/status/1354978655223468035",
"https://tyltk.withknown.com/"
],
"content": {
"text": "@TYLTK Mine's back up, and from what I see in the Known chat, you should be back too. Details about the issue here: https://chat.indieweb.org/known/2021-01-29#t1611887103870200",
"html": "@TYLTK Mine's back up, and from what I see in the Known chat, you should be back too. Details about the issue here: <a href=\"https://chat.indieweb.org/known/2021-01-29#t1611887103870200\">https://chat.indieweb.org/known/2021-01-29#t1611887103870200</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "18067205",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-14T09:43:00+01:00",
"url": "https://notiz.blog/2021/01/14/projekt-26/",
"name": "Projekt 26",
"content": {
"text": "Torsten Landsiedel hatte 2019 die Idee zum #Projekt26:\n\n\n\nAlle zwei Wochen \u201emuss\u201c ein Blogartikel geschrieben werden.\nAlle zwei Wochen \u201emuss\u201c ein anderer Blogartikel kommentiert werden \u2013 das ist neu, aber wichtig, damit wir den Blog wieder als zentralen Ort f\u00fcr den Austausch nutzen und das nicht auf den Social Media Plattformen diverser Konzerne machen.\nDas Thema sollte WordPress sein, angrenzende Themengebiete, wie CSS, JavaScript, etc. gehen nat\u00fcrlich auch. Bonuspunkte gibt es f\u00fcr Artikel zum Thema Gutenberg.\nDer Hashtag lautet #projekt26 und sollte selbstredend bei der Bewerbung der Artikel genutzt werden.\nAm liebsten sind mir echte, origin\u00e4re Artikel, keine Zweiverwertungen, Listen, Linktipps, etc. \u2013 Faustformel k\u00f6nnte die Mindestl\u00e4nge der VG Wort sein (1800 Zeichen).\nIch mag den Fokus auf WordPress, auch wenn das ja hier eher nicht mein Haupt-Thema ist. Das gibt meinem Blog aber ein wenig Abwechslung und ich schaffe es vielleicht mal \u00fcber die ganzen Plugins zu schreiben, die ich in den letzten Jahren so verbrochen habe\u2026 und da w\u00e4ren wir ja wieder beim Thema \ud83d\ude09\n\n\n\nNeben dem regelm\u00e4\u00dfigen Bloggen, mag ich aber auch den Punkt mit dem Kommentieren. Was uns in den letzten Jahren immer mehr verloren gegangen ist, woran ironischerweise die SOZIALEN Netzwerke nicht ganz unschuldig sind, ist der Diskurs direkt im Blog. (Das ist \u00fcbrigens mit einer der Gr\u00fcnde warum ich das Webmention und ActivityPub Plugin geschrieben habe.)\n\n\n\nDa ich in den letzten Jahren hier eher weniger aktiv war, motiviert mich die Idee der selbstauferlegte Druck hoffentlich, in diesem Jahr regelm\u00e4\u00dfiger zu schreiben.\n\n\n\n\u2026und dass ich diesen Artikel statt in Kalenderwoche 1 oder 2, erst jetzt schreibe, best\u00e4rkt mich nur noch mehr in dieser Ansicht!\n\n\n\n(zum Gl\u00fcck kann man Artikel zur\u00fcck datieren \ud83d\ude00 )",
"html": "<p>Torsten Landsiedel <a href=\"https://torstenlandsiedel.de/2019/12/28/projekt26-jetzt-erst-recht/\">hatte 2019 die Idee</a> zum <a href=\"https://twitter.com/hashtag/project26\">#Projekt26</a>:</p>\n\n\n\n<ul><li>Alle <strong>zwei Wochen</strong> \u201e<em>muss</em>\u201c ein Blogartikel geschrieben werden.</li>\n<li>Alle zwei Wochen \u201e<em>muss</em>\u201c ein anderer Blogartikel kommentiert werden \u2013 <em>das ist neu</em>, aber wichtig, damit wir den Blog wieder als zentralen Ort f\u00fcr den Austausch nutzen und das nicht auf den Social Media Plattformen diverser Konzerne machen.</li>\n<li>Das Thema sollte WordPress sein, angrenzende Themengebiete, wie CSS, JavaScript, etc. gehen nat\u00fcrlich auch. Bonuspunkte gibt es f\u00fcr Artikel zum Thema Gutenberg.</li>\n<li>Der Hashtag lautet <code><a href=\"https://notiz.blog/tag/projekt26/\">#projekt26</a></code> und sollte selbstredend bei der Bewerbung der Artikel genutzt werden.</li>\n<li>Am liebsten sind mir echte, origin\u00e4re Artikel, keine Zweiverwertungen, Listen, Linktipps, etc. \u2013 Faustformel k\u00f6nnte die Mindestl\u00e4nge der VG Wort sein (1800 Zeichen).</li>\n</ul><p>Ich mag den Fokus auf WordPress, auch wenn das ja hier eher nicht mein Haupt-Thema ist. Das gibt meinem Blog aber ein wenig Abwechslung und ich schaffe es vielleicht mal \u00fcber die ganzen Plugins zu schreiben, die ich in den letzten Jahren so verbrochen habe\u2026 und da w\u00e4ren wir ja wieder beim Thema \ud83d\ude09</p>\n\n\n\n<p>Neben dem regelm\u00e4\u00dfigen Bloggen, mag ich aber auch den Punkt mit dem Kommentieren. Was uns in den letzten Jahren immer mehr verloren gegangen ist, woran ironischerweise die <strong>SOZIALEN</strong> Netzwerke nicht ganz unschuldig sind, ist der Diskurs direkt im Blog. (Das ist \u00fcbrigens mit einer der Gr\u00fcnde warum ich das <a href=\"https://wordpress.org/plugins/webmention/\">Webmention</a> und <a href=\"https://wordpress.org/plugins/activitypub/\">ActivityPub Plugin</a> geschrieben habe.)</p>\n\n\n\n<p>Da ich in den letzten Jahren hier eher weniger aktiv war, motiviert mich die Idee der selbstauferlegte Druck hoffentlich, in diesem Jahr regelm\u00e4\u00dfiger zu schreiben.</p>\n\n\n\n<p>\u2026und dass ich diesen Artikel statt in Kalenderwoche 1 oder 2, erst jetzt schreibe, best\u00e4rkt mich nur noch mehr in dieser Ansicht!</p>\n\n\n\n<p>(zum Gl\u00fcck kann man Artikel zur\u00fcck datieren \ud83d\ude00 )</p>"
},
"author": {
"type": "card",
"name": "Matthias Pfefferle",
"url": "https://notiz.blog/author/matthias-pfefferle/",
"photo": "https://secure.gravatar.com/avatar/75512bb584bbceae57dfc503692b16b2?s=40&d=mm&r=g"
},
"post-type": "article",
"_id": "18052534",
"_source": "206",
"_is_read": true
}
@Cambridgeport90 You need to tweak the theme so that Jetpack isn't included in the div with e-content.
You can use Indiewebify.me to test. Bridgy also has a preview option at https://brid.gy/twitter/Cambridgeport90
{
"type": "entry",
"published": "2021-01-25T19:42:47+00:00",
"url": "http://stream.boffosocko.com/2021/cambridgeport90-you-need-to-tweak-the-theme-so-that-jetpack",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1353790778175324160"
],
"in-reply-to": [
"https://twitter.com/Cambridgeport90/status/1353185750066622464"
],
"content": {
"text": "@Cambridgeport90 You need to tweak the theme so that Jetpack isn't included in the div with e-content. \n\nYou can use Indiewebify.me to test. Bridgy also has a preview option at https://brid.gy/twitter/Cambridgeport90",
"html": "<a href=\"https://twitter.com/Cambridgeport90\">@Cambridgeport90</a> You need to tweak the theme so that Jetpack isn't included in the div with e-content. <br />\nYou can use Indiewebify.me to test. Bridgy also has a preview option at <a href=\"https://brid.gy/twitter/Cambridgeport90\">https://brid.gy/twitter/Cambridgeport90</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "17973211",
"_source": "192",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-25T17:24:50+00:00",
"url": "http://stream.boffosocko.com/2021/andrejaenisch-yes-they-took-that-name-as-an-homagea_domain_of_one%2527s_own",
"syndication": [
"https://twitter.com/ChrisAldrich/status/1353756066929111046"
],
"in-reply-to": [
"https://twitter.com/AndreJaenisch/status/1353597489379758081"
],
"content": {
"text": "@AndreJaenisch Yes, they took that name as an homage.\nhttps://indieweb.org/A_Domain_of_One%27s_Own",
"html": "<a href=\"https://twitter.com/AndreJaenisch\">@AndreJaenisch</a> Yes, they took that name as an homage.<br /><a href=\"https://indieweb.org/A_Domain_of_One%27s_Own\">https://indieweb.org/A_Domain_of_One%27s_Own</a>"
},
"author": {
"type": "card",
"name": "Chris Aldrich",
"url": "http://stream.boffosocko.com/profile/chrisaldrich",
"photo": "http://stream.boffosocko.com/file/600427b81f7785e704eadfe511a9270f/thumb.jpg"
},
"post-type": "reply",
"_id": "17966705",
"_source": "192",
"_is_read": true
}
Something that I haven’t seen anywhere on the Indieweb: is there a simple guide for services which let you replace Twitter, Facebook, Insta, etc etc with more open alternatives? Preferably written with non-technical users in mind?
{
"type": "entry",
"author": {
"name": "Ian Betteridge",
"url": "https://ianbetteridge.com",
"photo": "https://micro.blog/ianbetteridge/avatar.jpg"
},
"url": "https://microblog.ianbetteridge.com/2021/01/24/something-that-i.html",
"content": {
"html": "<p>Something that I haven\u2019t seen anywhere on the Indieweb: is there a simple guide for services which let you replace Twitter, Facebook, Insta, etc etc with more open alternatives? Preferably written with non-technical users in mind?</p>",
"text": "Something that I haven\u2019t seen anywhere on the Indieweb: is there a simple guide for services which let you replace Twitter, Facebook, Insta, etc etc with more open alternatives? Preferably written with non-technical users in mind?"
},
"published": "2021-01-24T23:10:17+00:00",
"post-type": "note",
"_id": "33380030",
"_source": "7224",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-23 13:32-0800",
"url": "https://gregorlove.com/2021/01/today-i-dipped-my-toes/",
"category": [
"indieweb"
],
"name": "Some Thoughts on Commenting",
"content": {
"text": "Today I dipped my toes back into IndieWeb land (lake?) by joining the pop-up session, \u201cRespectful Responses.\u201d I didn\u2019t go in with a specific goal; it just sounded like a good topic:\n\n\nHow do we enable more positive serendipity & discovery via our websites, between both existing friends & family, and new positive interactions. And how do we raise barriers to spam, harassment, and other unpleasant social media interactions.\n\n\nThe session got me thinking more about the commenting experience for people without personal websites. David talked about the experience of leaving a comment and expecting it to appear immediately. Some sites will display a message that the comment is pending moderation, and some will even show the commenter a preview of their comment. My site does the former if I have not approved a comment from your email address before. I had not considered that could be a negative experience for some people. The more I thought about it, I realized that many times when I link an article on Facebook or Twitter, people will come to my site to read it then go back to the social site to leave a comment instead of using my local comment form.\n\nThis could be for various reasons. The most obvious is probably the ease of posting on the social site. It\u2019s one text field, the comment appears immediately, and that is how people interact online the majority of the time. My local comment form with fields for name, email address, website, and comment is tedious by comparison. I realize the required email address field is off-putting as well.\n\nI like the idea of changing that experience around so instead of a comment form that\u2019s always public, comments are allowed from a trusted audience. That audience could be as broad as \u201cpeople who have logged in to my site.\u201d I think the barrier of logging in would still mean people would go back to the social sites to respond, though. I am not sure how to get around that. That is often the challenge with IndieWeb: creating experiences that are at least as easy as the silos.",
"html": "<p>Today I dipped my toes back into IndieWeb land (lake?) by joining the pop-up session, \u201c<a href=\"https://events.indieweb.org/2021/01/indiewebcamp-pop-up-session-respectful-responses-SoijMaY9KH7P\">Respectful Responses</a>.\u201d I didn\u2019t go in with a specific goal; it just sounded like a good topic:</p>\n\n<blockquote>\n<p>How do we enable more positive serendipity & discovery via our websites, between both existing friends & family, and new positive interactions. And how do we raise barriers to spam, harassment, and other unpleasant social media interactions.</p>\n</blockquote>\n\n<p>The session got me thinking more about the commenting experience for people without personal websites. <a class=\"h-card\" href=\"https://david.shanske.com/\">David</a> talked about the experience of leaving a comment and expecting it to appear immediately. Some sites will display a message that the comment is pending moderation, and some will even show the commenter a preview of their comment. My site does the former if I have not approved a comment from your email address before. I had not considered that could be a negative experience for some people. The more I thought about it, I realized that many times when I link an article on Facebook or Twitter, people will come to my site to read it then go back to the social site to leave a comment instead of using my local comment form.</p>\n\n<p>This could be for various reasons. The most obvious is probably the ease of posting on the social site. It\u2019s one text field, the comment appears immediately, and that is how people interact online the majority of the time. My local comment form with fields for name, email address, website, and comment is tedious by comparison. I realize the required email address field is off-putting as well.</p>\n\n<p>I like the idea of changing that experience around so instead of a comment form that\u2019s always public, comments are allowed from a trusted audience. That audience could be as broad as \u201cpeople who have logged in to my site.\u201d I think the barrier of logging in would still mean people would go back to the social sites to respond, though. I am not sure how to get around that. That is often the challenge with IndieWeb: creating experiences that are at least as easy as the silos.</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/3473/profile-2016-med.jpg"
},
"post-type": "article",
"_id": "17934254",
"_source": "95",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/12555-webmention-js-0-4-0",
"published": "2021-01-23T12:15:58-08:00",
"content": {
"html": "<p>I\u2019ve just released v0.4.0 of <a href=\"https://github.com/PlaidWeb/webmention.js/\">webmention.js</a>, which adds the ability to coalesce comment-type responses into the \u201creactions\u201d section. I\u2019d been considering it for a while but finally got the impetus to add it during today\u2019s <a href=\"https://events.indieweb.org/2021/01/indiewebcamp-pop-up-session-respectful-responses-SoijMaY9KH7P\">Respectful Responses IndieWeb session</a>.</p><p>This change shouldn\u2019t break current users of webmention.js, as it\u2019s an opt-in configuration value.</p><p>As an aside, I <em>really</em> need to get around to making an actual site for <a href=\"https://plaidweb.site/\">PlaidWeb</a>, so I have somewhere to put non-Publ discussion and release announcements.</p>\n\n\n\n\n<p><a href=\"http://beesbuzz.biz/blog/12555-webmention-js-0-4-0#comments\">comments</a></p>",
"text": "I\u2019ve just released v0.4.0 of webmention.js, which adds the ability to coalesce comment-type responses into the \u201creactions\u201d section. I\u2019d been considering it for a while but finally got the impetus to add it during today\u2019s Respectful Responses IndieWeb session.This change shouldn\u2019t break current users of webmention.js, as it\u2019s an opt-in configuration value.As an aside, I really need to get around to making an actual site for PlaidWeb, so I have somewhere to put non-Publ discussion and release announcements.\n\n\n\n\ncomments"
},
"name": "fluffy rambles: webmention.js 0.4.0",
"post-type": "article",
"_id": "17931061",
"_source": "3782",
"_is_read": true
}
I'm going!IndieWeb-friendly personal sites can work together to provide all kinds of social features to the web. Likes, replies, bookmarks, GIF responses, reaction videos, and way more!
But should our sites do this? Recreating the dopamine-hit, engagement-maximizing, abuse-inviting patterns of the social silos is likely not the answer.
How can we make the web social while protecting one another?
Let’s start a conversation and find out in this IndieWebCamp Popup!
{
"type": "entry",
"published": "2021-01-20T21:41:00-0500",
"rsvp": "yes",
"url": "https://martymcgui.re/2021/01/20/214100/",
"in-reply-to": [
"https://events.indieweb.org/2021/01/respectful-responses-SoijMaY9KH7P"
],
"content": {
"text": "I'm going!IndieWeb-friendly personal sites can work together to provide all kinds of social features to the web. Likes, replies, bookmarks, GIF responses, reaction videos, and way more!\n\nBut should our sites do this? Recreating the dopamine-hit, engagement-maximizing, abuse-inviting patterns of the social silos is likely not the answer.\n\nHow can we make the web social while protecting one another?\n\nLet\u2019s start a conversation and find out in this IndieWebCamp Popup!",
"html": "I'm going!<p>IndieWeb-friendly personal sites can work together to provide all kinds of social features to the web. Likes, replies, bookmarks, GIF responses, reaction videos, and way more!</p>\n\n<p>But <em>should</em> our sites do this? Recreating the dopamine-hit, engagement-maximizing, abuse-inviting patterns of the social silos is likely not the answer.</p>\n\n<p>How can we make the web social while protecting one another?</p>\n\n<p>Let\u2019s start a conversation and find out in this IndieWebCamp Popup!</p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "rsvp",
"refs": {
"https://events.indieweb.org/2021/01/respectful-responses-SoijMaY9KH7P": {
"type": "entry",
"summary": "How do we enable more positive serendipity & discovery via our websites, between both existing friends & family, and new positive interactions. And how do we raise barriers to spam, harassment, and other unpleasant social media interactions.",
"url": "https://events.indieweb.org/2021/01/respectful-responses-SoijMaY9KH7P",
"name": "Respectful Responses",
"author": {
"type": "card",
"name": "events.indieweb.org",
"url": "http://events.indieweb.org",
"photo": null
},
"post-type": "article"
}
},
"_id": "17871410",
"_source": "175",
"_is_read": true
}
Our footpaths converged around the same 5-10 platforms, each with its own particular manner of communication. I have learned, unintentionally, to code switch every time I craft a new post. It’s exhausting, trying to keep track of all those unspoken rules shaped by years of use.
But I don’t have rules like that on my blog. I turned off stats. There are no comments. No likes.
{
"type": "entry",
"published": "2021-01-19T20:23:59Z",
"url": "https://adactio.com/links/17766",
"category": [
"writing",
"blogging",
"publishing",
"sharing",
"indieweb",
"socialmedia",
"rss"
],
"bookmark-of": [
"https://lucybellwood.com/stumbling/"
],
"content": {
"text": "Stumbling \u2013 Lucy Bellwood\n\n\n\n\n Our footpaths converged around the same 5-10 platforms, each with its own particular manner of communication. I have learned, unintentionally, to code switch every time I craft a new post. It\u2019s exhausting, trying to keep track of all those unspoken rules shaped by years of use.\n \n But I don\u2019t have rules like that on my blog. I turned off stats. There are no comments. No likes.",
"html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://lucybellwood.com/stumbling/\">\nStumbling \u2013 Lucy Bellwood\n</a>\n</h3>\n\n<blockquote>\n <p>Our footpaths converged around the same 5-10 platforms, each with its own particular manner of communication. I have learned, unintentionally, to code switch every time I craft a new post. It\u2019s exhausting, trying to keep track of all those unspoken rules shaped by years of use.</p>\n \n <p>But I don\u2019t have rules like that on my blog. I turned off stats. There are no comments. No likes.</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": "17837213",
"_source": "2",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-19T18:08:06.603Z",
"url": "https://www.jvt.me/mf2/2021/01/iyvrw/",
"category": [
"homebrew-website-club"
],
"content": {
"text": "Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-LwVx3NUZ2dKh",
"html": "<p>Reminder that it's <a href=\"https://www.jvt.me/tags/homebrew-website-club/\">#HomebrewWebsiteClub</a> Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! <a href=\"https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-LwVx3NUZ2dKh\">https://events.indieweb.org/2021/01/homebrew-website-club-nottingham-LwVx3NUZ2dKh</a></p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "17836506",
"_source": "2169",
"_is_read": true
}
“In the case of Capsule, each content creator has their own website — has their own address, like Capsule.Greenwald.com — and then people go there and their first discovery of the mesh is through people that they’re interested in hearing from.”
techcrunch.com/2021/01/18/cryptocat-author-gets-insanely-fast-backing-to-build-p2p-tech-for-social-media
I had to think about this for a bit, but I think I like this idea as an extension of the current IndieWeb ecosystem. Most people don't want to pay for a domain name or hosting, so I wonder whether Capsule can find a way to enable both groups to interact successfully.
The question for me is, will non-paying servers be able to operate as first class citizens in the federation, with a trusted identity? Will be interesting to watch development.
{
"type": "entry",
"published": "2021-01-19T17:08:26+10:00",
"url": "https://mblaney.xyz/2021-01-19-In_the_case_of_Capsule_each_content_creato",
"category": [
"indieweb"
],
"content": {
"text": "\u201cIn the case of Capsule, each content creator has their own website \u2014 has their own address, like Capsule.Greenwald.com \u2014 and then people go there and their first discovery of the mesh is through people that they\u2019re interested in hearing from.\u201d\n\ntechcrunch.com/2021/01/18/cryptocat-author-gets-insanely-fast-backing-to-build-p2p-tech-for-social-media\n\n\nI had to think about this for a bit, but I think I like this idea as an extension of the current IndieWeb ecosystem. Most people don't want to pay for a domain name or hosting, so I wonder whether Capsule can find a way to enable both groups to interact successfully.\n\n\nThe question for me is, will non-paying servers be able to operate as first class citizens in the federation, with a trusted identity? Will be interesting to watch development.",
"html": "\u201cIn the case of Capsule, each content creator has their own website \u2014 has their own address, like Capsule.Greenwald.com \u2014 and then people go there and their first discovery of the mesh is through people that they\u2019re interested in hearing from.\u201d<br /><br /><a href=\"https://techcrunch.com/2021/01/18/cryptocat-author-gets-insanely-fast-backing-to-build-p2p-tech-for-social-media/?ncid=txtlnkusaolp00000618\">techcrunch.com/2021/01/18/cryptocat-author-gets-insanely-fast-backing-to-build-p2p-tech-for-social-media</a><br /><br />\nI had to think about this for a bit, but I think I like this idea as an extension of the current IndieWeb ecosystem. Most people don't want to pay for a domain name or hosting, so I wonder whether Capsule can find a way to enable both groups to interact successfully.<br /><br />\nThe question for me is, will non-paying servers be able to operate as first class citizens in the federation, with a trusted identity? Will be interesting to watch development."
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://mblaney.xyz",
"photo": "https://mblaney.xyz/public/profile_thumb.png"
},
"post-type": "note",
"_id": "17823101",
"_source": "3708",
"_is_read": true
}
Does anyone have any experience with the whole IndieWeb thing? It feels more complicated than it’s worth. https://indieweb.org/
mike.rockwell.mx
{
"type": "entry",
"author": {
"name": "Mike Rockwell",
"url": "https://mdrockwell.net/",
"photo": "https://www.gravatar.com/avatar/6cb444245fc3c3ace752833c2616784a?s=96&d=https%3A%2F%2Fmicro.blog%2Fimages%2Fblank_avatar.png"
},
"url": "https://mike.rockwell.mx/asides/450",
"content": {
"html": "<p>Does anyone have any experience with the whole IndieWeb thing? It feels more complicated than it\u2019s worth. <a href=\"https://indieweb.org/\">https://indieweb.org/</a></p> <a href=\"https://mike.rockwell.mx/asides/450\">mike.rockwell.mx</a>",
"text": "Does anyone have any experience with the whole IndieWeb thing? It feels more complicated than it\u2019s worth. https://indieweb.org/ mike.rockwell.mx"
},
"published": "2021-01-17T23:37:40+00:00",
"post-type": "note",
"_id": "33380031",
"_source": "7224",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-16T19:23:55+00:00",
"url": "https://werd.io/2021/adjusting-the-volume",
"name": "Adjusting the volume",
"content": {
"text": "I'm not quite an indieweb zealot - you can find me on Twitter and other social networks over the web - but I've been writing on my own site since 1998 (albeit not one consistent, continuous site - I change it up every decade or so), and it's become a core part of who I am, how I think, and how I represent myself online.You might have noticed - email subscribers certainly did - that I've turned up the volume on my posting this year. So far in January, that's meant a post a day in my personal space. The feedback has generally been good, but a few email subscribers did complain. I totally get it. Nobody wants their inboxes to clog up; the calculus might be different if this was a business newsletter with actionable insights, but that's not what this is. More than anything, I'm hoping to spark a conversation with my posts.There are a few things I'm thinking about doing. The first is dropping the frequency of the emails, and thinking about them as more of a digest. You'd get one on Thursday, and one on Sunday (or something like that). Obviously, RSS / h-feed / JSON-feed subscribers (hi!) would still receive posts in real time. Maybe there would also be an email list for people who did want to receive posts as I wrote them.The second thing I'm thinking about doing is taking this posting frequency and putting it on Medium for the rest of the month, with a regular summary post over here. This is a controversial thing for someone who's so deep into indieweb and the open web to suggest, but there are a few reasons for trying this. Mostly I want to see how the experience compares. I worked at Medium in 2016, and posted fairly regularly there during that time and while I was at Matter Ventures, but the platform has evolved significantly since then.So that's what I'm going to do to start. For the remainder of January, I'll be posting on Medium daily, with summary listings posted here semi-regularly. Then I'll return here in February and let you know what I discovered.You can follow me on Medium over here.",
"html": "<p>I'm not quite an <a href=\"https://indieweb.org\">indieweb</a> zealot - you can find me on Twitter and other social networks over the web - but I've been writing on my own site since 1998 (albeit not one consistent, continuous site - I change it up every decade or so), and it's become a core part of who I am, how I think, and how I represent myself online.</p><p>You might have noticed - email subscribers certainly did - that I've turned up the volume on my posting this year. So far in January, that's meant a post a day in my personal space. The feedback has generally been good, but a few email subscribers did complain. I totally get it. Nobody wants their inboxes to clog up; the calculus might be different if this was a business newsletter with actionable insights, but that's not what this is. More than anything, I'm hoping to spark a conversation with my posts.</p><p>There are a few things I'm thinking about doing. The first is dropping the frequency of the emails, and thinking about them as more of a digest. You'd get one on Thursday, and one on Sunday (or something like that). Obviously, RSS / h-feed / JSON-feed subscribers (hi!) would still receive posts in real time. Maybe there would also be an email list for people who <em>did</em> want to receive posts as I wrote them.</p><p>The second thing I'm thinking about doing is taking this posting frequency and <a href=\"https://benwerd.medium.com\">putting it on Medium</a> for the rest of the month, with a regular summary post over here. This is a controversial thing for someone who's so deep into indieweb and the open web to suggest, but there are a few reasons for trying this. Mostly I want to see how the experience compares. I worked at Medium in 2016, and posted fairly regularly there during that time and <a href=\"https://medium.com/matter-driven-narrative\">while I was at Matter Ventures</a>, but the platform has evolved significantly since then.</p><p>So that's what I'm going to do to start. For the remainder of January, I'll be posting on Medium daily, with summary listings posted here semi-regularly. Then I'll return here in February and let you know what I discovered.</p><p><a href=\"https://benwerd.medium.com\">You can follow me on Medium over here.</a></p>"
},
"author": {
"type": "card",
"name": "Ben Werdm\u00fcller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "article",
"_id": "17775347",
"_source": "191",
"_is_read": true
}
#indieweb is the best web
My new year's resolution is to read and respond to comments on my blog. Getting a bit hard to respond to every question on twitter, and I think this might be bit more manageable. conscienceandconsciousness.com
https://twitter.com/Philip_Goff/status/1350212744075743238
{
"type": "entry",
"published": "2021-01-16T12:27:09+10:00",
"url": "https://mblaney.xyz/2021-01-16-indieweb_is_the_best_web__My_new_years_res",
"syndication": [
"https://twitter.com/malcolmblaney/status/1350268343761186816"
],
"quotation-of": "https://twitter.com/Philip_Goff/status/1350212744075743238",
"content": {
"text": "#indieweb is the best web\n\nMy new year's resolution is to read and respond to comments on my blog. Getting a bit hard to respond to every question on twitter, and I think this might be bit more manageable. conscienceandconsciousness.com\nhttps://twitter.com/Philip_Goff/status/1350212744075743238",
"html": "#indieweb is the best web<br /><br />My new year's resolution is to read and respond to comments on my blog. Getting a bit hard to respond to every question on twitter, and I think this might be bit more manageable. <a href=\"https://conscienceandconsciousness.com/\">conscienceandconsciousness.com</a><br /><a class=\"u-url\" href=\"https://twitter.com/Philip_Goff/status/1350212744075743238\">https://twitter.com/Philip_Goff/status/1350212744075743238</a><a href=\"https://brid.gy/publish/twitter?bridgy_omit_link=true\"></a><a href=\"https://twitter.com/malcolmblaney/status/1350268343761186816\" class=\"u-syndication\"></a>"
},
"author": {
"type": "card",
"name": "Malcolm Blaney",
"url": "https://mblaney.xyz",
"photo": "https://mblaney.xyz/public/profile_thumb.png"
},
"post-type": "note",
"refs": {
"https://twitter.com/Philip_Goff/status/1350212744075743238": {
"type": "entry",
"url": "https://twitter.com/Philip_Goff/status/1350212744075743238",
"name": "My new year's resolution is to read and respond to comments on my blog. Getting a bit hard to respond to every question on twitter, and I think this might be bit more manageable. conscienceandconsciousness.com\nhttps://twitter.com/Philip_Goff/status/1350212744075743238",
"post-type": "article"
}
},
"_id": "17765228",
"_source": "3708",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": "fluffy",
"url": "http://beesbuzz.biz/",
"photo": null
},
"url": "http://beesbuzz.biz/blog/2316-Distributed-toxicity-and-the-IndieWeb",
"published": "2021-01-12T14:44:18-08:00",
"content": {
"html": "<p>This tweet has been making the rounds in IndieWeb spaces, and reflects a thing I\u2019ve been thinking about on and off lately for obvious reasons:</p><blockquote><p>I was building a decentralized, WebMention-based social network (way before Mastodon/ActivityPub), and if anyone had cared back then, it would be a nazi darling today and that just sucks. <a href=\"https://t.co/jXaZTsUNz8\">https://t.co/jXaZTsUNz8</a></p>\u2014 Hendrik Mans (@hmans) <a href=\"https://twitter.com/hmans/status/1349105824992538624?ref_src=twsrc%5Etfw\">January 12, 2021</a></blockquote> <p>I\u2019ve seen several other related sentiments lately; with a certain prominent politician being deplatformed from all of the mainstream social media platforms, and all of the platforms that accept him being in turn shut down or otherwise made ineffective, people have been (quite reasonably!) wondering what happens if he ends up starting up his own IndieWeb site, and causes a resurgence in self-hosted or otherwise privately-run, single-author blogs.</p>\n\n\n<p>I feel like the threat model for IndieWeb is very different than the threat model of so-called \u201csilo\u201d social media. Silos are built around increasing engagement and spreading popular posts far and wide, and ensuring that people stay addicted to the site. As such, they\u2019re also biased towards fast-spreading, viral content, and quick, hot takes that give people an adrenaline and/or dopamine rush.</p><p>One way in which self-hosted platforms are different is that it\u2019s up to people to seek out and spread the information they want to. At least with current platforms it\u2019s pretty unwieldy to do a quick repost and propagation of content, and there\u2019s also no central source of post propagation. You posting something to the IndieWeb doesn\u2019t mean that it\u2019ll automatically propagate to anyone who isn\u2019t already subscribed to you, and audiences tend to remain a lot smaller and more deliberate.</p><p>Mastodon still has the concept of a federated timeline, where anything that gets posted will spread far and wide based on connections between instances. This is, in effect, very similar to the algorithmic discovery stuff that makes Twitter work the way it does too.</p><p>There\u2019s also the whole fire-and-forget quick-post hot-take nature of conversations which just plain doesn\u2019t happen in IndieWeb spaces, at least not right now. Some future stack might make Twitter-like updates more convenient. I know that I personally wouldn\u2019t subscribe to sources of those, though, and there\u2019s still a much greater onus on the reader to be able to subscribe to and process those feeds.</p><p>A future IndieWeb platform could very well make the same mistakes, though, and lead to automatic discovery and propagation of stuff. Centralized readers in particular would be a pretty obvious source of this sort of thing.</p><p>But the great thing about IndieWeb, at least, is that people are still in control of their experience. There isn\u2019t one specific publishing or reading model that people are stuck with, and this is by design. There will certainly be <em>pockets</em> of IndieWeb stuff that becomes just as objectionable as the worst parts of Twitter/Mastodon or the entirety of Parler/Gab, but people can still participate in IndieWeb without having to be a part of it.</p><p>I also feel that having personal responsibility for the content you host also makes you much more accountable for that content. If someone were to start posting illegal stuff to their website, their hosting provider would be well within their rights to shut it down. They could then move to a hosting provider that\u2019s more amenable to that or not under the same jurisdiction, but fundamentally, if nobody is subscribing to their site content, it\u2019s still not going to spread.</p><p>For that matter, nothing stops any currently-deplatformed troll from running their own website. There are <em>plenty</em> of ways that people can launch a quick-and-easy WordPress blog, for example. But just because someone is posting it to the web doesn\u2019t mean they\u2019re going to have an audience. Nothing automatically makes their toxic material spread through the universe.</p><p>I think IndieWeb developers do need to be careful about the tools they develop. If you\u2019re working on IndieWeb stuff, make sure you\u2019re solving the problems that need to be solved, and not reinventing the same problems as the silos the long way around. And if you\u2019re building a shared-hosting platform or a centralized reader, you\u2019d better damned well be putting safety and accountability as the top priority for everything you provide.</p><p>So, yeah. I can imagine some facet of IndieWeb going in a very dangerous direction that would be much more difficult to stop than on a centralized server. But IndieWeb is an ethos and a set of opt-in protocols, and participating in IndieWeb in general doesn\u2019t mean having to participate in <em>all</em> of it. I feel like that\u2019s already a huge advantage.</p>\n\n<p><a href=\"http://beesbuzz.biz/blog/2316-Distributed-toxicity-and-the-IndieWeb#comments\">comments</a></p>",
"text": "This tweet has been making the rounds in IndieWeb spaces, and reflects a thing I\u2019ve been thinking about on and off lately for obvious reasons:I was building a decentralized, WebMention-based social network (way before Mastodon/ActivityPub), and if anyone had cared back then, it would be a nazi darling today and that just sucks. https://t.co/jXaZTsUNz8\u2014 Hendrik Mans (@hmans) January 12, 2021 I\u2019ve seen several other related sentiments lately; with a certain prominent politician being deplatformed from all of the mainstream social media platforms, and all of the platforms that accept him being in turn shut down or otherwise made ineffective, people have been (quite reasonably!) wondering what happens if he ends up starting up his own IndieWeb site, and causes a resurgence in self-hosted or otherwise privately-run, single-author blogs.\n\n\nI feel like the threat model for IndieWeb is very different than the threat model of so-called \u201csilo\u201d social media. Silos are built around increasing engagement and spreading popular posts far and wide, and ensuring that people stay addicted to the site. As such, they\u2019re also biased towards fast-spreading, viral content, and quick, hot takes that give people an adrenaline and/or dopamine rush.One way in which self-hosted platforms are different is that it\u2019s up to people to seek out and spread the information they want to. At least with current platforms it\u2019s pretty unwieldy to do a quick repost and propagation of content, and there\u2019s also no central source of post propagation. You posting something to the IndieWeb doesn\u2019t mean that it\u2019ll automatically propagate to anyone who isn\u2019t already subscribed to you, and audiences tend to remain a lot smaller and more deliberate.Mastodon still has the concept of a federated timeline, where anything that gets posted will spread far and wide based on connections between instances. This is, in effect, very similar to the algorithmic discovery stuff that makes Twitter work the way it does too.There\u2019s also the whole fire-and-forget quick-post hot-take nature of conversations which just plain doesn\u2019t happen in IndieWeb spaces, at least not right now. Some future stack might make Twitter-like updates more convenient. I know that I personally wouldn\u2019t subscribe to sources of those, though, and there\u2019s still a much greater onus on the reader to be able to subscribe to and process those feeds.A future IndieWeb platform could very well make the same mistakes, though, and lead to automatic discovery and propagation of stuff. Centralized readers in particular would be a pretty obvious source of this sort of thing.But the great thing about IndieWeb, at least, is that people are still in control of their experience. There isn\u2019t one specific publishing or reading model that people are stuck with, and this is by design. There will certainly be pockets of IndieWeb stuff that becomes just as objectionable as the worst parts of Twitter/Mastodon or the entirety of Parler/Gab, but people can still participate in IndieWeb without having to be a part of it.I also feel that having personal responsibility for the content you host also makes you much more accountable for that content. If someone were to start posting illegal stuff to their website, their hosting provider would be well within their rights to shut it down. They could then move to a hosting provider that\u2019s more amenable to that or not under the same jurisdiction, but fundamentally, if nobody is subscribing to their site content, it\u2019s still not going to spread.For that matter, nothing stops any currently-deplatformed troll from running their own website. There are plenty of ways that people can launch a quick-and-easy WordPress blog, for example. But just because someone is posting it to the web doesn\u2019t mean they\u2019re going to have an audience. Nothing automatically makes their toxic material spread through the universe.I think IndieWeb developers do need to be careful about the tools they develop. If you\u2019re working on IndieWeb stuff, make sure you\u2019re solving the problems that need to be solved, and not reinventing the same problems as the silos the long way around. And if you\u2019re building a shared-hosting platform or a centralized reader, you\u2019d better damned well be putting safety and accountability as the top priority for everything you provide.So, yeah. I can imagine some facet of IndieWeb going in a very dangerous direction that would be much more difficult to stop than on a centralized server. But IndieWeb is an ethos and a set of opt-in protocols, and participating in IndieWeb in general doesn\u2019t mean having to participate in all of it. I feel like that\u2019s already a huge advantage.\n\ncomments"
},
"name": "fluffy rambles: Distributed toxicity and the IndieWeb",
"post-type": "article",
"_id": "17688237",
"_source": "3782",
"_is_read": true
}
Creating Postman collections programmatically from a Micropub server's supported configuration.
{
"type": "entry",
"published": "2021-01-11 19:37:01 +0000 UTC",
"summary": "Creating Postman collections programmatically from a Micropub server's supported configuration.",
"url": "https://www.jvt.me/posts/2021/01/11/micropub-postman/",
"category": [
"postman",
"ruby",
"micropub",
"micropub-postman"
],
"name": "Autogenerating Postman Collections for Micropub Servers",
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "article",
"_id": "17655943",
"_source": "2169",
"_is_read": true
}
Tonight I've been investigating a few things for my #Postman API Hack and I've found that Postman's OAuth2 support is pretty awesome - it works very nicely with #Indieauth which is an important part of my hack 😉 I'm also pretty happy with what I'm planning on doing - hoping to get some good progress with the hack itself this weekend, too!
{
"type": "entry",
"published": "2021-01-08T22:26:30.781Z",
"url": "https://www.jvt.me/mf2/2021/01/hjfzb/",
"category": [
"postman",
"indieauth"
],
"content": {
"text": "Tonight I've been investigating a few things for my #Postman API Hack and I've found that Postman's OAuth2 support is pretty awesome - it works very nicely with #Indieauth which is an important part of my hack \ud83d\ude09 I'm also pretty happy with what I'm planning on doing - hoping to get some good progress with the hack itself this weekend, too!",
"html": "<p>Tonight I've been investigating a few things for my <a href=\"https://www.jvt.me/tags/postman/\">#Postman</a> API Hack and I've found that Postman's OAuth2 support is pretty awesome - it works very nicely with <a href=\"https://www.jvt.me/tags/indieauth/\">#Indieauth</a> which is an important part of my hack \ud83d\ude09 I'm also pretty happy with what I'm planning on doing - hoping to get some good progress with the hack itself this weekend, too!</p>"
},
"author": {
"type": "card",
"name": "Jamie Tanna",
"url": "https://www.jvt.me",
"photo": "https://www.jvt.me/img/profile.png"
},
"post-type": "note",
"_id": "17596654",
"_source": "2169",
"_is_read": true
}
🔖 Bookmarked How I turned my Goodreads data into a self-hosted website with Eleventy https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy
{
"type": "entry",
"published": "2021-01-07T18:17:46-0500",
"summary": "\ud83d\udd16 Bookmarked How I turned my Goodreads data into a self-hosted website with Eleventy https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy",
"url": "https://martymcgui.re/2021/01/07/how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy/",
"category": [
"goodreads",
"IndieWeb",
"ownyourdata"
],
"bookmark-of": [
"https://hiddedevries.nl/en/blog/2021-01-04-how-i-turned-my-goodreads-data-into-a-self-hosted-website-with-eleventy"
],
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "bookmark",
"_id": "17567148",
"_source": "175",
"_is_read": true
}
{
"type": "entry",
"published": "2021-01-06T10:13:25-08:00",
"url": "https://aaronparecki.com/2021/01/06/7/indieweb",
"category": [
"indieweb"
],
"syndication": [
"https://twitter.com/aaronpk/status/1346882587000664064"
],
"content": {
"text": "Live now! \ud83c\udf99 @allie_nimmons and @DavidWolfpaw chatting all about the #IndieWeb! https://youtu.be/i6Ixyi_I9g4",
"html": "Live now! \ud83c\udf99 <a href=\"https://twitter.com/allie_nimmons\">@allie_nimmons</a> and <a href=\"https://twitter.com/DavidWolfpaw\">@DavidWolfpaw</a> chatting all about the <a href=\"https://aaronparecki.com/tag/indieweb\">#IndieWeb</a>! <a href=\"https://youtu.be/i6Ixyi_I9g4\"><span>https://</span>youtu.be/i6Ixyi_I9g4</a>"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "note",
"_id": "17527851",
"_source": "16",
"_is_read": true
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://dri.es/",
"photo": null
},
"url": "https://dri.es/can-someone-add-some-more-html-tags-please",
"published": "2021-01-06T04:39:12-05:00",
"content": {
"html": "<p>Every day, millions of new web pages are added to the internet. Most of them are unstructured, uncategorized, and nearly impossible for software to understand. It irks me.</p>\n\n<p>Look no further than <a href=\"https://en.wikipedia.org/wiki/Tim_Berners-Lee\">Sir Tim Berners-Lee's Wikipedia page</a>:</p>\n\n\n<img src=\"https://dri.es/files/images/blog/wikipedia-timbl-markup.png\" alt=\"The markup for Tim Berners-Lee's Wikipedia page; it's complex and inconsistent\" title=\"Tim Berners-Lee's Wikipedia page: HMTL code\" /><em>What Wikipedia editors write (<a href=\"https://en.wikipedia.org/w/index.php?title=Tim_Berners-Lee&action=edit\">source</a>).</em><img src=\"https://dri.es/files/images/blog/wikipedia-timbl-page.png\" alt=\"The browser output for Tim Berners-Lee's Wikipedia page\" title=\"Tim Berners-Lee's Wikipedia page: rendered page\" /><em>What visitors of Wikipedia see.</em><p>At first glance, there is <a href=\"http://blog.spencermounta.in/2019/wikipedias-in-trouble/index.html\">no rhyme or reason to Wikipedia's markup</a>. (Wikipedia also has <a href=\"https://en.wikipedia.org/wiki/Help:WikiHiero_syntax\">custom markup for hieroglyphs</a>, which admittedly <em>is</em> pretty cool.)</p>\n\n<p>The problem? Wikipedia is the world's largest source of knowledge. It's a top 10 website in the world. Yet, Wikipedia's markup language is <a href=\"http://blog.spencermounta.in/2019/wikipedias-in-trouble/index.html\">nearly impossible to parse</a>, Tim Berners-Lee's Wikipedia page has <a href=\"https://validator.w3.org/nu/?doc=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FTim_Berners-Lee\">almost 100 HTML validation errors</a>, and the page's generated HTML output is not very semantic. It's hard to use or re-use with other software.</p>\n\n<p>I bet it irks Sir Tim Berners-Lee too.</p>\n\n\n<img src=\"https://dri.es/files/images/blog/wikipedia-timbl-markup.png\" alt=\"The markup for Tim Berners-Lee's Wikipedia page; it's complex and inconsistent\" title=\"Tim Berners-Lee's Wikipedia page: HMTL code\" /><em>What Wikipedia editors write (<a href=\"https://en.wikipedia.org/w/index.php?title=Tim_Berners-Lee&action=edit\">source</a>).</em><img src=\"https://dri.es/files/images/blog/wikipedia-timbl-html.png\" alt=\"The generated HTML code for Tim Berners-Lee's Wikipedia page; it could be more semantic\" title=\"Tim Berners-Lee's Wikipedia page: generated HTML code\" /><em>What the browser sees; the HTML code Wikipedia (MediaWiki) generates.</em><p>It's not just Wikipedia. Every site is still messing around with custom <code>s for a table of contents, footnotes, logos, and more. I could think of a dozen new HTML tags that would make web pages, including Wikipedia, easier to write and reuse: , , , and many more.\n\n</code></p><p><code>A good approach would be to take the most successful <a href=\"https://en.wikipedia.org/wiki/Schema.org\">Schema.org schemas</a>, <a href=\"http://microformats.org/\">Microformats</a> and <a href=\"https://en.wikipedia.org/wiki/Web_Components\">Web Components</a>, and incorporate their functionality into the <a href=\"https://html.spec.whatwg.org/\">official HTML specification</a>.</code></p><code>\n\n</code><p><code>Adding new semantic markup options to <em>the</em> HTML specification is the surest way to improve the semantic web, improve content reuse, and advance content authoring tools.</code></p><code> \n\n</code><p><code>Unfortunately, I don't see new tags being introduced. I don't see experiments with <a href=\"https://en.wikipedia.org/wiki/Web_Components\">Web Components</a> being promoted to official standards. I hope I'm wrong! (<a href=\"https://meta.wikimedia.org/wiki/Cunningham%27s_Law\">Cunningham's Law</a> states that <q>the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer</q>. If I'm wrong, I'll update this poost.)</code></p><code>\n \n</code><p><code>If you want to help make the web better, you could literally start with <a href=\"https://en.wikipedia.org/wiki/Tim_Berners-Lee\">Sir Tim Berners-Lee's Wikipedia page</a>, and use it as the basis to spend a decade <a href=\"https://github.com/whatwg/html/commits\">pushing for HTML markup improvements</a>. It could be the <a href=\"http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.html\">start of a long and successful career</a>.</code></p><code></code>",
"text": "Every day, millions of new web pages are added to the internet. Most of them are unstructured, uncategorized, and nearly impossible for software to understand. It irks me.\n\nLook no further than Sir Tim Berners-Lee's Wikipedia page:\n\n\nWhat Wikipedia editors write (source).What visitors of Wikipedia see.At first glance, there is no rhyme or reason to Wikipedia's markup. (Wikipedia also has custom markup for hieroglyphs, which admittedly is pretty cool.)\n\nThe problem? Wikipedia is the world's largest source of knowledge. It's a top 10 website in the world. Yet, Wikipedia's markup language is nearly impossible to parse, Tim Berners-Lee's Wikipedia page has almost 100 HTML validation errors, and the page's generated HTML output is not very semantic. It's hard to use or re-use with other software.\n\nI bet it irks Sir Tim Berners-Lee too.\n\n\nWhat Wikipedia editors write (source).What the browser sees; the HTML code Wikipedia (MediaWiki) generates.It's not just Wikipedia. Every site is still messing around with custom s for a table of contents, footnotes, logos, and more. I could think of a dozen new HTML tags that would make web pages, including Wikipedia, easier to write and reuse: , , , and many more.\n\nA good approach would be to take the most successful Schema.org schemas, Microformats and Web Components, and incorporate their functionality into the official HTML specification.\n\nAdding new semantic markup options to the HTML specification is the surest way to improve the semantic web, improve content reuse, and advance content authoring tools. \n\nUnfortunately, I don't see new tags being introduced. I don't see experiments with Web Components being promoted to official standards. I hope I'm wrong! (Cunningham's Law states that the best way to get the right answer on the internet is not to ask a question; it's to post the wrong answer. If I'm wrong, I'll update this poost.)\n \nIf you want to help make the web better, you could literally start with Sir Tim Berners-Lee's Wikipedia page, and use it as the basis to spend a decade pushing for HTML markup improvements. It could be the start of a long and successful career."
},
"name": "Can someone add some more HTML tags, please?",
"post-type": "article",
"_id": "17522110",
"_source": "238",
"_is_read": true
}
