For IndieWebCamp San Diego’s Create Day, I worked on cleaning up some code for indiewebify.me and pushed it to a branch on my GitHub.
The readme there has more details, but this is basically an in-progress update to use the SlimPHP framework. It is probably only about 30% complete, but some parts of it are functional. Pushing this to Github will make it easier for the community to collaborate on and decide how to move forward.
IndieWebCamp San Diego 2024 Project Goals
TIL the term “smishing” (SMS phishing) while looking up info on those spam text messages claiming to be from the USPS about a missed package. Never click the links in those, of course. You can also report them to the postal inspector.
Checking out a new podcast, Public Health is Dead. Sounds promising so far.
“Public Health is Dead is a forward-thinking autopsy on how we’ve f*cked up in public health. How do we prepare for future pandemics while we’re already in the thick of one? And how do we reinvent systems that place some of us closer to death?”
If you have a blog and ever feel stuck about why you should post, what to post next, or how to write your post, hopefully this post will help you get unstuck, and publish your post.
Why Post
There is a whole wiki page on the topic:
* https://indieweb.org/why_post — which could use some gardening
Here are a few reasons why to post:
* Wean yourself off social media. Post to your own site instead of social media. If you already post on social media, into someone else’s garage¹, then you already have reason enough to post. So post on your own site first, and optionally syndicate² to that silo, only if you have friends who still use it to read posts.
* Search everything you write. Do you post long comments or issues on GitHub? Do you post on public mailing lists? Post such things to your own site, so you can more easily search everything you’ve written on a topic. Then post a copy to those external destinations.
* All the reasons to own your data: https://indieweb.org/own_your_data
What to Post
* Post positive things promptly: https://tantek.com/2018/357/t3
* … from that day first: https://tantek.com/2018/364/t1
* … in time order: https://tantek.com/2018/364/t5
* Make and share lists. People like lists
* Post to learn in public, and pass on what you learn
How to Post
* Use a local text editor
* Capture first, edit & publish later: https://tantek.com/2023/365/t1/
* Do something positive (in-person), then post about it: https://tantek.com/2018/002/t1
* Single topic post
* Short and to the point. Edit and remove anything distracting from the main point.
* Quotable post title
* Summary opening paragraph
* Put tangents aside
* Quotable sentences and multi-sentence paragraphs
* Subheadings help cluster related paragraphs
* Use a footer for updates, terminology, previous posts, additional reading, and citations.
* Move definitions, citations, etc. to the footer unless including them inline either provides little risk of distraction or significantly helps reading flow
* Use footer sections: Previously, Post Glossary, References, Additional Reading
* Check your references
Each of these points could be its own blog post. There are many more whys, whats, and hows. This is a start.
* https://indieweb.org/why_post
* https://indieweb.org/what_to_post
* https://indieweb.org/how_to_post
Add your own to each, and help organize them.
Glossary
mailing list
https://indieweb.org/mailing_list
own your data
https://indieweb.org/own_your_data
post footer
https://indieweb.org/posts#Footer_sections
silo
https://indieweb.org/silo
social media
https://indieweb.org/social_media
References
¹ https://tantek.com/2023/001/t1/own-your-notes
² https://indieweb.org/POSSE
This is post 29 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/306/t1/simple-embeds
→ 🔮
