status.blaise.ca
type: Site
name: stadeus
space of: indiewebdev

indiewebdev
type: Container
type: channel
description: Updates tagged with indiewebdev on stadeus!
licence: http://creativecommons.org/licenses/by/3.0/
items: simple-embeds
items: greshams-law-developers-users-jargon
items: gresham-law-developers-users-jargon
items: posse-indieweb-twitter-facebook

simple-embeds
type: item
type: MicroblogPost
title: : Last week at a #HomebrewWebsiteClub session¹ I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots.I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things:1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe.2. A way to “Follow Your Nose” discover that separate embed version3. A way to discover the original post from the embedded versionFor (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice.For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly².For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink.Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service!https://indieweb.org/embed#IndieWeb_ExamplesI have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together.Got other ideas for simple embeds? Want to implement them on your own site?Join us in the #indiewebdev chat: https://chat.indieweb.org/devUPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages). A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2Glossaryembed https://indieweb.org/embedFollow Your Nose https://indieweb.org/follow_your_noseh-entry https://microformats.org/wiki/h-entryoEm…
link: https://status.blaise.ca/notice/116234
description: 's status on Friday, 01-Nov-2024 17:33:00 EDT
encoded: Last week at a #HomebrewWebsiteClub session¹ I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots. I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things: 1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe. 2. A way to “Follow Your Nose” discover that separate embed version 3. A way to discover the original post from the embedded version For (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice. For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly². For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink. Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service! https://indieweb.org/embed#IndieWeb_Examples I have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together. Got other ideas for simple embeds? Want to implement them on your own site? Join us in the #indiewebdev chat: https://chat.indieweb.org/dev UPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages). A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2 Glossary embed https://indieweb.org/embed Follow Your Nose https://indieweb.org/follow_your_nose h-entry https://microformats.org/…
date: 2024-11-01T17:33:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110303
enclosure: libre.fm
links to: libre.fm
enclosure: devUPDATE:
links to: devUPDATE:
enclosure: t2Glossaryembed
links to: t2Glossaryembed
enclosure: embedFollow
links to: embedFollow
enclosure: follow your noseh-entry
links to: follow your noseh-entry
enclosure: h-entryoEmbed
links to: h-entryoEmbed
enclosure: oEmbedrel-canonical
links to: oEmbedrel-canonical
enclosure: rel-canonicalstatic
links to: rel-canonicalstatic
enclosure: static web hostingReferences
links to: static web hostingReferences
enclosure: embedding²
links to: embedding²
enclosure: rel-embedThis
links to: rel-embedThis
enclosure: fediverse-unfollow-bridgyfed-bug
links to: fediverse-unfollow-bridgyfed-bug
tagged: concept

libre.fm
date: 2024-11-01T20:03:07-04:00
type: text/html; charset=utf-8

devUPDATE:
date: 2024-11-01T20:03:08-04:00
length: 169
type: text/html

t2Glossaryembed
date: 2024-11-01T20:03:08-04:00
type: text/html; charset=UTF-8

embedFollow
date: 2024-11-01T20:03:09-04:00
type: text/html; charset=UTF-8

follow your noseh-entry
date: 2024-11-01T20:03:10-04:00
type: text/html; charset=UTF-8

h-entryoEmbed
date: 2024-11-01T20:03:11-04:00
type: text/html; charset=UTF-8

oEmbedrel-canonical
date: 2024-11-01T20:03:12-04:00
type: text/html; charset=UTF-8

rel-canonicalstatic
date: 2024-11-01T20:03:12-04:00
type: text/html; charset=UTF-8

static web hostingReferences
date: 2024-11-01T20:03:13-04:00
type: text/html; charset=UTF-8

embedding²
date: 2024-11-01T20:03:14-04:00
type: text/html; charset=UTF-8

rel-embedThis
date: 2024-11-01T20:03:16-04:00
type: text/html; charset=UTF-8

fediverse-unfollow-bridgyfed-bug
date: 2024-11-01T20:03:17-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: 100posts

concept
type: Tag
label: 100postsofindieweb

concept
type: Tag
label: homebrewwebsiteclub

concept
type: Tag
label: indieweb

concept
type: Tag
label: indiewebdev

greshams-law-developers-users-jargon
type: item
type: MicroblogPost
title: : Similar to @paulgraham.com (@paulg@mas.to @paulg)’s 2008 observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak.Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum.The #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details.It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technica…
link: https://status.blaise.ca/notice/116166
description: 's status on Sunday, 04-Feb-2024 18:05:00 EST
encoded: Similar to @paulgraham.com (@paulg@mas.to @paulg)’s 2008 observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak. Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return. Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided. Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum. The #IndieWeb community started in 2011 as a single #indiewebcamp IRC channel (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details. It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics. As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon. The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started tec…
date: 2024-02-04T18:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110239
enclosure: indieweb-for-everyone-internet-of-people
links to: indieweb-for-everyone-internet-of-people
enclosure: earthquake-sanfrancisco-shifted
links to: earthquake-sanfrancisco-shifted
enclosure: IndieWebIndieWebCamp
links to: IndieWebIndieWebCamp
enclosure: jargonLoqi
links to: jargonLoqi
enclosure: Loqimain
links to: Loqimain
enclosure: metaMediaWiki
links to: metaMediaWiki
enclosure: Project:Categoriesplumbing
links to: Project:Categoriesplumbing
enclosure: plumbingprotocol
links to: plumbingprotocol
enclosure: silos¹
links to: silos¹
enclosure: Email³
links to: Email³
enclosure: make what you need⁴
links to: make what you need⁴
enclosure: use what you make⁵
links to: use what you make⁵
enclosure: rename to IndieWeb⁶
links to: rename to IndieWeb⁶
enclosure: jargon⁷
links to: jargon⁷
enclosure: Loqi Nudge⁸
links to: Loqi Nudge⁸
enclosure: Chat Channels Purposes⁹
links to: Chat Channels Purposes⁹
enclosure: t1705883690759800
links to: t1705883690759800
enclosure: devDiscord
links to: devDiscord
enclosure: Discordformat
links to: Discordformat
enclosure: formatHacker
links to: formatHacker
enclosure: Hacker NewsIndieWeb
links to: Hacker NewsIndieWeb
enclosure: IndieWebCampIRC
links to: IndieWebCampIRC
enclosure: IRCjargon
links to: IRCjargon
enclosure: indiewebMatrix
links to: indiewebMatrix
enclosure: Matrixmeta
links to: Matrixmeta
enclosure: protocolReddit
links to: protocolReddit
enclosure: Reddittools
links to: Reddittools
enclosure: toolsSlack
links to: toolsSlack
enclosure: Slacksocial
links to: Slacksocial
enclosure: trolls.html
links to: trolls.html
tagged: concept

indieweb-for-everyone-internet-of-people
date: 2024-01-27T06:09:55-05:00
type: text/html; charset=UTF-8

earthquake-sanfrancisco-shifted
date: 2024-02-04T21:30:22-05:00
type: text/html; charset=UTF-8

IndieWebIndieWebCamp
date: 2024-02-04T21:30:25-05:00
type: text/html; charset=UTF-8

jargonLoqi
date: 2024-02-04T21:30:26-05:00
type: text/html; charset=UTF-8

Loqimain
date: 2024-02-04T21:30:27-05:00
type: text/html; charset=UTF-8

metaMediaWiki
date: 2024-02-04T21:30:29-05:00
type: text/html; charset=UTF-8

Project:Categoriesplumbing
date: 2024-02-04T21:30:30-05:00
type: text/html; charset=UTF-8

plumbingprotocol
date: 2024-02-04T21:30:31-05:00
type: text/html; charset=UTF-8

silos¹
date: 2024-02-04T21:30:33-05:00
type: text/html; charset=UTF-8

Email³
date: 2024-02-04T21:30:34-05:00
type: text/html; charset=UTF-8

make what you need⁴
date: 2024-02-04T21:30:35-05:00
type: text/html; charset=UTF-8

use what you make⁵
date: 2024-02-04T21:30:36-05:00
type: text/html; charset=UTF-8

rename to IndieWeb⁶
date: 2024-02-04T21:30:37-05:00
type: text/html; charset=UTF-8

jargon⁷
date: 2024-02-04T21:30:38-05:00
type: text/html; charset=UTF-8

Loqi Nudge⁸
date: 2024-02-04T21:30:39-05:00
type: text/html; charset=UTF-8

Chat Channels Purposes⁹
date: 2024-02-04T21:30:41-05:00
type: text/html; charset=UTF-8

t1705883690759800
date: 2024-02-04T21:30:43-05:00
type: text/html; charset=utf-8

devDiscord
date: 2024-02-05T00:34:49-05:00
type: text/html; charset=UTF-8

Discordformat
date: 2024-02-05T00:34:50-05:00
type: text/html; charset=UTF-8

formatHacker
date: 2024-02-05T00:34:51-05:00
type: text/html; charset=UTF-8

Hacker NewsIndieWeb
date: 2024-02-05T00:34:52-05:00
type: text/html; charset=UTF-8

IndieWebCampIRC
date: 2024-02-05T00:34:53-05:00
type: text/html; charset=UTF-8

IRCjargon
date: 2024-02-05T00:34:54-05:00
type: text/html; charset=UTF-8

indiewebMatrix
date: 2024-02-05T00:34:55-05:00
type: text/html; charset=UTF-8

Matrixmeta
date: 2024-02-05T00:34:56-05:00
type: text/html; charset=UTF-8

protocolReddit
date: 2024-02-05T00:34:57-05:00
type: text/html; charset=UTF-8

Reddittools
date: 2024-02-05T00:34:58-05:00
type: text/html; charset=UTF-8

toolsSlack
date: 2024-02-05T00:34:59-05:00
type: text/html; charset=UTF-8

Slacksocial
date: 2024-02-05T00:34:59-05:00
type: text/html; charset=UTF-8

trolls.html
date: 2024-02-05T00:35:00-05:00
type: text/html

concept
type: Tag
label: discord

concept
type: Tag
label: hackernews

concept
type: Tag
label: indiewebcamp

concept
type: Tag
label: jargon

concept
type: Tag
label: matrix

concept
type: Tag
label: slack

gresham-law-developers-users-jargon
type: item
type: MicroblogPost
title: : Similar to @paulgraham.com (@paulg@mas.to @paulg)’s observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak.Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return.Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided.Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum.The #IndieWeb community started in 2011 as a single IRC channel #indiewebcamp (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details.It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics.As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon.The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technical con…
link: https://status.blaise.ca/notice/116165
description: 's status on Sunday, 04-Feb-2024 18:05:00 EST
encoded: Similar to @paulgraham.com (@paulg@mas.to @paulg)’s observation about trolls¹, there’s a sort of Gresham's Law of developers (vs users): developers are willing to use a forum with a lot of users in it, but users aren’t willing to use a forum with a lot of developer-speak. Whether such forums are email lists, chat (IRC, #Matrix, #Slack, #Discord), or, well, online forums (#Reddit, #HackerNews), when discussions either start or shift into technical details, jargon, or acronyms, users (in a very broad sense) tend to stop participating, and sometimes leave, never to return. Users in this context are anyone with a desire (or a preference) not to chat or even be bothered spending time reading about technical plumbing & #jargon, and see such discussions as a distraction at best, and more like noise to be avoided. Paraphrasing Paul Graham again: once technical details, jargon, acronyms “take hold, it tends to become the dominant culture” and discourages users from showing up, discussing user-centric topics, or even staying in said forum. The #IndieWeb community started in 2011 as a single IRC channel #indiewebcamp (no email list²) because it was tightly coupled to IndieWebCamp events, which were both highly technical and yet focused on actually making things work on your personal site that you need³, that you will use⁴ yourself. Conversations bridged real world use-cases and technical details. It only took us five years after the first IndieWebCamp in Portland to recognize that the community had grown beyond the events, and had a clear need for a separate place for deep discussions of developer topics. As part of renaming the community from IndieWebCamp to IndieWeb⁵, we created the #indieweb-dev (dev) channel for such technical topics like protocols, formats, tools, coding libraries, APIs, and any other acronyms or jargon. The community did a good job of keeping technical topics in the dev channel, and encouraging new folks in the main #indieweb channel who started technica…
date: 2024-02-04T18:05:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110238
enclosure: indieweb-for-everyone-internet-of-people
links to: indieweb-for-everyone-internet-of-people
enclosure: earthquake-sanfrancisco-shifted
links to: earthquake-sanfrancisco-shifted
enclosure: devformat
links to: devformat
enclosure: formatIndieWeb
links to: formatIndieWeb
enclosure: IndieWebIndieWebCamp
links to: IndieWebIndieWebCamp
enclosure: IndieWebCampjargon
links to: IndieWebCampjargon
enclosure: jargonLoqi
links to: jargonLoqi
enclosure: Loqimain
links to: Loqimain
enclosure: indiewebmeta
links to: indiewebmeta
enclosure: metaMediaWiki
links to: metaMediaWiki
enclosure: Project:Categoriesplumbing
links to: Project:Categoriesplumbing
enclosure: plumbingprotocol
links to: plumbingprotocol
enclosure: protocoltools
links to: protocoltools
enclosure: toolssocial
links to: toolssocial
enclosure: silos¹
links to: silos¹
links to: trolls.html²
enclosure: Email³
links to: Email³
enclosure: make what you need⁴
links to: make what you need⁴
enclosure: use what you make⁵
links to: use what you make⁵
enclosure: rename to IndieWeb⁶
links to: rename to IndieWeb⁶
enclosure: jargon⁷
links to: jargon⁷
enclosure: Loqi Nudge⁸
links to: Loqi Nudge⁸
enclosure: Chat Channels Purposes⁹
links to: Chat Channels Purposes⁹
enclosure: t1705883690759800
links to: t1705883690759800
tagged: concept

devformat
date: 2024-02-04T21:30:22-05:00
type: text/html; charset=UTF-8

formatIndieWeb
date: 2024-02-04T21:30:24-05:00
type: text/html; charset=UTF-8

IndieWebCampjargon
date: 2024-02-04T21:30:26-05:00
type: text/html; charset=UTF-8

indiewebmeta
date: 2024-02-04T21:30:28-05:00
type: text/html; charset=UTF-8

protocoltools
date: 2024-02-04T21:30:32-05:00
type: text/html; charset=UTF-8

toolssocial
date: 2024-02-04T21:30:33-05:00
type: text/html; charset=UTF-8

posse-indieweb-twitter-facebook
type: item
type: MicroblogPost
title: : “To PESOS or to POSSE?”https://dri.es/to-pesos-or-to-posseGreat post@Dries! #openweb#indiewebGo for it. POSSEing to Twitter^1 and Facebook^2 works quite well.Whether notes^3 / status updates (since 2010), or photos^4 (since 2015), it’s totally doable, and brings incredible peace of mind and a greater sense of ownership & control over your content.You may also want to look into POSSEing replies^5, owning your comments as it were.This comment for example, was originally posted ontantek.comas a single post, a multi-reply^6, automatically POSSEd to Twitter where it was auto-ellipsed & threaded^7 with your tweet, and only manually cross-posted on your original post.Lots more on the IndieWeb wiki, and plenty of friendly folks ready and willing to share cross-platform/language development experience implementing all this stuff in the #indieweb-dev channel:*https://chat.indieweb.org/devDrop by and say hi anytime!Tantek1^https://indieweb.org/Twitter#POSSE_to_Twitter2^https://indieweb.org/POSSE_to_Facebook3^https://indieweb.org/note4^https://indieweb.org/photo5^https://indieweb.org/reply6^https://indieweb.org/multiple-reply7^https://indieweb.org/Twitter#original_has_POSSE_tweet
link: https://status.blaise.ca/notice/106948
description: 's status on Tuesday, 06-Feb-2018 13:36:00 EST
encoded: “To PESOS or to POSSE?”https://dri.es/to-pesos-or-to-posse Great post@Dries! #openweb#indieweb Go for it. POSSEing to Twitter^1 and Facebook^2 works quite well. Whether notes^3 / status updates (since 2010), or photos^4 (since 2015), it’s totally doable, and brings incredible peace of mind and a greater sense of ownership & control over your content. You may also want to look into POSSEing replies^5, owning your comments as it were. This comment for example, was originally posted ontantek.comas a single post, a multi-reply^6, automatically POSSEd to Twitter where it was auto-ellipsed & threaded^7 with your tweet, and only manually cross-posted on your original post. Lots more on the IndieWeb wiki, and plenty of friendly folks ready and willing to share cross-platform/language development experience implementing all this stuff in the #indieweb-dev channel: *https://chat.indieweb.org/dev Drop by and say hi anytime! Tantek 1^https://indieweb.org/Twitter#POSSE_to_Twitter 2^https://indieweb.org/POSSE_to_Facebook 3^https://indieweb.org/note 4^https://indieweb.org/photo 5^https://indieweb.org/reply 6^https://indieweb.org/multiple-reply 7^https://indieweb.org/Twitter#original_has_POSSE_tweet
date: 2018-02-06T13:36:00-05:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/102945
tagged: concept

concept
type: Tag
label: openweb

Tantek
type: Agent
holds account: acct