I wrote some things you need to know about consistency: https://lars-christian.com/on-consistency/
Hmm, so this is almost exactly what I'm looking for, I think: "microblog.pub - A self-hosted, single-user, #ActivityPub powered #microblog." #IndieWeb friendly.
@ewisniowski I've only recently gotten into this, but the #Indieweb wiki is a WEALTH of information! This is where i found info about Indieweb #Wordpress and it inspired me to redo my site.
POSSE - https://indieweb.org/POSSE
As for Ghost, I'm not sure, based on this: https://indieweb.org/Ghost#Lack_of_extensibility_or_IndieWeb
Yes I know my website appears to be down, but check back tomorrow or in a few days! Domain registrar stuff. https://robertkingett.com/ #IndieWeb
Small digital communities are not without its challenges, but nothing scales wholesale abuse like venture capital funding and shareholder value.
And puzzle CAPITAs.
I don't want to train someone's AI. I don't know how that's related but I don't like it. #tech #socialmedia #SmallWeb #indieweb
What using RSS feels like https://gilest.org/rss-feels.html #RSS #IndieWeb
the 32-bit cafe is having a valentine's day event, and it starts today! there's a *ton* of ways to participate—you can make a card from images, text, or code! you have until february 12th to submit!
Bookmarks page is now live at https://grgml.xyz/bookmarks/ 🎉 With microformats, bridgy-specific content for posting to mastodon, webmentions support and all that. This will probably be the feature that gets me to update my website most often, as I'll be adding lots of read/want-to-read links there.
IndieWebCamp Brighton 2024 · Paul Robert Lloyd
This is going to be a fun weekend!
Not got a personal website? Bring your laptop or mobile device, and we’ll help you get setup so that you can publish somewhere you control and can make your own.
Seasoned web developer? Learn about the different open web services, software and technologies that can help empower yourself and others to own their content and online identity.
Nice to see newer blogging platforms providing a blog by email option! Keep it up! https://posthaven.com/features #Email #Blog #Blogs #IndieWeb
Reply to 'A RSS Feed For My Mastodon Bookmarks'
#IndieWeb
An excellent idea from @ton ! Adapting it for my own context I can see two possible options - either pull the bookmarks from Mastodon into bookmark entries on this blog, or post to Diigo as new bookmarks. Probably the latter as I am fairly liberal in what I bookmark on Mastodon.
https://www.synesthesia.co.uk/stream/reply-to-a-rss-feed-for-my-mastodon-bookmarks/
Reminder that I write about a lot of stuff, blindness, life stuff, my author news. I never stick to 1 topic so if you wanna follow, my RSS feed is https://robertkingett.com/feed/ #RSS #Blog #IndieWeb
[New Shared Link] - #IndieWeb fediwall
https://stream.indieweb.org/
#fediverse
#indieweb
#indiestream
cc @bacardi55
🎪 #IndieWebCamp Brighton tickets are available!
🎟 https://ti.to/indiewebcamp/brighton-2024
🗓 2024-03-09…10
🏢 The Skiff, Brighton, England
🌐 https://indieweb.org/2024/Brighton
Grab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https://indieweb.org/2024/Brighton#In_person
For more information, see organizer @paulrobertlloyd.com (@paulrobertlloyd@mastodon.social)’s post: https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/
Also check out @ClearLeft.com (@clearleft@mastodon.social @clearleft)’s “Patterns Day” (https://patternsday.com/) in Brighton the Thursday (2024-03-07) beforehand!
Previously: https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned
This is post 9 of #100PostsOfIndieWeb. #100Posts #IndieWeb
← https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon
→ 🔮
IndieWebCamp San Diego 2023
https://fed.brid.gy/r/https://www.ciccarello.me/blog/2024/02/05/indiewebcamp-san-diego-2023/
🎪 #IndieWebCamp Brighton tickets are available!
🎟 https://ti.to/indiewebcamp/brighton-2024
🗓 2024-03-09…10
🏢 The Skiff, Brighton, England
🌐 https://indieweb.org/2024/Brighton
Grab an in-person ticket (limited capacity) then optionally add yourself to the list of participants: https://indieweb.org/2024/Brighton#In_person
For more information, see organizer @paulrobertlloyd.com (@paulrobertlloyd@mastodon.social)’s post: https://paulrobertlloyd.com/2024/032/a1/indiewebcamp_brighton/
Also check out @ClearLeft.com (@clearleft@mastodon.social @clearleft)’s “Patterns Day” (https://patternsday.com/) in Brighton the Thursday (2024-03-07) beforehand!
Previously: https://tantek.com/2024/022/t1/indiewebcamp-brighton-planned
This is post 9 of #100PostsOfIndieWeb. #100Posts #IndieWeb
← https://tantek.com/2024/035/t1/greshams-law-developers-users-jargon
→ 🔮
From yesterday, one of my most favorite things I've written recently:
https://chavanniclass.wordpress.com/2024/02/04/err-on-the-side-of-publishing/
#blog #blogging #writing #IndieWeb #publishing #WritingCommunity #inspiration
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 technical conversations to continue them in the dev channel.
Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.
We had already started documenting IndieWeb related jargon⁶ on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com (@aaronpk@aaronparecki.com) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge⁷ them to the development channel.
Having Loqi do some of the gentle nudging has helped, though it‘s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.
We’ve documented both a summary and lengthier descriptions of channel purposes⁸ which help us remind each other, as well as provide a guide to newcomers.
Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone⁹, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.
It takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.
The ideas behind this post were originally shared in the IndieWeb meta chat channel.¹⁰
This is post 8 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted
→ 🔮
Post glossary:
development channel (indieweb-dev)
https://indieweb.org/discuss#dev
Discord
https://indieweb.org/Discord
format
https://indieweb.org/format
Hacker News (HN)
https://indieweb.org/Hacker_News
IndieWeb
https://indieweb.org/IndieWeb
IndieWebCamp
https://indieweb.org/IndieWebCamp
IRC
https://indieweb.org/IRC
jargon
https://indieweb.org/jargon
Loqi
https://indieweb.org/Loqi
main IndieWeb chat channel (on main)
https://indieweb.org/discuss#indieweb
Matrix
https://indieweb.org/Matrix
meta chat channel
https://indieweb.org/discuss#meta
MediaWiki Category
https://www.mediawiki.org/wiki/Project:Categories
plumbing
https://indieweb.org/plumbing
protocol
https://indieweb.org/protocol
https://indieweb.org/Reddit
tools
https://indieweb.org/tools
Slack
https://indieweb.org/Slack
social media silos
https://indieweb.org/silos
¹ https://www.paulgraham.com/trolls.html (2008 essay, HN still succumbed to trolling)
² https://indieweb.org/discuss#Email
³ https://indieweb.org/make_what_you_need
⁴ https://indieweb.org/use_what_you_make
⁵ https://indieweb.org/rename_to_IndieWeb
⁶ https://indieweb.org/jargon
⁷ https://indieweb.org/Category:jargon#Loqi_Nudge
⁸ https://indieweb.org/discuss#Chat_Channels_Purposes
⁹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
¹⁰ https://chat.indieweb.org/meta/2024-01-22#t1705883690759800
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 technical conversations to continue them in the dev channel.
Still, it was too easy for user-centric topics to veer into technical territory. It often felt more natural to continue a thread in the channel it started rather than break to another channel. There was also a need for regular community labor to nudge developer conversations to the developer chat channel.
We had already started documenting IndieWeb related jargon⁶ on the wiki and turned it into a MediaWiki Category so we could tag individual pages as jargon and have them automatically show-up in a list. Soon after, @aaronparecki.com (@aaronpk@aaronparecki.com) added a heuristic to the friendly channel bot Loqi to recognize when people started using jargon in the main IndieWeb chat channel and nudge⁷ them to the development channel.
Having Loqi do some of the gentle nudging has helped, though it‘s still quite easy for even the experienced folks in the community to get drawn into a developer conversation on main as it were.
We’ve documented both a summary and lengthier descriptions of channel purposes⁸ which help us remind each other, as well as provide a guide to newcomers.
Both experienced community members and newcomers share much of the user-centric focus of the IndieWeb, the IndieWeb being for everyone⁹, whether developer, hobbyist, or someone who wants an independent presence on the web without bothering with technical details. Whether some of us want to code or not, we all want to use our IndieWeb sites to express ourselves on the web, to use our sites instead of depending on social media silos. That shared purpose keeps us focused.
It takes a village: eternal community vigilance is the price of staying user-centric and welcoming to newcomers.
The ideas behind this post were originally shared in the IndieWeb meta chat channel.¹⁰
This is post 8 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/033/t1/earthquake-sanfrancisco-shifted
→ 🔮
Post glossary:
development channel (indieweb-dev)
https://indieweb.org/discuss#dev
Discord
https://indieweb.org/Discord
format
https://indieweb.org/format
Hacker News (HN)
https://indieweb.org/Hacker_News
IndieWeb
https://indieweb.org/IndieWeb
IndieWebCamp
https://indieweb.org/IndieWebCamp
IRC
https://indieweb.org/IRC
jargon
https://indieweb.org/jargon
Loqi
https://indieweb.org/Loqi
main IndieWeb chat channel (on main)
https://indieweb.org/discuss#indieweb
Matrix
https://indieweb.org/Matrix
meta chat channel
https://indieweb.org/discuss#meta
MediaWiki Category
https://www.mediawiki.org/wiki/Project:Categories
plumbing
https://indieweb.org/plumbing
protocol
https://indieweb.org/protocol
https://indieweb.org/Reddit
tools
https://indieweb.org/tools
Slack
https://indieweb.org/Slack
social media silos
https://indieweb.org/silos
¹ https://www.paulgraham.com/trolls.html (2008 essay, HN still succumbed to trolling)
² https://indieweb.org/discuss#Email
³ https://indieweb.org/make_what_you_need
⁴ https://indieweb.org/use_what_you_make
⁵ https://indieweb.org/rename_to_IndieWeb
⁶ https://indieweb.org/jargon
⁷ https://indieweb.org/Category:jargon#Loqi_Nudge
⁸ https://indieweb.org/discuss#Chat_Channels_Purposes
⁹ https://tantek.com/2024/026/t3/indieweb-for-everyone-internet-of-people
¹⁰ https://chat.indieweb.org/meta/2024-01-22#t1705883690759800