Total of 264 posts

Herein you’ll find articles on a very wide variety of topics about technology in the consumer space (mostly) and items of personal interest to me.

If you’d like to read my professional engineering articles and whitepapers, they can be found at Control System Space

I have also participated in and created several podcsts most notably Pragmatic and Causality and all of my podcasts can be found at The Engineered Network.

Fediverse Series: Definition

This third post in a series about the Fediverse focuses on micro-blogging platforms. My first introduction was to Mastodon, then Pleroma and finally most recently to Misskey. Let’s look briefly at each in turn.

Mastodon

Currently the most popular in terms of active users Mastodon (approximately 2,500+ servers) originated in late 2016 and is a complex application that uses a long list of frameworks and components to deliver what is considered to be the best Web-user interface experience at the moment for both end users and adminstators. However scaling the platform remains a concern and it is driven effectively by a single developer. It originally supported OStatus, but in v1.6 about a year after it launched it added ActivityPub support.

Pleroma

Launched informally in 2017 and like Mastodon, originally supported OStatus but later adopted ActivityPub though a tighter subset known as LitePub, in March 2018 and at time of writing, despite there being over 400 instances they are still running pre-v1 software with no formal release to date. Installation however is much simpler than Mastodon and can run on extremely low-capacity low-performance hardware as a result. It has a native web user interface which is similar to Twitter in some aspects, however also comes with the Mastodon-FE (Front-End) and supports the Mastodon v1 API allowing most Mastodon compliant client and server applications to work with it seamlessly.

Misskey

Reaching v1.0 in April 2018, Misskey is developed predominantly with a strong Japanese influence and elegant styling, conforming to the ActivityPub protocol and a very tidy web interface design. It has similar installation requirements to Mastodon though is considered easier to install and maintain and at time of writing has only 40 servers in operation with posts predominantly in Japanese, but gaining in popularity in other regions.

Server vs Instance and Application vs Fediverse

Let’s be clear, a server running the software for any of these three platforms on it, is “an instance” of that software. Hence you can consider an instance to be a server usually, but technically if you’re load-balancing then things get more hazy. Each instance is for a single domain or subdomain so it still makes sense to think of an instance by its domain name and not call it a server (technically).

It’s also better to separate the application names such as Misskey, Pleroma and Mastodon from the Federated protocol they utilise, such as OStatus and ActivityPub. During the OStatus era (which technically we’re still in however OStatus use is on the decline in favour of ActivityPub/LitePub) the term “Fediverse” was coined to describe the network of federated messaging between different platforms and applications using a common protocol. As naming goes it seems to have stuck, despite a suggestion to use IndieWeb and ActivityWeb and alternative naming conventions based on their current protocol names respectively.

What I’ve Installed

Well the Fediverse sees all, including my Mastodon and my Pleroma servers and tells the story. I’ve had no end of problems with my Mastodon server, with its higher VPS specification to run it, problematic upgrades and poor availability I decided to give Pleroma a shot and haven’t regretted it. They recently added web push notifications which was really great and my script authetication issues also work now so my automation scripts are behaving at last. Having said that make no mistake, they aren’t claiming it’s done yet and their current optimistic GitHub tag of v0.9.9 tells the story indirectly, though the Pleroma development team are keen to ensure it’s as solid as possible before touting a 1.0 release.

Under-the-hood Migration

To date swapping the server and messages under-the-hood as it were it isn’t supported. Meaning if you start up an instance using Mastodon with posts/toots/messages from that instance, becuase how messages are represented by the software on the server, it’s currently not possible to take a message list from one server, migrate the entire lot to a Pleroma server running different software on the same domain. I tried this and too many things broke.

I suspect migration may someday be possible but for now at least shifting to a different domain (or in my case, sub-domain) was the next best option.

No More Mastodon: FEDIVERSE

The truth is that I might set up a Misskey server someday, I might set up a blog that federates using Plume, WriteFreely or a Hugo-ActivityPub bridge might be developed, and I want to be able to describe the means to find me, NOT the technology. In modern conversation we might say “Send me an EMail”, we don’t say “Send me an Outlook” or “Send me a Thunderbird” which, well, could be interesting. In the same fashion I no longer intend to tell people to find me on Mastodon, or Pleroma, or whichever platform I’m using since they all Federate. You can find me now, on the Fediverse.

Updates Across the Board

To reflect this I’m adopting the proposed Fediverse iconongraphy on all of my sites, will be updating URLs, podcast intros/outtros you name it to reflect the Fediverse so when you hear me mention it you’ll know what and why. TEN was updated recently to reflect this.

So if you’re looking to get in touch, you can follow me on the Fediverse @chidgey@pleroma.engineered.space, just log into your Fediverse account on any instance of Misskey, Pleroma or Mastodon, type that into the search box and you’ll find me, follow/remote follow me and say ‘Hello’.

Catch you on the Fediverse everyone :)

Fediverse Series: Facebook

This second post in a series about the Fediverse (this one, somewhat more tangentially) focuses on the usefulness of Facebook pages as they relate to the future of TEN as it has been used as a Full-Length Blog Link MicroBlogging-page (of sorts). NOTE: I’m not going to be looking at all of the other ways Facebook is a problem, and if you want to look into Fediverse alternatives there are a few including Diaspora

Not wishing to re-hash the entirety of my previous post a quick refresher about Twinkblogs…Links to full-length Blogs posted as Microblog entries that aren’t intended to convey much other than a title and some brief text, drawing potential listeners to the episode in question. In that regard it’s the size of the audience you can reach through that channel that matters the most.

So far as feedback via mentions goes, if you’re interested in comments on your podcast then that’s something worth exploring and whilst Facebook had this functionality I seldom got comments via that page. Any feedback from readers is welcomed to either myself via the feedback form or via the Fediverse directly to me personally.

Federation support may someday include embedded audio and the simplicity of being able to consolidate into a single window is quite appealing. Unfortunately I remain concerned that such functionality is unlikely to be as fully featured or as useful as a dedicate podcast client application. For this reason until future support for federated posting via Hugo with embedded audio becomes a reality, it will remain off the table.

Facebook Page Algorithm

Lifting the mostly uninteresting curtain behind the TEN Facebook Page, the same number of posts occurred in 2018 as 2017. In 2018 only 3 Likes in 12 months, and all but six Notifications I received on the page came from Facebook helpfully suggesting “…people who like Engineered haven’t heard from you in a while…Write a post…” Uh-huh. Thanks. The reach of these posts expressed as a percentage of Like(s) in the month of December averaged 22%. Some 15 months earlier it exceeded 100% regularly.

Early in its life, Facebook encouraged businesses, groups, organisations to host their pages on Facebook for organic growth and a wide distribution. However changes to Facebooks algorithms in the past few years with dozens of weighting factors now used to tweak what people see in their timeline makes trying to get organic visibility essentially impossible unless you want to A) try to game the system (sounds like a full time job) or B) pay $43AUD to reach an additional 3,400 people per day, so claims another ‘helpful’ Notification from Facebook on the page. Uh-huh. No thanks.

Future Plans

Currently when a podcast episode goes up on TEN, an RSS Feed scraper takes a copy of the title, a URL link to the episode, then publishes it to a Mastodon account. From there a second script takes that and re-tweets it to the Engineered_Net Twitter account and Facebook is manually added later. With a significant following on Twitter the Engineered_Net account will remain for the immediate future. However the same can not be said of Facebook.

Based on the above Twinkblog rationale, manual posting requirements (Facebooks API requires regular re-authentication which is annoying), Facebook asking for money to ‘give back’ organic reach, and finally with my move to gradually step away from Facebook, I’ve decided to close the The Engineered Network page on Facebook. All other subscription methods will remain unchanged including RSS to Causality, Analytical and Pragmatic as well as the TEN Master Feed. My recommendation is that people that have Liked TEN on Facebook and use it for show notifications either follow the TEN Twitter account @Engineered_Net or better still, jump on the Fediverse somewhere and following me @chidgey@pleroma.engineered.space where I’m active every day.

Failing that just subscribe in your podcast player app of choice. There’s PocketCasts on Android and iOS, Overcast on iOS, and Apples Podcast app is also much improved in recent times as well.

Reflecting on podcast distribution for a moment: It’s funny (okay it isn’t…it’s brilliant!) how an open standard like RSS that powers podcast subscription and distribution remains the best option, whilst centralised platforms like Facebook, once they get big, turn-coat on everyone and charge for visibility. Hopefully this explains why so many people are leaving their Facebook pages and highlights some of the risks of using centralised, company controlled sites for notifications and distribution.

Fediverse Series: TechDistortion

This first post in a series about the Fediverse focuses on three aspects as they relate to the future of TechDistortion (this blog): Full-Length Blog Link MicroBlogging, WebMentions and Federation support (ActivityPub/LitePub/OStatus).

Twinkblog

Links to full-length Blogs posted as Microblog entries don’t intend to convey much other than a title and some brief text, drawing potential readers to the full article. I mentioned the phenomenon of Twinkblogs 5 years ago, but really it’s an avenue of communicating an article exists, not the content of the article itself. In that regard it’s the size of the audience you can reach through that channel that matters the most.

WebMention

IndieWeb are popularising the WebMention as a method of allowing users to reply to a blog or article with the article then able to aggregate all comments, mentions, reblogs as part of the article. Any WebMention compliant site would allow that interaction to occur creating a common point for all comments in a federated way between users from different accounts on different systems, like Disqus but not centralised and more flexible. If you’re interested in comments on your blog then that’s something worth exploring. I’ve never had comments enabled on TechDistortion in the decade I’ve been writing articles and don’t intend to add them now. Any feedback from readers is welcomed to either myself via the feedback form or via the Fediverse directly to me personally.

Federation

Not all platforms are so text-length restrictive as Twitter (280 characters) and Mastodon (500 characters) with Pleroma allowing administrators to set whatever limit they like. On my Pleroma instance I’ve left it at the default 5,000 characters but might change that at some point in the future. The idea is that using ActivityPub/LitePub a blog could be subscribed to as if it was a regular account on the Fediverse. That seems convenient however scrolling through a 9,000 character long article on a smartphone screen application intended for short posts might not be as clean an experience as a dedicated long-article reading application like Unread (for example). That said, the simplicity of being able to consolidate into a single window is quite appealing. Unfortunately when moving away from Statamic to Hugo, Federation wasn’t a thought I had in mind, and hence since neither supports Federation it will not be explored in the short term.

Future Plans

Currently when a blog entry goes up on TechDistortion, an RSS Feed scraper takes a copy of the title, a URL link to the article, then publishes it to a Mastodon account. From there a second script takes that and re-tweets it to the TechDistortion Twitter account. Currently counting the number of actual people and lists on the TechDistortion Twitter account, there are more real people subscribed to the sites RSS Feed directly and also to both my personal Mastodon and old Twitter accounts.

Based on the above Twinkblog rationale and also with my move to gradually step away from Twitter, I’ve decided to close the TechDistortion Twitter account. I will instead be posting those links only to my personal Fediverse account, which is copied to my ‘old’ personal Twitter account. RSS will always remain for anyone to subscribe to. My recommendation is that people following the blog on Twitter either follow my ‘old’ Twitter account @johnchidgey or better still, jump on the Fediverse somewhere and following me @chidgey@pleroma.engineered.space where I’m active every day.

In future if a Hugo–>Federation intermediary service is developed I’ll probably look into that, since I really like Hugo ;)

Thanks everyone.

Oh yeah…Happy New Year.