Many great points in this @pluralistic thread on achieving meaningful change through joining a movement, but I wanted to highlight this note on "infrequently updated sites":
"I follow a bunch of people via RSS who only update a couple times per year."
https://mamot.fr/@pluralistic/113317953289922474
Not having "a lot" to say shouldn't stop you from sharing your thoughts and experiences in a blog. And you didn't "fail" if you only have one or two posts.
20 years and two weeks ago, I came up with undohtml.css and unknowingly invented the mechanism of CSS Resets (AKA reboot or reset style sheets¹) which spawned numerous variants, many still in broad use on the web today.
https://tantek.com/log/2004/09.html#d06t2354
A one sentence problem description, and a short paragraph describing my problem-solving, actions, license, link to less than 300 bytes of code (not counting comments), and a few future thoughts.
The rest of that blog post was about “debug scaffolding”, the part I thought was more interesting at the time.
Eric Meyer (@meyerweb.com @meyerweb@mastodon.social) followed up ~10 days afterwards with his thinking and improvements:
- https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/
where he mentioned “resetting” in passing, but not actually calling it a "reset".
~2.5 years later Eric published “Reset Styles” with further reasoning and improvements:
- http://meyerweb.com/eric/thoughts/2007/04/12/reset-styles/
describing them as: “reset” or “baseline” set of styles.
Subsequently he iterated in several more blog posts:
- http://meyerweb.com/eric/thoughts/2007/04/14/reworked-reset/
- http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/ — this is Eric’s first post where he explicitly calls them “reset styles”, which I believe is the origin of the eventual phrase “CSS Reset” and “reset style sheets”
- http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/ (yes a Matrix: Reloaded reference)
~6 months later Eric published his evergreen resource “CSS Tools: Reset CSS”
- https://meyerweb.com/eric/tools/css/reset/
which, as you see within the URL: “css/reset”, is perhaps where the phrase “CSS Reset” comes from, and it’s also the label (link text) he gives that page in his UI about-page² and the first content link in his 404 page³.
My technology invention takeaways from all this:
- if you find yourself repeatedly solving the same (especially annoying) problem, create a re-usable solution that works for you
- write up your problem statement / use-case in only one sentence
- publish your solution (on your personal site⁴), name it something short, with only a short paragraph description, and re-use/remix friendly license (like Creative Commons)
And things not to worry about (that may get in your way to publishing):
- perfecting or making your solution “big enough” or “the right size”. does it solve your problem? then it’s already the right size.
- coming up with the perfect name. instead, name it what it does. someone might come up with a better name weeks, months, or years later. let them run with it!
- waiting to blog multiple things. I could have blogged undohtml.css by itself, probably should have, and instead lumped it into a blog post with another CSS thing I came up with.
Further reading and resources for CSS Resets:
- More history: https://css-tricks.com/reboot-resets-reasoning/
- Large collection: https://perishablepress.com/a-killer-collection-of-global-css-reset-styles/
References:
¹ https://en.wikipedia.org/wiki/Reset_style_sheet
² https://meyerweb.com/ui/about.html
³ https://meyerweb.com/404
⁴ https://indieweb.org/
#undoHTML #undoHTMLCSS #reset #CSSreset #resetstyles #webdesign #technology #invention #indieweb
20 years and two weeks ago, I came up with undohtml.css and unknowingly invented the mechanism of CSS Resets (AKA reboot or reset style sheets¹) which spawned numerous variants, many still in broad use on the web today.
https://tantek.com/log/2004/09.html#d06t2354
A one sentence problem description, and a short paragraph describing my problem-solving, actions, license, link to less than 300 bytes of code (not counting comments), and a few future thoughts.
The rest of that blog post was about “debug scaffolding”, the part I thought was more interesting at the time.
Eric Meyer (@meyerweb.com @meyerweb@mastodon.social) followed up ~10 days afterwards with his thinking and improvements:
* https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/
where he mentioned “resetting” in passing, but not actually calling it a "reset".
~2.5 years later Eric published “Reset Styles” with further reasoning and improvements:
* http://meyerweb.com/eric/thoughts/2007/04/12/reset-styles/
describing them as: “reset” or “baseline” set of styles.
Subsequently he iterated in several more blog posts:
* http://meyerweb.com/eric/thoughts/2007/04/14/reworked-reset/
* http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/ — this is Eric’s first post where he explicitly calls them “reset styles”, which I believe is the origin of the eventual phrase “CSS Reset” and “reset style sheets”
* http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/ (yes a Matrix: Reloaded reference)
~6 months later Eric published his evergreen resource “CSS Tools: Reset CSS”
* https://meyerweb.com/eric/tools/css/reset/
which, as you see within the URL: “css/reset”, is perhaps where the phrase “CSS Reset” comes from, and it’s also the label (link text) he gives that page in his UI about-page² and the first content link in his 404 page³.
My technology invention takeaways from all this:
1. if you find yourself repeatedly solving the same (especially annoying) problem, create a re-usable solution that works for you
2. write up your problem statement / use-case in only one sentence
3. publish your solution (on your personal site⁴), name it something short, with only a short paragraph description, and re-use/remix friendly license (like Creative Commons)
And things not to worry about (that may get in your way to publishing):
1. perfecting or making your solution “big enough” or “the right size”. does it solve your problem? then it’s already the right size.
2. coming up with the perfect name. instead, name it what it does. someone might come up with a better name weeks, months, or years later. let them run with it!
3. waiting to blog multiple things. I could have blogged undohtml.css by itself, probably should have, and instead lumped it into a blog post with another CSS thing I came up with.
Further reading and resources for CSS Resets:
* More history: https://css-tricks.com/reboot-resets-reasoning/
* Large collection: https://perishablepress.com/a-killer-collection-of-global-css-reset-styles/
References:
¹https://en.wikipedia.org/wiki/Reset_style_sheet
²https://meyerweb.com/ui/about.html
³https://meyerweb.com/404
⁴https://indieweb.org/
#undoHTML#undoHTMLCSS#reset#CSSreset#resetstyles#webdesign#technology#invention#indieweb
https://tantek.com/log/2004/09.html#d06t2354
A one sentence problem description, and a short paragraph describing my problem-solving, actions, license, link to less than 300 bytes of code (not counting comments), and a few future thoughts.
The rest of that blog post was about “debug scaffolding”, the part I thought was more interesting at the time.
Eric Meyer (@meyerweb.com @meyerweb@mastodon.social) followed up ~10 days afterwards with his thinking and improvements:
* https://meyerweb.com/eric/thoughts/2004/09/15/emreallyem-undoing-htmlcss/
where he mentioned “resetting” in passing, but not actually calling it a "reset".
~2.5 years later Eric published “Reset Styles” with further reasoning and improvements:
* http://meyerweb.com/eric/thoughts/2007/04/12/reset-styles/
describing them as: “reset” or “baseline” set of styles.
Subsequently he iterated in several more blog posts:
* http://meyerweb.com/eric/thoughts/2007/04/14/reworked-reset/
* http://meyerweb.com/eric/thoughts/2007/04/18/reset-reasoning/ — this is Eric’s first post where he explicitly calls them “reset styles”, which I believe is the origin of the eventual phrase “CSS Reset” and “reset style sheets”
* http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/ (yes a Matrix: Reloaded reference)
~6 months later Eric published his evergreen resource “CSS Tools: Reset CSS”
* https://meyerweb.com/eric/tools/css/reset/
which, as you see within the URL: “css/reset”, is perhaps where the phrase “CSS Reset” comes from, and it’s also the label (link text) he gives that page in his UI about-page² and the first content link in his 404 page³.
My technology invention takeaways from all this:
1. if you find yourself repeatedly solving the same (especially annoying) problem, create a re-usable solution that works for you
2. write up your problem statement / use-case in only one sentence
3. publish your solution (on your personal site⁴), name it something short, with only a short paragraph description, and re-use/remix friendly license (like Creative Commons)
And things not to worry about (that may get in your way to publishing):
1. perfecting or making your solution “big enough” or “the right size”. does it solve your problem? then it’s already the right size.
2. coming up with the perfect name. instead, name it what it does. someone might come up with a better name weeks, months, or years later. let them run with it!
3. waiting to blog multiple things. I could have blogged undohtml.css by itself, probably should have, and instead lumped it into a blog post with another CSS thing I came up with.
Further reading and resources for CSS Resets:
* More history: https://css-tricks.com/reboot-resets-reasoning/
* Large collection: https://perishablepress.com/a-killer-collection-of-global-css-reset-styles/
References:
¹https://en.wikipedia.org/wiki/Reset_style_sheet
²https://meyerweb.com/ui/about.html
³https://meyerweb.com/404
⁴https://indieweb.org/
#undoHTML#undoHTMLCSS#reset#CSSreset#resetstyles#webdesign#technology#invention#indieweb
At #FediForum today, we ran two sessions.
The first session brought together implementors of ActivityPub, AtProto/Bluesky, Nostr and IndieWeb applications to discuss how these protocols relate to each other, and what recommendations they all have for potential adopters who need to decide which to support.
It was a productive, cordial discussion and we will have more to say about it once FediForum publishes the notes from the meeting.
Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation.
Full post: https://tantek.com/2024/044/t1/twenty-years-microformats
Aside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).
Since early 2023, here are the top three updates & interesting developments in microformats:
- Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
- Wikipedia, Threads, omg.lol
- Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.
- #metaformats adoptions, implementations, iteration
Twenty years ago this past February, Kevin Marks and I introduced #microformats in a conference presentation.
Full post: https://tantek.com/2024/044/t1/twenty-years-microformats
Aside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).
Since early 2023, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
* Wikipedia, Threads, omg.lol
2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.
3. #metaformats adoptions, implementations, iteration
Full post: https://tantek.com/2024/044/t1/twenty-years-microformats
Aside: This is an even shorter summary of that post from ~200 days ago, which #Mastodon readers never got due to a Mastodon #federation bug (details in https://tantek.com/t5Yo1).
Since early 2023, here are the top three updates & interesting developments in microformats:
1. Growing rel=me adoption for distributed verification (✅ in Mastodon etc.)
* Wikipedia, Threads, omg.lol
2. Proposal to merge #microformats2 h-review into h-entry, since in practice (e.g. on #indieweb) reviews are just entries with a bit more.
3. #metaformats adoptions, implementations, iteration
The open web is amazing.
So we keep saying in our little subculture, e.g. at #xoxo on the weekend or all over the #fediverse and #indieweb. And generally are met with incomprehension outside of our little subculture.
IMHO that's because we are not saying **why** the open web is amazing.
I think it all boils down to: "on the open web, I can be much more creative, with minimum expense, than elsewhere, and so easily share my creations with the world."
Getting there. #WordPress site connected via ActivityPub plugin, user account matches a Gravatar account name and all appears to be working (avatar/header img, bio description.) 🤞
I’ll be in New York next month, from September 16-30th.
So first of all I’d be delighted to meet fellow nerds in the #opensource #fediverse #indieweb community if anyone wants to meet up 👋
Secondly, although I’ve booked a place already: If anyone’s got a spare bed or couch for me, kindly reach out! Would gladly cover some of the rent/food for the duration.
Staying in NYC for two weeks is 2x more expensive than the flight there from Norway, lol…
The brilliant @molly.wiki just opened #xoxofest with a rousing speech telling us to take back the web from the big platforms by posting on our own sites again #indieweb
People over protocols over platforms.
inspired by today’s #indieweb #fediverse #ActivityPub #decentralized #socialMedia lunch meetup at #XOXO #XOXOConf (@xoxo@xoxo.zone)
This is post 16 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/173/t1/years-posse-microformats-adoption
→ https://tantek.com/2024/238/t1/indiewebcamp-portland
People over protocols over platforms.
inspired by today’s #indieweb#fediverse#ActivityPub#decentralized#socialMedia lunch meetup at #XOXO#XOXOConf ( @xoxo@xoxo.zone)
This is post 16 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/173/t1/years-posse-microformats-adoption
→ https://tantek.com/2024/238/t1/indiewebcamp-portland
inspired by today’s #indieweb#fediverse#ActivityPub#decentralized#socialMedia lunch meetup at #XOXO#XOXOConf ( @xoxo@xoxo.zone)
This is post 16 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/173/t1/years-posse-microformats-adoption
→ https://tantek.com/2024/238/t1/indiewebcamp-portland
Has anyone built the #indieweb version of Meetup? (Opt in to groups that then plan localized events - perhaps inclusive of online ones?) it’s tricky as it takes some good practices to avoid spam, scams and other bad behavior and actors. But reoccurring (as well as one off but low barriers to entry to holding) events is really good for community building (regardless of the topics)
All setup here at IndieWebCamp Portland!
https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k
Good crowd of participants from #XOXO #XOXOConf (@xoxofest.com @xoxo@xoxo.zone @xoxo) here to work on their personal website(s), domains, or other independent social media setups!
As encouraged by Andy Baio (@waxy.org @andybaio@xoxo.zone @waxpancake)
“Every one of you should have a home on the web not controlled by a billionaire.”
If you’re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions.
Personal site and hack demos at 16:00 PDT!
#indieweb #fediverse #ActivityPub #decentralized #socialMedia
This is post 17 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/237/t1/people-over-protocols-platforms
→ 🔮
All setup here at IndieWebCamp Portland!
https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k
Good crowd of participants from #XOXO#XOXOConf (@xoxofest.com @xoxo@xoxo.zone @xoxo) here to work on their personal website(s), domains, or other independent social media setups!
As encouraged by Andy Baio (@waxy.org @andybaio@xoxo.zone @waxpancake)
“Every one of you should have a home on the web not controlled by a billionaire.”
If you’re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions.
Personal site and hack demos at 16:00 PDT!
#indieweb#fediverse#ActivityPub#decentralized#socialMedia
This is post 17 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/237/t1/people-over-protocols-platforms
→ 🔮
https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k
Good crowd of participants from #XOXO#XOXOConf (@xoxofest.com @xoxo@xoxo.zone @xoxo) here to work on their personal website(s), domains, or other independent social media setups!
As encouraged by Andy Baio (@waxy.org @andybaio@xoxo.zone @waxpancake)
“Every one of you should have a home on the web not controlled by a billionaire.”
If you’re in #Portland and want help, encouragement, or camaraderie in getting setup or doing more with your personal site, come on by! We’ll be having a mix of discussion sessions and create/hack sessions.
Personal site and hack demos at 16:00 PDT!
#indieweb#fediverse#ActivityPub#decentralized#socialMedia
This is post 17 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/237/t1/people-over-protocols-platforms
→ 🔮
Introducing Betula 1.2
Betula is a federated self-hosted single-user bookmarking software. Organize your collection with tags. Write descriptions and quotes. #IndieWeb microformats and #Fediverse are supported.
This release brings #ActivityPub-backed following. Follow Betula from Mastodon and whatnot and receive all new bookmarks. A new design for bookmarks was also made.
Release notes: https://betula.mycorrhiza.wiki/v1.2.0.html
Happy bookmarking!
"On August 6, 1991 [33 years ago], the first website was introduced to the world. [It] contained information about the World Wide Web Project. It launched at the European Organization for Nuclear Research, CERN, where it was created by British computer scientist Tim Berners-Lee."
http://info.cern.ch/hypertext/WWW/TheProject.html
Happy birthday, web!
#WorldWideWeb#WWW#TheWeb #indieweb#FirstWebsite #internet #history#OTD
Is your first website still online? Or maybe your oldest website? I'd love to see it!
"On August 6, 1991 [33 years ago], the first website was introduced to the world. [It] contained information about the World Wide Web Project. It launched at the European Organization for Nuclear Research, CERN, where it was created by British computer scientist Tim Berners-Lee."
http://info.cern.ch/hypertext/WWW/TheProject.html
Happy birthday, web!
#WorldWideWeb#WWW#TheWeb #indieweb#FirstWebsite #internet #history#OTD
@talksina @lordmatt#Webmention is more blogging-style... it is kind of the next iteration of pingbacks...
@pfefferle @talksina @lordmatt As a standard #Webmention is merely a notification mechanism that A has mentioned B – they can be blog posts, social interactions or whatever else
The #IndieWeb stack of tech is much more granular than the #ActivityPub one – so the definition of A and B is left as an exercise to the user of it
But maybe you're talking about a WordPress plugin specifically?
I think of https://openmentions.com as the #IndieWeb equivalent of hashtags for content. Especially #blogs.
As a visual designer I shouldn't be saying it but @pluralistic just reminded me how much I loved MySpace and how my young adult obsessive creative personality with a passion for punk zines and comics was constantly changing and shuffling stuff in my profile. It was so fun to go on my friends profile and see what they did with theirs and exchange tips.
"An artform that can't be transgressive is sterile, stillborn, a dead end."
https://pluralistic.net/2024/07/20/ransom-note-force-field/#antilibraries
I've started owl-blogs to explore the #IndieWeb space. At the moment I'm "only" using #microformats and #webmention.
I've tried to implement #micropub in the past, but found it provided to little value for me.
Anything I should try out next?