remove all this section

redate for new version

This note describes planned changes for the Page.

The Admin Pages Issue covers this page.

On most websites, my Admin Pages cover the domain. But for Privacy Policy (and some others), my approach is to declare a Keith Taylor Privacy Policy. So that policy applies to all my websites. Unless it is overridden for a specified domain.

In earlier versions, I considered a complicated system for analyzing privacy needs (see archive). But that was overkill for me. Because visitors choose their own privacy restrictions when visiting my websites. So your choices are...

Cookies

All my websites should work without cookies. If you choose to allow cookies, they do not collect any personal information. Furthermore, you can check the privacy policies of the third party services that I use:

Email Address

You choose if you want to communicate with me or not. You can communicate via GitHub (Issues and Discussions) or via Gumroad (Subscriptions and Memberships).

For GitHub, I recommend that you keep your email address private. Which, at the time of writing is the default setting for your GitHub profile. In any event, I will not normally look at your GitHub profile email address.

For Gumroad, the main purpose of that service is to allow us to communicate via email. So if you want to keep your email address private, don't use my Gumroad services. But I hope that you will want to do so. In which case I recommend that you reserve an email address for the sole purpose of subscribing to my services.

Most importantly, I will only use your email address to send the products and services that you request. And I will never pass it to anyone else.

#BuildInPublic

And when I started it, I intended spending time creating a very thorough review of modern Privacy Policies. With a view to developing a template which is better than the pointless boilerplate rolled out by privacy policy generators.

Alas, I haven't had time to meet the high expectations I set for myself. On the other hand, I've dropped Google Analytics and I'm transmigrating all my sites from WordPress to Eleventy.

So there's no need for WordPress cookies. And the only analytics data I collect is from Microsoft Clarity. Which as far as I know, does not collect any personal information.

For personal contact I rely on GitHub and Gumroad. I also use OneSignal notification services and Google Adsense advertising services. Of these, the only personal information I use is your email address that you send to me via Gumroad. And I only use your email address to send the products or services that you request.

Should you need to investigate further, the Privacy Policies for my third party services are: - GitHub - Google Adsense - Gumroad - OneSignal

#BuildInPublic

Optional free membership for followers who want email notification as soon as I publish.

#BuildInPublic

Next Post#3

Next Post#2

Next Post#1

This post is the home of my #BuildInPublic project. Because with my #BuildInPublic approach, I reward followers with earliest content previews.

In fact, I'm developing tiers of followers/subscribers here. As will become clear in the next few days.

Furthermore, I'm adopting a #BuildInPublic approach to all my websites. Because I want to create informal online learning environments that encourage learners to become coaches/mentors. Obviously, that will take time to onboard people and qualify objectives. But I have to start somewhere. And #BuildInPublic seems to me to be my best chance of finding like-minded collaborators.

I often rush into assessing new applications. Because I learn quicker by applying compared to reading. But one downside is that I frequently miss key features.

That's only a major drawback if I abandon the application where I can't see how it fits my project. And today I avoided that with serendipity. Because… 1. My application was a Chrome Extension 1. I wanted to test to see if was active and change webpage content accordingly 1. I found I could run the app without an extension - as fully described in the documentation that I skipped reading!

All of which is an idea for my next blog post. But the real point is I have established a process for starting ad-hoc Shrewd Learning projects "in the wild". Because normally, I start making notes somewhere. Then forgetting where I put them.

I think we all do that when we spot something interesting that might warrant future research. Now for my established subject areas, I always start annotating new topics within that subject area. So, I can prioritize it in my usual processes.

Today, I've extended this by tagging public notes with Shrewd Learning. So when I look at the Shrewd Learning Tag, I see all notes that present potential new learning topics. Which opens a great way to collaborate loosely with other people if I can establish some traction with Shrewd Learning.

For now, this is my reminder to do a personal blog entry based on this. More importantly, I should update this blog entry to reflect recent advances in Shrewd Learning and my other 2 online learning projects.

Remove space to ShrewdNotes

New 4 part blog series... - Introducing 📒ShrewdNotes. Members Notes in Progress. - How Keith Uses 📒ShrewdNotes - How You Can Use 📒ShrewdNotes - Why We Might Share 📒ShrewdNotes

Embedding Hypothesis in Websites and Platforms

Embedding Hypothesis To add Hypothesis to your website or platform, simply add the following line to the HTML source of your page:

From https://web.hypothes.is/help/embedding-hypothesis-in-websites-and-platforms/

Which continues with an example of Hypothes.is client configuration.

Is it the best to put private vs public in the Contact Page? Or should it be separate?

I think it is best to include it in the Contact Page. Because my perception is that it's all about contacting me. But I should do a poll on this.

Also, this isn't just a Gout issue, so it needs to be addressed in other subject sites. And as it is a fundamental part of successful collaboration, I will repeat it in Food and Learning.