See yesterday’s post for the meeting’s talking points.
It was a small group, but we had an encouraging discussion. Everyone at the meeting felt there’s a need for something like IndieWeb or PDH. Below is a list of questions and comments from the June 20, 2016 event.
- Infosec needs to be the foundation of PDH and IndieWeb-for-consumers, build other stuff on top of it.
- Infosec foundation means we need to get infosec people involved in PDH early on.
- OWASP involvement (Open Web Application Security Project)?
- PDH is intended for 80% of internet users, so it must be simple to use, have plug-n-play operation.
- Remote access and mobile device interaction need to be high priority design criteria.
- For PDH sites, can other webdev tools than just WordPress be used?
- Yes, per principle of plurality, aka diversity or experimentation. But a PDH-Secure certified stack is envisioned, probably incorporating philosophy aspects of Debian Linux project and Google flagship Nexus Android phones.
- Use proprietary webdev framework (like svnO) because site more difficult to attack than open source platform like WordPress?
- How will increasing use of virtual reality affect the PDH concept and implementation?
- Gravatar — good example of a publish once, syndicate everywhere.
- MSPW (make stuff people want) — “yeah, I can make a website, but what would I want to do with it?”
- Figure out highly-engaging “starter uses” for the consumer who takes the time to create their own PDH website.
- If they have a compelling reason to start using PDH, young people will find plenty of unexpected ways to use it.
- One potential starter use example is the Minecraft-Raspberry Pi neighborhood friends’ network.
- PDH is envisioned as an umbrella site for personal residual revenue streams and ventures.
- OYD server (OwnYourData) could be the next phase for consumer network hardware after home wireless routers.
- Update OYD software like Chromebook, helping democratize consumer servers.
- Incorporate traffic shaping or limiting so individual OYD servers are highly resistant to slashdotting if original content on that server goes viral.
- Personal “Google Drive,” “Dropbox,” or file server.
- Many BSD Unix community members have IndieWeb ethos — build own stuff, run own services.
- Target early adopters and trend starters
- Young people
- Create beta tester student network
- 3 levels of target demographics for beta testing and early users
- 13-14 year olds
- High school juniors
- College juniors
- Schedule another event to discuss PDH and IndieWeb; maybe another Coder Cooperative session, maybe a different setting.
- Revise talking points and create 10-slide presentation. PDH pitch still in early stages of development — very rough, too much information, needs to be much smoother, more concise and impactful.
- Develop 100-word summary and one-page proposal for PDH initiative.
- Identify PDH concept basic principles.
- Identify several recommended options for registering a domain name, hosting a WordPress PDH website, and backing up all website data. Write up details regarding registration, hosting, and backup,including set-up costs and annual fees.
Keep an eye on this blog for announcement and details about the next meetup to discuss the PDH initiative and IndieWeb. Tentative timeframe for that meetup is August 2016. If you have questions about the discussion points or Next Steps, please contact me at bwaldron (at) gmail [dott] com.
Hope to see you at the next PDH event! 🙂
The two posts from yesterday and today, along with the six posts written earlier about the PDH and IndieWeb are pretty much a complete information package regarding last night’s event at the Appleton Makerspace. I was satisfied with the experiment of using the “Events Wrangling” blog that way as an event resource.
I need to dig into event themes for WordPress.com sites to see what others have developed into more formal event tools or platforms. When I’m the events wrangler for a future event, it’s likely I’ll try a slightly different WordPress website approach than what I used this time.
Blogging: Fundamentals, Day 6 — An Irresistible About Page
[Good feeling about Blogging U and Blogging: Fundamentals class today. Not trying to figure out where classroom is, where my email for today’s assignment is, or whether I’m going to get my assignment done! Nothing but blue skies…]
Blogging 101, Day 6 assignment is:
- Create an About page on your blog.
- Write the content for your About page — use your Day One post for inspiration if you’d like — and click Publish.
- Go to My Sites > Customize, then select the Widgets tab. Add a Text Widget with a one- or two-sentence version of your story, and click Save and Publish.
Steps 1 and 2 of the assignment were pretty easy since I already had an About page with lots of content. Step 2 was good from the standpoint of causing me to take a fresh look at what my About page said. I made a few minor changes and decided I need to refocus the content to make it more relevant to my “ideal reader,” the subject of my June 19 post. Step 3 appears easy, and I will do that as soon as I publish this post.
While working on Step 2, however, I made the mistake of reading the two linked resources for writing About page content; “About Page 101: Making Them Care” and “About Page 201: The Meat Grinder.” Big Mistake. With capital letters, as you can see.
The reason it was a mistake is that my About page doesn’t feel even close to “making them care.” It will require several hours of writing down thoughts and sentences, trying a few on, seeing if any fit well enough to replace what’s already on the About page. Getting the words on that page to the point of Making Them Care will require the gracious but merciless assistance of a few wise and worldly wordsmith friends.
So, add About-improvement item to my To-Do list, which gets longer with every new Blogging U assignment. Blogging U is a probably-fantastic resource for a WordPress blogger. But, like everything worthwhile, there’s a price to pay. In this case, Price = Time. (Right now it’s almost 11 PM, and I usually go to bed by 10 PM.)
My virtual assignments for the Blogging: Fundamentals class seem to have three outcomes — I was really only looking for the first one…
- Straightforward Learning. Learn something, apply what I learned, complete that part of assignment easily.
- Complex Learning. Learn required skill, but also learn about many things related to required skill. Apply required skill and complete assignment. But — spend more time reading about related skills and capabilities, and make mental or written list of additional work needed on website or in future blog posts.
- Challenging Learning. The challenging stuff is like today’s assignment to create an irresistible About page, or the previous lesson that asked me to figure out what the ideal reader for my blog will actually spend their precious time reading.
I’m glad I clicked the Sign Up button for this Blogging U class. I just wish I would have clicked it ten years ago.
[I know — Blogging U and that button weren’t there ten years ago. Which makes me wonder: What do I wish Automattic offered now that they’ll probably have ten years from now???]
Other posts related to IndieWeb and Personal Digital Home
“WordPress: Default Personal Digital Home (PDH)”
“WordPress Personal Digital Home, Part 2: In The Year 2036”
“WordPress Personal Digital Home, Part 3: Pick A Problem”
“WordPress Personal Digital Home, Part 4: Baby Steps”
“IndieWeb Summit 2017 & WordPress PDH”
“Coder Cooperative June 20th Meetup: IndieWeb And Personal Digital Home“
“IndieWeb and PDH: Talking Points For Coder Cooperative June 20 Meetup“
“Day-After Report: June 20 Coder Cooperative, IndieWeb & PDH” — today’s post