Embracing IndieWeb can at times feel overwhelming. But it’s the amazing implementations that keep me inspired - ones from the likes of Barnaby Walters, @adactio (Jeremy Keith), Kartik Prabhu, and many more. Over to Micropub now.
I have enabled an extremely basic processing and display of two types of posts - likes and replies. However, am still not sure the possible activity types as responses from webmention.io in documentation. Any idea @aaronpk?
On my journey towards embracing IndieWeb, achieved - identify via microformats2, IndieAuth enabled, webmention addressed - receive and send mentions and of course, micro.blog syndication. Couple of open items - significance of h-entry for posts, way to process and display incoming webmentions.
Experimentation continues with IndieWeb projects — over to Webmentions. It is a really wonderful concept which enables responses to a post to be written on one’s own website. As Jeremy Keith wrote in one of his posts:
Basically, it’s an equivalent to pingback. Let’s say I write something here on adactio.com. Suppose that prompts you to write something in response on your own site. A web mention is a way for you to let me know that your response exists.
Even better, and simpler to follow explanation is put out by Drew Mclellan detailing what’s involved in implementing webmentions.
The flow goes something like this.
- Frankie posts a blog entry.
- Alex has thoughts in response, so also posts a blog entry linking to
- Alex’s publishing software finds the link and fetches Frankie’s post, finding the URL of Frankie’s Webmention endpoint in the document.
- Alex’s software sends a notification to the endpoint.
- Frankie’s software then fetches Alex’s post to verify that it really does link back, and then chooses how to display the reaction alongside Frankie’s post.
The end result is that by being notified of the external reaction, the publisher is able to aggregate those reactions and collect them together with the original content.
I have got the webmentions (and pingbacks) enabled here — over to testing now. So there you have it. This post is also an attempt at sending a webmention.
Today has really been extremely productive. I have got many of the things sorted out. Posting from a workable CMS (thanks Netlify CMS), crossposting to twitter and of course to micro.blog. Delighted!
Exploring the option to enable an editorial process in CMS. So that a draft can be saved first before it is published. This will be a nice option to have for longer post.
Interest behavior. Understood how it works. It satisfies my needs. A post passes through multiple stages. For me, only important stages are save and publish. Trying Ready anyway.
Managed to solve the problem with avoiding issue with including title for microblog in crossposting. Solution? Of course, involved fixing the RSS feed — relevant even today.
It’s been about 6 months now that I got my static site up with Hugo. Pretty satisfied with what I’ve got running. However, though I am digging posting on mobile as git commits, I’ve been in need of a lite, static CMS. Exploring Netlify CMS.
Problem I am currently facing with Netlify CMS is it defaults to the title as filename for a new post. I do not want to use any for the journal entries, especially to keep crossposting simple.
I am since long fascinated by IndieWeb and multiple projects the guys are working on. One project that recently got me hooked is micro.blog. I have since been working on different feeds to get a custom microblogging of my own. The concept is great. And so looks the implementation. Time for some experiment.
How Dark Patterns are employed by health insurers
Dark patterns, dark algorithms, dark user experiences, what is that? You might ask. I will define them as the following for this piece:
Dark pattern - anything designed for malintention
Dark algorithm - an algorithm that is designed as a dark pattern
Dark UX - a user flow on the internet that is designed as a dark pattern
All of these patterns are designed intentionally, or if not, are the act of serious neglect. It was also super hard to aggregate these as recurring issues because there is no central place to discuss these issues and their prevelance, since sickness is taboo.
Ok cool, so how do these manifest in health insurance, you might ask?
Another reminder that businesses and their owners are inclined, or even at times duty-bound, to maximise the earnings for the stakeholders. Every day, the boundaries on what should be perceived as morally corrupt just get pushed farther.
It’s a troubling trend then that we are training the machines to do the same for us — imparting intelligence to maximise benefits for organisations who build these AI systems. A fascinating thread this that captures the fallouts of such training purely geared towards such optimisations.
Almost 10 years ago I had a prototype where I played around with using a simple genetic algorithm to breed enemies that would be good against whatever play style you chose. The fitness function in it was just how long they could stay alive against you
— Tyler Glaiel (@TylerGlaiel) January 18, 2018
if you optimize games for money you get mobile lootbox garbage. if you optimize videos for watch time you get vlogs that are 95% filler. if you optimize social media posts for view counts you get clickbait, lies, and freebooting
— Tyler Glaiel (@TylerGlaiel) January 18, 2018
AI is really good at finding local minimums and maximums. Like "oh, promoting 45 minute videos gets more watch time than 5 minute videos". Its terrible at recognizing that promoting that kind of garbage will eventually cause people to leave for better platforms
— Tyler Glaiel (@TylerGlaiel) January 18, 2018