Good morning, IndieWeb! We’ve got a meetup this Wednesday in Austin, at Radio Coffee & Beer. You can RSVP here or just show up. ☕️🍺
{
"type": "entry",
"author": {
"name": "Manton Reece",
"url": "https://www.manton.org/",
"photo": "https://micro.blog/manton/avatar.jpg"
},
"url": "https://www.manton.org/2025/01/13/good-morning-indieweb-weve-got.html",
"content": {
"html": "<p>Good morning, IndieWeb! We\u2019ve got a meetup this Wednesday in Austin, at Radio Coffee & Beer. You can <a href=\"https://events.indieweb.org/2025/01/indieweb-meetup-austin-zFL9jqPFAgIK\">RSVP here</a> or just show up. \u2615\ufe0f\ud83c\udf7a</p>",
"text": "Good morning, IndieWeb! We\u2019ve got a meetup this Wednesday in Austin, at Radio Coffee & Beer. You can RSVP here or just show up. \u2615\ufe0f\ud83c\udf7a"
},
"published": "2025-01-13T08:27:45-06:00",
"category": [
"Coffee"
],
"post-type": "note",
"_id": "43528110",
"_source": "12",
"_is_read": false
}
The Mastodon instance I'm on, #IndieWeb, has reacted to the #Threads moderation reduction announcement by limiting the discoverability of Threads on IndieWeb. Essentially, if you choose to follow a Threads user's federated output, cool. But nobody is going to stumble on any Threads content - they'll have to purposely bring it in on a case-by-case basis. This is level one containment - the next level is blocking Threads permanently. It's not a complex system, but it works.
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://indieweb.social/@AndySocial/113821899391451681",
"content": {
"html": "<p>The Mastodon instance I'm on, <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a>, has reacted to the <a href=\"https://indieweb.social/tags/Threads\">#<span>Threads</span></a> moderation reduction announcement by limiting the discoverability of Threads on IndieWeb. Essentially, if you choose to follow a Threads user's federated output, cool. But nobody is going to stumble on any Threads content - they'll have to purposely bring it in on a case-by-case basis. This is level one containment - the next level is blocking Threads permanently. It's not a complex system, but it works.</p>",
"text": "The Mastodon instance I'm on, #IndieWeb, has reacted to the #Threads moderation reduction announcement by limiting the discoverability of Threads on IndieWeb. Essentially, if you choose to follow a Threads user's federated output, cool. But nobody is going to stumble on any Threads content - they'll have to purposely bring it in on a case-by-case basis. This is level one containment - the next level is blocking Threads permanently. It's not a complex system, but it works."
},
"published": "2025-01-13T16:05:53+00:00",
"post-type": "note",
"_id": "43528040",
"_source": "8007",
"_is_read": false
}
Back to filling in earlier years on my online gallery. New drawings get shoved in there regularly, but until now I had only uploaded everything as old as 2020 (and then a random assortment of drawings going back to the '90s). Now I'm working on 2019! It looks like that's when I moved away from mostly pencil to an all-digital workflow on a tablet PC.
They're here, and there'll be more as I keep updating:
https://bigraccoon.ca/gallery?tag=Year%3A%202019
#PersonalSites #IndieWeb #MastoArt
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.art/@jsstaedtler/113821705547400745",
"content": {
"html": "<p>Back to filling in earlier years on my online gallery. New drawings get shoved in there regularly, but until now I had only uploaded everything as old as 2020 (and then a random assortment of drawings going back to the '90s). Now I'm working on 2019! It looks like that's when I moved away from mostly pencil to an all-digital workflow on a tablet PC.</p><p>They're here, and there'll be more as I keep updating:<br /><a href=\"https://bigraccoon.ca/gallery?tag=Year%3A%202019\"><span>https://</span><span>bigraccoon.ca/gallery?tag=Year</span><span>%3A%202019</span></a></p><p><a href=\"https://mastodon.art/tags/PersonalSites\">#<span>PersonalSites</span></a> <a href=\"https://mastodon.art/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://mastodon.art/tags/MastoArt\">#<span>MastoArt</span></a></p>",
"text": "Back to filling in earlier years on my online gallery. New drawings get shoved in there regularly, but until now I had only uploaded everything as old as 2020 (and then a random assortment of drawings going back to the '90s). Now I'm working on 2019! It looks like that's when I moved away from mostly pencil to an all-digital workflow on a tablet PC.\n\nThey're here, and there'll be more as I keep updating:\nhttps://bigraccoon.ca/gallery?tag=Year%3A%202019\n\n#PersonalSites #IndieWeb #MastoArt"
},
"published": "2025-01-13T15:16:35+00:00",
"photo": [
"https://files.mastodon.social/cache/media_attachments/files/113/821/705/674/223/517/original/e1b4c0160cbcb44e.png"
],
"post-type": "photo",
"_id": "43527494",
"_source": "8007",
"_is_read": false
}
Spent most of the day on the frontend of my website. Happy so far. You can check it out here: https://mariobreskic.de/
Had to remove the #webmentions plugin because, really? Who needs it.
Now, with that out of the way, I can get back to my actual work.
Also, as you can most likely tell from reading https://codeandcanvas.tumblr.com/post/772571059280068608/log-004-exit I’ve decided to get rid of Firefox, ad blocking, telemetry denial, and so forth, because it is an absolute waste of time, psychic energy, and turns you into an utter wimp!
{
"type": "entry",
"author": {
"name": "#webmentions",
"url": "https://mastodon.social/tags/webmentions",
"photo": null
},
"url": "https://mastodon.mariobreskic.de/@mario/113821707258259583",
"content": {
"html": "<p>Spent most of the day on the frontend of my website. Happy so far. You can check it out here: <a href=\"https://mariobreskic.de/\"><span>https://</span><span>mariobreskic.de/</span><span></span></a></p><p>Had to remove the <a href=\"https://mastodon.mariobreskic.de/tags/webmentions\">#<span>webmentions</span></a> plugin because, really? Who needs it.<br />Now, with that out of the way, I can get back to my actual work.</p><p>Also, as you can most likely tell from reading <a href=\"https://codeandcanvas.tumblr.com/post/772571059280068608/log-004-exit\"><span>https://</span><span>codeandcanvas.tumblr.com/post/</span><span>772571059280068608/log-004-exit</span></a> I\u2019ve decided to get rid of Firefox, ad\u00a0blocking, telemetry\u00a0denial, and so forth, because it is an absolute waste of time, psychic energy, and turns you into an utter wimp!</p>",
"text": "Spent most of the day on the frontend of my website. Happy so far. You can check it out here: https://mariobreskic.de/\n\nHad to remove the #webmentions plugin because, really? Who needs it.\nNow, with that out of the way, I can get back to my actual work.\n\nAlso, as you can most likely tell from reading https://codeandcanvas.tumblr.com/post/772571059280068608/log-004-exit I\u2019ve decided to get rid of Firefox, ad\u00a0blocking, telemetry\u00a0denial, and so forth, because it is an absolute waste of time, psychic energy, and turns you into an utter wimp!"
},
"published": "2025-01-13T15:17:01+00:00",
"post-type": "note",
"_id": "43527495",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"published": "2025-01-13T14:22:08+00:00",
"url": "https://werd.io/2025/free-our-feeds",
"category": [
"Fediverse"
],
"bookmark-of": [
"https://freeourfeeds.com/"
],
"name": "Free Our Feeds",
"content": {
"text": "[Free Our Feeds]\n\nThe non-profit social media foundation space is really heating up. Which is not a bad thing!\n\nEnter Free our Feeds:\n\"It will take independent funding and governance to turn Bluesky\u2019s underlying tech\u2014the AT Protocol\u2014into something more powerful than a single app. We want to create an entire ecosystem of interconnected apps and different companies that have people\u2019s interests at heart.\nFree Our Feeds will build a new, independent foundation to help make that happen.\"\nThe names involved in this particular venture are really fascinating. Nabiha Syed is the ED of the Mozilla Foundation and is joined by Mark Surman, its President; Robin Berjon has done some of the most important writing and thinking in this space, particularly with respect to governance; Eli Pariser is an experienced activist who co-founded Avaaz and used to run MoveOn; Mallory Knodel is the ED of the ActivityPub-centric Social Web Foundation.\n\nAnd then the signatories to the letter are people like Jimmy Wales, Mark Ruffalo, Cory Doctorow, Roger McNamee, Shoshana Zuboff and Audrey Tang.\n\nSo the Social Web Foundation is ActivityPub-centric and Free Our Feeds is AT Protocol-centric. My (figurative) money is increasingly on A New Social, which posits that all these individual protocols and sub-networks will ultimately be universally addressable as one social internet, and is backing tools to help make that happen.\n\nIt's all wonderful. It's all such a great change from the old model - and in a week where Zuckerberg went \"full Musk\", the timing couldn't be better.\n#Fediverse\n [Link]",
"html": "<p>[<a href=\"https://freeourfeeds.com/\">Free Our Feeds</a>]</p><p>The non-profit social media foundation space is really heating up. Which is not a bad thing!</p><p>Enter <a href=\"https://freeourfeeds.com/\">Free our Feeds</a>:</p><blockquote>\n<p>\"It will take independent funding and governance to turn Bluesky\u2019s underlying tech\u2014the AT Protocol\u2014into something more powerful than a single app. We want to create an entire ecosystem of interconnected apps and different companies that have people\u2019s interests at heart.</p>\n<p>Free Our Feeds will build a new, independent foundation to help make that happen.\"</p>\n</blockquote><p>The names involved in this particular venture are really fascinating. Nabiha Syed is the ED of the Mozilla Foundation and is joined by Mark Surman, its President; Robin Berjon has done some of the most important writing and thinking in this space, particularly with respect to governance; Eli Pariser is an experienced activist who co-founded Avaaz and used to run MoveOn; Mallory Knodel is the ED of the ActivityPub-centric Social Web Foundation.</p><p>And then the signatories to the letter are people like Jimmy Wales, Mark Ruffalo, Cory Doctorow, Roger McNamee, Shoshana Zuboff and Audrey Tang.</p><p>So the Social Web Foundation is ActivityPub-centric and Free Our Feeds is AT Protocol-centric. My (figurative) money is increasingly on <a href=\"https://www.anew.social/\">A New Social</a>, which posits that all these individual protocols and sub-networks will ultimately be universally addressable as one social internet, and is backing tools to help make that happen.</p><p>It's all wonderful. It's all such a great change from the old model - and in a week where Zuckerberg went \"full Musk\", the timing couldn't be better.</p>\n<p><a href=\"https://werd.io/tag/Fediverse\" class=\"p-category\">#Fediverse</a></p>\n <p>[<a href=\"https://freeourfeeds.com/\">Link</a>]</p>"
},
"author": {
"type": "card",
"name": "Ben Werdmuller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "bookmark",
"_id": "43527270",
"_source": "191",
"_is_read": false
}
{
"type": "entry",
"published": "2025-01-13T12:31:43+00:00",
"url": "https://werd.io/2025/the-people-should-own-the-town-square",
"category": [
"Fediverse"
],
"bookmark-of": [
"https://blog.joinmastodon.org/2025/01/the-people-should-own-the-town-square/"
],
"name": "The people should own the town square",
"content": {
"text": "[Mastodon]\n\nMastodon is growing up:\n\"Simply, we are going to transfer ownership of key Mastodon ecosystem and platform components (including name and copyrights, among other assets) to a new non-profit organization, affirming the intent that Mastodon should not be owned or controlled by a single individual.\n[...] We are in the process of a phased transition. First we are establishing a new legal home for Mastodon and transferring ownership and stewardship. We are taking the time to select the appropriate jurisdiction and structure in Europe. Then we will determine which other (subsidiary) legal structures are needed to support operations and sustainability.\"\nEugen, Mastodon's CEO, will not be the leader of this new entity, although it's not yet clear who will be. He's going to focus on product instead.\n\nAnother note, right at the end of this announcement: the non-profit seeks to grow its annual budget to \u20ac5 million. That's a big increase from current levels, but is absolutely needed. It sounds like plans are in place to make that happen.\n\nI'm excited for everyone involved; everyone who uses Mastodon; everyone on the web. Greater competition through a truly federated solution with decentralized ownership is good for everyone. I can't wait to see what happens next.\n#Fediverse\n [Link]",
"html": "<p>[<a href=\"https://blog.joinmastodon.org/2025/01/the-people-should-own-the-town-square/\">Mastodon</a>]</p><p>Mastodon is growing up:</p><blockquote>\n<p>\"Simply, we are going to transfer ownership of key Mastodon ecosystem and platform components (including name and copyrights, among other assets) to a new non-profit organization, affirming the intent that Mastodon should not be owned or controlled by a single individual.</p>\n<p>[...] We are in the process of a phased transition. First we are establishing a new legal home for Mastodon and transferring ownership and stewardship. We are taking the time to select the appropriate jurisdiction and structure in Europe. Then we will determine which other (subsidiary) legal structures are needed to support operations and sustainability.\"</p>\n</blockquote><p>Eugen, Mastodon's CEO, will not be the leader of this new entity, although it's not yet clear who will be. He's going to focus on product instead.</p><p>Another note, right at the end of this announcement: the non-profit seeks to grow its annual budget to \u20ac5 million. That's a big increase from current levels, but is absolutely needed. It sounds like plans are in place to make that happen.</p><p>I'm excited for everyone involved; everyone who uses Mastodon; everyone on the web. Greater competition through a truly federated solution with decentralized ownership is good for everyone. I can't wait to see what happens next.</p>\n<p><a href=\"https://werd.io/tag/Fediverse\" class=\"p-category\">#Fediverse</a></p>\n <p>[<a href=\"https://blog.joinmastodon.org/2025/01/the-people-should-own-the-town-square/\">Link</a>]</p>"
},
"author": {
"type": "card",
"name": "Ben Werdmuller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "bookmark",
"_id": "43526179",
"_source": "191",
"_is_read": false
}
I love full-width websites, I love fixed width websites. I love flex galleries and I love grid galleries. I love plain websites and colourful websites. I love cool skeuomorphic design elements and I love plain, bog-standard webpages. I love clever and loose tag-based navigation and I love organised and well-defined hierarchies. I love painterly graphic elements and I love hard-edged vector elements
in short, my website can't be done because it will always want to be something else
#indieweb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@qxoko/113820961860516074",
"content": {
"html": "<p>I love full-width websites, I love fixed width websites. I love flex galleries and I love grid galleries. I love plain websites and colourful websites. I love cool skeuomorphic design elements and I love plain, bog-standard webpages. I love clever and loose tag-based navigation and I love organised and well-defined hierarchies. I love painterly graphic elements and I love hard-edged vector elements</p><p>in short, my website can't be done because it will always want to be something else</p><p><a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a></p>",
"text": "I love full-width websites, I love fixed width websites. I love flex galleries and I love grid galleries. I love plain websites and colourful websites. I love cool skeuomorphic design elements and I love plain, bog-standard webpages. I love clever and loose tag-based navigation and I love organised and well-defined hierarchies. I love painterly graphic elements and I love hard-edged vector elements\n\nin short, my website can't be done because it will always want to be something else\n\n#indieweb"
},
"published": "2025-01-13T12:07:27+00:00",
"post-type": "note",
"_id": "43525803",
"_source": "8007",
"_is_read": false
}
I really like this little tool I’ve built: it collects all relevant posts from my most active social media accounts in one place, so that fellow goblins can just chill out in it. Comments and #webmentions are also active, so there is always room for goblin notes and scratches in the archive.
{
"type": "entry",
"author": {
"name": "#webmentions",
"url": "https://mastodon.social/tags/webmentions",
"photo": null
},
"url": "https://mastodon.mariobreskic.de/@mario/113820724426683425",
"content": {
"html": "<p>I really like this little tool I\u2019ve built: it collects all relevant posts from my most active social media accounts in one place, so that fellow goblins can just chill out in it. Comments and <a href=\"https://mastodon.mariobreskic.de/tags/webmentions\">#<span>webmentions</span></a> are also active, so there is always room for goblin notes and scratches in the archive.</p>",
"text": "I really like this little tool I\u2019ve built: it collects all relevant posts from my most active social media accounts in one place, so that fellow goblins can just chill out in it. Comments and #webmentions are also active, so there is always room for goblin notes and scratches in the archive."
},
"published": "2025-01-13T11:07:04+00:00",
"post-type": "note",
"_id": "43525463",
"_source": "8007",
"_is_read": false
}
Turning myself into a goblin asking himself what other goblins would like in a social media archive has so far been fungal.
https://social.mariobreskic.de/goblin/2025/01/13/651/
I really like this little tool I’ve built: it collects all relevant posts from my most active social media accounts in one place, so that fellow goblins can just chill out in it. Comments and #webmentions are also active, so there is always room for goblin notes and scratches in the archive.
{
"type": "entry",
"author": {
"name": "#webmentions",
"url": "https://mastodon.social/tags/webmentions",
"photo": null
},
"url": "https://mastodon.mariobreskic.de/@mario/113820613008466413",
"content": {
"html": "<p>Turning myself into a goblin asking himself what other goblins would like in a social\u00a0media\u00a0archive has so far been fungal. </p><p><a href=\"https://social.mariobreskic.de/goblin/2025/01/13/651/\"><span>https://</span><span>social.mariobreskic.de/goblin/</span><span>2025/01/13/651/</span></a></p><p>I really like this little tool I\u2019ve built: it collects all relevant posts from my most active social media accounts in one place, so that fellow goblins can just chill out in it. Comments and <a href=\"https://mastodon.mariobreskic.de/tags/webmentions\">#<span>webmentions</span></a> are also active, so there is always room for goblin notes and scratches in the archive.</p>",
"text": "Turning myself into a goblin asking himself what other goblins would like in a social\u00a0media\u00a0archive has so far been fungal. \n\nhttps://social.mariobreskic.de/goblin/2025/01/13/651/\n\nI really like this little tool I\u2019ve built: it collects all relevant posts from my most active social media accounts in one place, so that fellow goblins can just chill out in it. Comments and #webmentions are also active, so there is always room for goblin notes and scratches in the archive."
},
"published": "2025-01-13T10:38:44+00:00",
"post-type": "note",
"_id": "43525229",
"_source": "8007",
"_is_read": false
}
🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/
As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.
The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, have long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).
There are multiple considerations to keep in mind when displaying such external content.
Two examples of external content are images (e.g. people’s icons or profile images from the author of a comment) and text (e.g. people’s names or the text of their comments).
For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.
If you accept Webmentions from arbitrary sources, there’s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.
For external text, one thing we discovered in recent IndieWeb chat¹ is that someone’s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text.
Fortunately there is a CSS property, 'unicode-bidi', that can be used to directionally isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:
<span style="unicode-bidi: isolate;">parsed text here</span>
Though even better would be use of a generic HTML class name indicating the semantic:
<span class="external-text">parsed text here</span>
and then a CSS rule in your style sheet to add that property (and any others you want for external text)
.external-text { unicode-bidi: isolate; }
Previously: https://tantek.com/2023/012/t1/six-years-webmention-w3c
This is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb
← https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web
→ 🔮
Glossary
HTML class name
https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors
IndieWeb chat
https://indieweb.org/discuss
pixelate
https://indieweb.org/pixelated
small pieces, loosely joined
https://www.smallpieces.com/
Unicode directional formatting characters
https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting
unicode-bidi CSS property
https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi
References
¹ https://chat.indieweb.org/dev/2025-01-05#t1736092889120900
{
"type": "entry",
"published": "2025-01-12 21:23-0800",
"url": "http://tantek.com/2025/012/t1/eight-years-webmention",
"category": [
"IndieWeb",
"Webmention",
"100PostsOfIndieWeb",
"100Posts",
"socialWeb",
"openSocialWeb"
],
"content": {
"text": "\ud83c\udf89 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/\n\nAs a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.\n\nThe primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, have long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).\n\nThere are multiple considerations to keep in mind when displaying such external content.\n\nTwo examples of external content are images (e.g. people\u2019s icons or profile images from the author of a comment) and text (e.g. people\u2019s names or the text of their comments).\n\nFor external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.\n\nIf you accept Webmentions from arbitrary sources, there\u2019s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.\n\nFor external text, one thing we discovered in recent IndieWeb chat\u00b9 is that someone\u2019s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text.\n\nFortunately there is a CSS property, 'unicode-bidi', that can be used to directionally isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:\n\n<span style=\"unicode-bidi: isolate;\">parsed text here</span>\n\nThough even better would be use of a generic HTML class name indicating the semantic:\n\n<span class=\"external-text\">parsed text here</span>\n\nand then a CSS rule in your style sheet to add that property (and any others you want for external text)\n\n.external-text { unicode-bidi: isolate; }\n\nPreviously: https://tantek.com/2023/012/t1/six-years-webmention-w3c\n\n\nThis is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb\n\n\u2190 https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web\n\u2192 \ud83d\udd2e\n\n\nGlossary\n\nHTML class name\n\u00a0 https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors\nIndieWeb chat\n\u00a0 https://indieweb.org/discuss\npixelate\n\u00a0 https://indieweb.org/pixelated\nsmall pieces, loosely joined\n\u00a0 https://www.smallpieces.com/\nUnicode directional formatting characters\n\u00a0 https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting\nunicode-bidi CSS property\n\u00a0 https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi \u00a0\n\n\nReferences\n\n\u00b9 https://chat.indieweb.org/dev/2025-01-05#t1736092889120900",
"html": "\ud83c\udf89 Eight years ago today, the #<span class=\"p-category\">IndieWeb</span> Webmention protocol was published as a W3C REC <a href=\"https://www.w3.org/TR/webmention/\">https://www.w3.org/TR/webmention/</a><br /><br />As a social web building block, #<span class=\"p-category\">Webmention</span> was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.<br /><br />The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, have long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).<br /><br />There are multiple considerations to keep in mind when displaying such external content.<br /><br />Two examples of external content are images (e.g. people\u2019s icons or profile images from the author of a comment) and text (e.g. people\u2019s names or the text of their comments).<br /><br />For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.<br /><br />If you accept Webmentions from arbitrary sources, there\u2019s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.<br /><br />For external text, one thing we discovered in recent IndieWeb chat<a href=\"http://tantek.com/#t5a01_note-1\">\u00b9</a> is that someone\u2019s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text.<br /><br />Fortunately there is a CSS property, 'unicode-bidi', that can be used to directionally isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:<br /><br /><span style=\"unicode-bidi: isolate;\">parsed text here</span><br /><br />Though even better would be use of a generic HTML class name indicating the semantic:<br /><br /><span class=\"external-text\">parsed text here</span><br /><br />and then a CSS rule in your style sheet to add that property (and any others you want for external text)<br /><br />.external-text { unicode-bidi: isolate; }<br /><br />Previously: <a href=\"https://tantek.com/2023/012/t1/six-years-webmention-w3c\">https://tantek.com/2023/012/t1/six-years-webmention-w3c</a><br /><br /><br />This is post 7 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span> #<span class=\"p-category\">socialWeb</span> #<span class=\"p-category\">openSocialWeb</span><br /><br />\u2190 <a href=\"https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web\">https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Glossary<br /><br />HTML class name<br />\u00a0 <a href=\"https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors\">https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors</a><br />IndieWeb chat<br />\u00a0 <a href=\"https://indieweb.org/discuss\">https://indieweb.org/discuss</a><br />pixelate<br />\u00a0 <a href=\"https://indieweb.org/pixelated\">https://indieweb.org/pixelated</a><br />small pieces, loosely joined<br />\u00a0 <a href=\"https://www.smallpieces.com/\">https://www.smallpieces.com/</a><br />Unicode directional formatting characters<br />\u00a0 <a href=\"https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting\">https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting</a><br />unicode-bidi CSS property<br />\u00a0 <a href=\"https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi\">https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi</a> \u00a0<br /><br /><br />References<br /><br /><a href=\"http://tantek.com/#t5a01_ref-1\">\u00b9</a> <a href=\"https://chat.indieweb.org/dev/2025-01-05#t1736092889120900\">https://chat.indieweb.org/dev/2025-01-05#t1736092889120900</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "43524564",
"_source": "1",
"_is_read": false
}
ð Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webme... tantek.com
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://tantek.com/2025/012/t1/eight-years-webmention",
"content": {
"html": "\u00f0 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webme... <a href=\"https://tantek.com/2025/012/t1/eight-years-webmention\">tantek.com</a>",
"text": "\u00f0 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webme... tantek.com"
},
"published": "2025-01-13T05:23:00+00:00",
"post-type": "note",
"_id": "43523957",
"_source": "8007",
"_is_read": false
}
🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/
As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.
The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, have long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).
There are multiple considerations to keep in mind when displaying such external content.
Two examples of external content are images (e.g. people’s icons or profile images from the author of a comment) and text (e.g. people’s names or the text of their comments).
For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.
If you accept Webmentions from arbitrary sources, there’s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.
For external text, one thing we discovered in recent IndieWeb chat¹ is that someone’s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text.
Fortunately there is a CSS property, 'unicode-bidi', that can be used to directionally isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:
<span style="unicode-bidi: isolate;">parsed text here</span>
Though even better would be use of a generic HTML class name indicating the semantic:
<span class="external-text">parsed text here</span>
and then a CSS rule in your style sheet to add that property (and any others you want for external text)
.external-text { unicode-bidi: isolate; }
Previously: https://tantek.com/2023/012/t1/six-years-webmention-w3c
This is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb
← https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web
→ 🔮
Glossary
HTML class name
https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors
IndieWeb chat
https://indieweb.org/discuss
pixelate
https://indieweb.org/pixelated
small pieces, loosely joined
https://www.smallpieces.com/
Unicode directional formatting characters
https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting
unicode-bidi CSS property
https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi
References
¹ https://chat.indieweb.org/dev/2025-01-05#t1736092889120900
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2025/012/t1/eight-years-webmention",
"content": {
"html": "<p>\ud83c\udf89 Eight years ago today, the <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> Webmention protocol was published as a W3C REC <a href=\"https://www.w3.org/TR/webmention/\">https://www.w3.org/TR/webmention/</a><br /><br />As a social web building block, <a href=\"https://indieweb.social/tags/Webmention\">#<span class=\"p-category\">Webmention</span></a> was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.<br /><br />The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, have long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).<br /><br />There are multiple considerations to keep in mind when displaying such external content.<br /><br />Two examples of external content are images (e.g. people\u2019s icons or profile images from the author of a comment) and text (e.g. people\u2019s names or the text of their comments).<br /><br />For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.<br /><br />If you accept Webmentions from arbitrary sources, there\u2019s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.<br /><br />For external text, one thing we discovered in recent IndieWeb chat<a href=\"https://tantek.com/2025/012/t1/eight-years-webmention#t5a01_note-1\">\u00b9</a> is that someone\u2019s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text.<br /><br />Fortunately there is a CSS property, 'unicode-bidi', that can be used to directionally isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:<br /><br /><span style=\"unicode-bidi: isolate;\">parsed text here</span><br /><br />Though even better would be use of a generic HTML class name indicating the semantic:<br /><br /><span class=\"external-text\">parsed text here</span><br /><br />and then a CSS rule in your style sheet to add that property (and any others you want for external text)<br /><br />.external-text { unicode-bidi: isolate; }<br /><br />Previously: <a href=\"https://tantek.com/2023/012/t1/six-years-webmention-w3c\">https://tantek.com/2023/012/t1/six-years-webmention-w3c</a><br /><br /><br />This is post 7 of <a href=\"https://indieweb.social/tags/100PostsOfIndieWeb\">#<span class=\"p-category\">100PostsOfIndieWeb</span></a>. <a href=\"https://indieweb.social/tags/100Posts\">#<span class=\"p-category\">100Posts</span></a> <a href=\"https://indieweb.social/tags/socialWeb\">#<span class=\"p-category\">socialWeb</span></a> <a href=\"https://indieweb.social/tags/openSocialWeb\">#<span class=\"p-category\">openSocialWeb</span></a><br /><br />\u2190 <a href=\"https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web\">https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web</a><br />\u2192 \ud83d\udd2e<br /><br /><br />Glossary<br /><br />HTML class name<br />\u00a0 <a href=\"https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors\">https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors</a><br />IndieWeb chat<br />\u00a0 <a href=\"https://indieweb.org/discuss\">https://indieweb.org/discuss</a><br />pixelate<br />\u00a0 <a href=\"https://indieweb.org/pixelated\">https://indieweb.org/pixelated</a><br />small pieces, loosely joined<br />\u00a0 <a href=\"https://www.smallpieces.com/\">https://www.smallpieces.com/</a><br />Unicode directional formatting characters<br />\u00a0 <a href=\"https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting\">https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting</a><br />unicode-bidi CSS property<br />\u00a0 <a href=\"https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi\">https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi</a> \u00a0<br /><br /><br />References<br /><br /><a href=\"https://tantek.com/2025/012/t1/eight-years-webmention#t5a01_ref-1\">\u00b9</a> <a href=\"https://chat.indieweb.org/dev/2025-01-05#t1736092889120900\">https://chat.indieweb.org/dev/2025-01-05#t1736092889120900</a></p>",
"text": "\ud83c\udf89 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/\n\nAs a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.\n\nThe primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, have long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).\n\nThere are multiple considerations to keep in mind when displaying such external content.\n\nTwo examples of external content are images (e.g. people\u2019s icons or profile images from the author of a comment) and text (e.g. people\u2019s names or the text of their comments).\n\nFor external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.\n\nIf you accept Webmentions from arbitrary sources, there\u2019s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.\n\nFor external text, one thing we discovered in recent IndieWeb chat\u00b9 is that someone\u2019s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text.\n\nFortunately there is a CSS property, 'unicode-bidi', that can be used to directionally isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:\n\n<span style=\"unicode-bidi: isolate;\">parsed text here</span>\n\nThough even better would be use of a generic HTML class name indicating the semantic:\n\n<span class=\"external-text\">parsed text here</span>\n\nand then a CSS rule in your style sheet to add that property (and any others you want for external text)\n\n.external-text { unicode-bidi: isolate; }\n\nPreviously: https://tantek.com/2023/012/t1/six-years-webmention-w3c\n\n\nThis is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb\n\n\u2190 https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web\n\u2192 \ud83d\udd2e\n\n\nGlossary\n\nHTML class name\n\u00a0 https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors\nIndieWeb chat\n\u00a0 https://indieweb.org/discuss\npixelate\n\u00a0 https://indieweb.org/pixelated\nsmall pieces, loosely joined\n\u00a0 https://www.smallpieces.com/\nUnicode directional formatting characters\n\u00a0 https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting\nunicode-bidi CSS property\n\u00a0 https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi \u00a0\n\n\nReferences\n\n\u00b9 https://chat.indieweb.org/dev/2025-01-05#t1736092889120900"
},
"published": "2025-01-13T05:23:00+00:00",
"post-type": "note",
"_id": "43523958",
"_source": "8007",
"_is_read": false
}
My list of articles worth of reading https://w3blogy.cz/ has now author attribution, abstract and tags. Every article from my Feedly feed is enhanced with semantic data extracted from the page. I have many layers of fallbacks to get the best data I can. #indieweb #semanticweb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://indieweb.social/@alesroubicek/113819462328102072",
"content": {
"html": "<p>My list of articles worth of reading <a href=\"https://w3blogy.cz/\"><span>https://</span><span>w3blogy.cz/</span><span></span></a> has now author attribution, abstract and tags. Every article from my Feedly feed is enhanced with semantic data extracted from the page. I have many layers of fallbacks to get the best data I can. <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://indieweb.social/tags/semanticweb\">#<span>semanticweb</span></a></p>",
"text": "My list of articles worth of reading https://w3blogy.cz/ has now author attribution, abstract and tags. Every article from my Feedly feed is enhanced with semantic data extracted from the page. I have many layers of fallbacks to get the best data I can. #indieweb #semanticweb"
},
"published": "2025-01-13T05:46:06+00:00",
"post-type": "note",
"_id": "43523485",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"published": "2025-01-13T02:22:56+00:00",
"url": "https://werd.io/2025/content-policy-on-the-social-web",
"category": [
"Fediverse"
],
"bookmark-of": [
"https://socialwebfoundation.org/2025/01/12/content-policy-on-the-social-web/"
],
"name": "Content Policy on the Social Web",
"content": {
"text": "[Social Web Foundation]\n\nThe Social Web Foundation's statement about Meta's moderation changes is important:\n\"Ideas matter, and history shows that online misinformation and harassment can lead to violence in the real world.\n[...] Meta is one of many ActivityPub implementers and a supporter of the Social Web Foundation. We strongly encourage Meta\u2019s executive and content teams to come back in line with best practices of a zero harm social media ecosystem. Reconsidering this policy change would preserve the crucial distinction between political differences of opinion and dehumanizing harassment. The SWF is available to discuss Meta\u2019s content moderation policies and processes to make them more humane and responsible.\"\nThis feels right to me. By implication: the current policies are inhumane and irresponsible. And as such, worth calling out.\n#Fediverse\n [Link]",
"html": "<p>[<a href=\"https://socialwebfoundation.org/2025/01/12/content-policy-on-the-social-web/\">Social Web Foundation</a>]</p><p><a href=\"https://socialwebfoundation.org/\">The Social Web Foundation</a>'s statement about Meta's moderation changes is important:</p><blockquote>\n<p>\"Ideas matter, and history shows that online misinformation and harassment can lead to violence in the real world.</p>\n<p>[...] Meta is one of many ActivityPub implementers and a supporter of the Social Web Foundation. We strongly encourage Meta\u2019s executive and content teams to come back in line with best practices of a zero harm social media ecosystem. Reconsidering this policy change would preserve the crucial distinction between political differences of opinion and dehumanizing harassment. The SWF is available to discuss Meta\u2019s content moderation policies and processes to make them more humane and responsible.\"</p>\n</blockquote><p>This feels right to me. By implication: <a href=\"https://www.theverge.com/2025/1/7/24338471/meta-hate-speech-hateful-conduct-policy-moderation\">the current policies</a> are inhumane and irresponsible. And as such, worth calling out.</p>\n<p><a href=\"https://werd.io/tag/Fediverse\" class=\"p-category\">#Fediverse</a></p>\n <p>[<a href=\"https://socialwebfoundation.org/2025/01/12/content-policy-on-the-social-web/\">Link</a>]</p>"
},
"author": {
"type": "card",
"name": "Ben Werdmuller",
"url": "https://werd.io/profile/benwerd",
"photo": "https://werd.io/file/5d388c5fb16ea14aac640912/thumb.jpg"
},
"post-type": "bookmark",
"_id": "43522602",
"_source": "191",
"_is_read": false
}
Nesse sentido o mais avançado parece ser o https://atabook.org/
Vi também umas paradas que tu bota que dá pra visualizar o mouse de quem mais estiver online ao mesmo tempo na página.
Será que existem outras coisas?
#indieWeb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://bolha.us/@guites/113818578769518446",
"content": {
"html": "<p>Nesse sentido o mais avan\u00e7ado parece ser o <a href=\"https://atabook.org/\"><span>https://</span><span>atabook.org/</span><span></span></a> </p><p>Vi tamb\u00e9m umas paradas que tu bota que d\u00e1 pra visualizar o mouse de quem mais estiver online ao mesmo tempo na p\u00e1gina.</p><p>Ser\u00e1 que existem outras coisas?</p><p><a href=\"https://bolha.us/tags/indieWeb\">#<span>indieWeb</span></a></p>",
"text": "Nesse sentido o mais avan\u00e7ado parece ser o https://atabook.org/ \n\nVi tamb\u00e9m umas paradas que tu bota que d\u00e1 pra visualizar o mouse de quem mais estiver online ao mesmo tempo na p\u00e1gina.\n\nSer\u00e1 que existem outras coisas?\n\n#indieWeb"
},
"published": "2025-01-13T02:01:24+00:00",
"post-type": "note",
"_id": "43522487",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://caneandable.social/@WeirdWriter/113818153631402970",
"content": {
"html": "<p>A series of posts on why the right wing likes the indie web, or small web, as it were and how they are taking advantage of the indieweb to push hate.</p><p>part 1 <a href=\"https://blog.avas.space/the-web-revival-harmful-ideas/\"><span>https://</span><span>blog.avas.space/the-web-reviva</span><span>l-harmful-ideas/</span></a></p><p>part 2 <a href=\"https://web.archive.org/web/20231206041729/https://daintyeco.smol.pub/webrevivalharmfulideaspart2\"><span>https://</span><span>web.archive.org/web/2023120604</span><span>1729/https://daintyeco.smol.pub/webrevivalharmfulideaspart2</span></a></p><p>RELATED. RageBate in the indieweb <a href=\"https://blog.avas.space/rage-bait/\"><span>https://</span><span>blog.avas.space/rage-bait/</span><span></span></a></p><p><a href=\"https://caneandable.social/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://caneandable.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://caneandable.social/tags/Internet\">#<span>Internet</span></a> <a href=\"https://caneandable.social/tags/WebRevival\">#<span>WebRevival</span></a></p>",
"text": "A series of posts on why the right wing likes the indie web, or small web, as it were and how they are taking advantage of the indieweb to push hate.\n\npart 1 https://blog.avas.space/the-web-revival-harmful-ideas/\n\npart 2 https://web.archive.org/web/20231206041729/https://daintyeco.smol.pub/webrevivalharmfulideaspart2\n\nRELATED. RageBate in the indieweb https://blog.avas.space/rage-bait/\n\n#SmallWeb #IndieWeb #Internet #WebRevival"
},
"published": "2025-01-13T00:13:17+00:00",
"post-type": "note",
"_id": "43521873",
"_source": "8007",
"_is_read": false
}
I'm working on a web component for embedding youtube videos. I'm setting it up to use the parent page's stylesheet. If I put the custom element on the page in the `<main>` element everything work as expected. If I move the custom element inside a `<section>` tag the styles get messed up. I spent an hour on it and made no progress. This page shows what's going on if that kind of puzzle appeals to you:
https://yt-player.alanwsmith.com/issue/
#WebDev #WebComponents #IndieWeb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://hachyderm.io/@TheIdOfAlan/113817938769180286",
"content": {
"html": "<p>I'm working on a web component for embedding youtube videos. I'm setting it up to use the parent page's stylesheet. If I put the custom element on the page in the `<main>` element everything work as expected. If I move the custom element inside a `<section>` tag the styles get messed up. I spent an hour on it and made no progress. This page shows what's going on if that kind of puzzle appeals to you: </p><p><a href=\"https://yt-player.alanwsmith.com/issue/\"><span>https://</span><span>yt-player.alanwsmith.com/issue</span><span>/</span></a></p><p><a href=\"https://hachyderm.io/tags/WebDev\">#<span>WebDev</span></a> <a href=\"https://hachyderm.io/tags/WebComponents\">#<span>WebComponents</span></a> <a href=\"https://hachyderm.io/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
"text": "I'm working on a web component for embedding youtube videos. I'm setting it up to use the parent page's stylesheet. If I put the custom element on the page in the `<main>` element everything work as expected. If I move the custom element inside a `<section>` tag the styles get messed up. I spent an hour on it and made no progress. This page shows what's going on if that kind of puzzle appeals to you: \n\nhttps://yt-player.alanwsmith.com/issue/\n\n#WebDev #WebComponents #IndieWeb"
},
"published": "2025-01-12T23:18:39+00:00",
"post-type": "note",
"_id": "43521506",
"_source": "8007",
"_is_read": false
}
This is super exciting, and I look forward to having my blog be fully federated this year!
https://activitypub.ghost.org/the-story-so-far/
#Technology #GhostCMS #Blog #Fediverse #IndieWeb
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://indieweb.social/@countablenewt/113817012561543227",
"content": {
"html": "<p>This is super exciting, and I look forward to having my blog be fully federated this year!</p><p><a href=\"https://activitypub.ghost.org/the-story-so-far/\"><span>https://</span><span>activitypub.ghost.org/the-stor</span><span>y-so-far/</span></a></p><p><a href=\"https://indieweb.social/tags/Technology\">#<span>Technology</span></a> <a href=\"https://indieweb.social/tags/GhostCMS\">#<span>GhostCMS</span></a> <a href=\"https://indieweb.social/tags/Blog\">#<span>Blog</span></a> <a href=\"https://indieweb.social/tags/Fediverse\">#<span>Fediverse</span></a> <a href=\"https://indieweb.social/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
"text": "This is super exciting, and I look forward to having my blog be fully federated this year!\n\nhttps://activitypub.ghost.org/the-story-so-far/\n\n#Technology #GhostCMS #Blog #Fediverse #IndieWeb"
},
"published": "2025-01-12T19:23:06+00:00",
"post-type": "note",
"_id": "43519661",
"_source": "8007",
"_is_read": false
}
🔗 Range via @louie #Indieweb #Blogging #Rss
Whenever I beat the RSS drum, someone always asks about discoverability, so I want to put this bluntly: it is through algorithmic discoverability features that harmful posts become visible. Whether they are original posts, reposts, or replies, harmful posts are only able to successfully reach their intended audience by depending on those features functioning as social media websites built them.
https://lmnt.me/blog/range.html
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://follow.coryd.dev/@cory/113816981741644034",
"content": {
"html": "<p>\ud83d\udd17 Range via <span class=\"h-card\"><a class=\"u-url\" href=\"https://pdx.social/@louie\">@<span>louie</span></a></span> <a href=\"https://follow.coryd.dev/tags/Indieweb\">#<span>Indieweb</span></a> <a href=\"https://follow.coryd.dev/tags/Blogging\">#<span>Blogging</span></a> <a href=\"https://follow.coryd.dev/tags/Rss\">#<span>Rss</span></a></p><p>Whenever I beat the RSS drum, someone always asks about discoverability, so I want to put this bluntly: it is through algorithmic discoverability features that harmful posts become visible. Whether they are original posts, reposts, or replies, harmful posts are only able to successfully reach their intended audience by depending on those features functioning as social media websites built them.</p><p><a href=\"https://lmnt.me/blog/range.html\"><span>https://</span><span>lmnt.me/blog/range.html</span><span></span></a></p>\n<a class=\"u-mention\" href=\"https://pdx.social/@louie\"></a>",
"text": "\ud83d\udd17 Range via @louie #Indieweb #Blogging #Rss\n\nWhenever I beat the RSS drum, someone always asks about discoverability, so I want to put this bluntly: it is through algorithmic discoverability features that harmful posts become visible. Whether they are original posts, reposts, or replies, harmful posts are only able to successfully reach their intended audience by depending on those features functioning as social media websites built them.\n\nhttps://lmnt.me/blog/range.html"
},
"published": "2025-01-12T19:15:16+00:00",
"post-type": "note",
"_id": "43519662",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodontech.de/@jak2k/113816864258554466",
"content": {
"html": "<p>I now have a <a href=\"https://mastodontech.de/tags/wiki\">#<span>wiki</span></a>:</p><p><a href=\"https://jak2k.schwanenberg.name/post/wiki/\"><span>https://</span><span>jak2k.schwanenberg.name/post/w</span><span>iki/</span></a></p><p><a href=\"https://mastodontech.de/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodontech.de/tags/web\">#<span>web</span></a> <a href=\"https://mastodontech.de/tags/PersonalSites\">#<span>PersonalSites</span></a> <a href=\"https://mastodontech.de/tags/personalwiki\">#<span>personalwiki</span></a></p>",
"text": "I now have a #wiki:\n\nhttps://jak2k.schwanenberg.name/post/wiki/\n\n#indieweb #web #PersonalSites #personalwiki"
},
"published": "2025-01-12T18:45:23+00:00",
"post-type": "note",
"_id": "43519389",
"_source": "8007",
"_is_read": false
}
