Cubo De Cuba

at Cubo De Cuba

Want to watch: Home Page.

Currently available on iTunes and free on Tubi TV.

Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation.

I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats

Since that post nearly a year ago, here are the top three updates & interesting developments in microformats:

1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
 * Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
 * Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
 * omg.lol profile links by default: https://home.omg.lol/info/profile-items

2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
 * https://github.com/microformats/h-entry/issues/32
 
3. #metaformats adoptions, implementations, and iteration
 * There was growing practical interest in metaformats, so I updated the spec accordingly
 * A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples
 * Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issues

Hard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.

From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever.  Looking forward to seeing what we can build in 2024.


Post Glossary

h-entry
  https://microformats.org/wiki/h-entry
h-review
  https://microformats.org/wiki/h-review
link-preview
  https://indieweb.org/link-preview
metaformats
  https://microformats.org/wiki/metaformats
microformats
  https://microformats.org/wiki/
microformats2
  https://microformats.org/wiki/microformats2
rel-me
  https://microformats.org/wiki/rel-me
#microformats #metaformats #microformats2 #IndieWeb #Mastodon #fediverse

Video: Midsummer Adventures at Mt. Hood

Twenty years and two days ago, @KevinMarks.com (@KevinMarks@xoxo.zone @KevinMarks) and I introduced #microformats in a conference presentation.

I wrote a long retrospective last year: https://tantek.com/2023/047/t1/nineteen-years-microformats

Since that update nearly a year ago, here are the top three interesting developments in microformats:

1. Growing rel=me adoption for distributed verification:
 * Wikipedia: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
 * Threads: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me
 * omg.lol profile links by default: https://home.omg.lol/info/profile-items

2. A proposal to merge h-review into h-entry, since reviews are in practice always entries with a bit more information:
 * https://github.com/microformats/h-entry/issues/32
 
3. #metaformats adoptions, implementations, and iteration
 * There was growing practical interest in metaformats, so I updated the spec accordingly
 * A half dozen implementations shipped: https://indieweb.org/metaformats#IndieWeb_Examples
 * Active discussion for evolving metaformats to support more real world use-cases: https://github.com/microformats/metaformats/issues

Hard to believe it’s been 20 years of iterating and evolving microformats, to #microformats2, growing adoption as #IndieWeb building blocks, distributed verification (those green checkmarks) in #Mastodon and across the #fediverse, and implementing metaformats parsing to standardize parsing various meta tags for link previews into equivalent microformats2.

From last year’s activity, it’s clear there’s more use-cases, implementer interest, and community activity than ever.  Looking forward to seeing what we can build in 2024.


Post Glossary

h-entry
  https://microformats.org/wiki/h-entry
h-review
  https://microformats.org/wiki/h-review
link-preview
  https://indieweb.org/link-preview
metaformats
  https://microformats.org/wiki/metaformats
microformats
  https://microformats.org/wiki/
microformats2
  https://microformats.org/wiki/microformats2
rel-me
  https://microformats.org/wiki/rel-me
#microformats #metaformats #microformats2 #IndieWeb #Mastodon #fediverse

Phishing Mitigation for Mastodon.social

If kittens eat twice as much as adult cats, why does their food come in cans that are half the size? 🤨

Durable Pseudonyms

#social-computing #identity #social-media

Bigscreen Beyond day 2

Want to read: The Future is Disabled: Prophecies, Love Notes and Mourning Songs by Leah Lakshmi Piepzna-Samarasinha (ISBN 9781551528915)

The Biergarten at The Standard

Outside seating getting harder to find. 🧣🧤

📕 Finished reading Blood in the Machine: The Origins of the Rebellion Against Big Tech by Brian Merchant ISBN: 9780316487740

Bigscreen Beyond

I'm planning out my travel for the year, and now that Brisbane is scratched, I'm barely going to hit Alaska MVP Gold. And if I buy the annual lounge pass, even with the signup bonus discount, it will work out to about $35 per visit.
#Brighton #London and other #England & #Europe friends:

🎪 #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
→ 🔮
#Brighton #London #England #Europe #IndieWebCamp #100PostsOfIndieWeb #100Posts #IndieWeb
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 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
https://tantek.com/2024/035/t2/indiewebcamp-brighton-tickets-available


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
Reddit
  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
#Matrix #Slack #Discord #HackerNews #jargon #IndieWeb #indiewebcamp #indieweb-dev #indieweb #100PostsOfIndieWeb #100Posts
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 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 such threads in the channel it started rather than break to another channel. It was also a constant bit of 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 use our sites instead of depending on social media silos. That common purpose keeps us focused.

It takes a community to keep a community healthy and welcoming to newcomers. Eternal community vigilance is the price of a user-focused and newcomer-inclusive community.

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
format
  https://indieweb.org/format
IndieWeb
  https://indieweb.org/IndieWeb
IndieWebCamp
  https://indieweb.org/IndieWebCamp
jargon
  https://indieweb.org/jargon
Loqi
  https://indieweb.org/Loqi
main IndieWeb chat channel (on main)
  https://indieweb.org/discuss#indieweb
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
tools
  https://indieweb.org/tools
social media silos
  https://indieweb.org/silos


¹ https://www.paulgraham.com/trolls.html
² 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
#Matrix #Slack #Discord #HackerNews #jargon #IndieWeb #indiewebcamp #indieweb-dev #indieweb #100PostsOfIndieWeb #100Posts

CarMax is great

IFC Center

Let’s Argento! 🧙‍♀️🔪

I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude

I was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends.

Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social.

Feels like something big has shifted.

The #federated #IndieWeb has replaced another #socialMedia silo use-case.

This is post 7 of #100PostsOfIndieWeb. #100Posts

https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable
→ 🔮


Post glossary:

silo
  https://indieweb.org/silo
social media
  https://indieweb.org/social_media
use-case
  https://indieweb.org/use_case
#earthquake #SanFrancisco #earthquakes #Twitter #fediverse #federated #IndieWeb #socialMedia #100PostsOfIndieWeb #100Posts