Similar Posts
The Apple Watch Series 3
The Apple Watch Series 3 is more interesting than I thought it would be, I like that it plays nicely with Strava and that it is possible to track shorter duration activities without worrying about battery life. I found that it loses about ten percent per hour. This is fine for most people.
Daily goals
Another feature that I like is that it measures daily goals in standing, calories and activity. The standing and activity goals are easy to beat on a daily basis. Standing 1 minute every hour is tremendously easy when you’re not driving or flying. It’s the activities goal that I find most relevant.
With previous devices that I have used, whether Fitbit or fitness apps on android or iOS they usually give you a daily step goal but if you go for a long bike ride or go climbing you will miss the step goal. With calories burned everything you do counts towards that goal.
With the workout
Better integration with Strava and other apps
I would like to see better exportability of data. With the Suunto Spartan Wrist HR
It is for this reason that I track cycling and hikes with both the Suunto watch and the Apple watch series 3.
Other comments
I don’t know what the heart rate variability data means so I don’t know whether to see the data as positive or negative. It is a shame that with most news apps we can read the headline and sub-heading but not much else. I wish that we could type messages rather than choose from presets. It is not as versatile as I would like from such a device.
Assessment
This is a watch perfectly suited to cycling, hiking and other activities as long as they do not exceed eight hours of activity. It is well suited for when you’re walking in town, cycling in the countryside or climbing. Tracking calories, rather than steps, is a great way of giving people sporting flexibility. It’s a practical introduction to sports tracking watches.
D-Day Film archives on Facebook
Yesterday D-Day Film Archives were shared on Facebook. These film archives were of landing crafts landing troops on the beaches, of battleships firing rocket salvos at the coast, of gliders being pulled by planes, of paratroopers getting and more.
Over the years films have been preserved by transferring the footage from one film stock to another and then transferred from film to tapes. The problem with film and tape is that they are stored in a physical location that only archivists have access to. This means that if we’re curious about seeing the footage, like the footage included in this post we would have to go to the film archive and ask for permission to see this footage. Within a few hours, days or weeks we might get an answer. We would have transport costs, access costs and more.
The advantage of digital video archives accessible online is that everything is accessible within a few seconds with the right keywords. This means that a child hearing about the Second World War for the first time can do a quick search and see this footage. History, rather than being words on a page, is brought to life. It stops being an abstract subject for the mind. In this footage, we see our grandparents and our nephews and nieces see their great-grandparents.
An effort, by the international community, should be made to preserve, digitise and then make available as much of this film material as possible. The technology exists today so that, at the very least, we can have digital backups of all of this material and in the best case scenario for this material to be available for future generations to watch and study.
I have already spent 15 months as a video archivist and media asset manager and I would like to continue this line of work. I find it to be a fascinating and interesting way to learn about history. It inspires to find books that contextualise the material that I am seeing on screen. This material makes us more informed citizens of the society in which we live.
Using WordPress as a Fediverse Instance
Over a period of a few days I have turned my WordPress blog into a fediverse instance. The process took some trial and error. In the end it was quit easy and there are three steps.
Step One: Have a WordPress Instance
The first step is to have a WordPress blog/CMS. You can start with an existing website, that you are willing to have on the fediverse, or you can install the WordPress CMS in another director and use that as a dedicated Fediverse CMS.
Step Two
Go the the plugins tab and add the activityPub plugin. Once this is done your blog will work as a fediverse instance. When someone subscribes to your instance via Calckey they will be able to read entire blog posts within Calckey, as if the blog was written natively. They can also comment but this is one way. You will need to check for comments and replies manually.
Step Three
The third step is to install the webfinger plugin for wordpress. This was the most complicated challenge for me, because webfinger expects to find the .well-known directory in the root of the website rather than the directory where the blog may actually be.
If your blog is in the root then you’re fine, your WordPress blog is now a Fediverse instance.
If you’re like me, and webfinger points to the wrong place then I have a simple solution.
Go to the webfinger lookup url and type your username. It will show you a get https line with where it expects to find your json file. Copy this into the URL bar but type the correct path. You will know you wrote it correctly when you get some JSON data. Copy this data and paste it into a file called webfinger.json.
Create a .well-known directory in the web rooot folder of your site. Add the webfinger.json file to this directory. Go back to the webfinger lookup page and check that your username@domain works correctly. If it returns the right json you’re in. Your blog is now a Fediverse instance
The Complicated Alternative
The advice I give for step three is the advice I would have liked to receive. People suggested that I change the htaccess file, which I tried to do, but without success. If you do attempt to change the htaccess file keep an unmodified backup in case you break something. I wouldn’t recommend experimenting with the htaccess file. The webfinger.json solution is simple and intuitive.
Why Does This Matter
The pre-requisites for installing Mastodon instances require permissions that we might not have on the host we are currently using. This limits what we are able to do. By having WordPress and the ActivityPub plugin and Webfinger we are able to bypass several barriers and get a fediverse instance running within minutes and in theory anyone can do it. Anyone that is familiar with WordPress.
And Finally
On Mastodon blog posts are shown as links to articles. People still have to visit the blog. If and when people comment on the mastodon toot those comments are added to the blog post comments, and vice versa.
With Calckey the blog posts that you write in WordPress display natively in Calckey. It does remove formatting however, so that’s something to work on. People that comment on the calckey post will be visible in the blog posts and vice versa. It’s native integration. It works well.
Now, when we write blog posts, people can see them directly in the fediverse, without having to browse away, especially with Calckey integration. In theory your blog post is not a blog post. It’s a note. This seamless integration should bring new life into blog posts. What I find especially amusing is that my blog already has 2100+ posts, in theory. In practice it has many more. People do not see legacy posts. They only see posts from the moment they start following on Mastodon or Calckey.