We are nearing the release date for WordPress 5.0 and Gutenberg, one of the most important and exciting projects I’ve worked on in my 15 years with this community. I knew we would be taking a big leap. But it’s a leap we need to take, and I think the end result is going to open up many new oppo...
Companies and apps constantly ask for ratings, but all that data may just be noise in the system.
A great framing of a lot of crazy digital exhaust that online services and apps are collecting that don’t do much. I’ve also thought for a while about the idea of signal to noise ratio of these types of data as well as their quantization levels which often don’t make much sense to me. I don’t think that there are any IndieWeb realizations of these sorts of (mostly business) systems in the wild yet, but this is an important area to begin to consider when they do.Syndicated copies to:
For some time, we have been considering how we could open up compatibility between Micro.blog and Mastodon. Any feature that could be disruptive needs to be approached carefully. In this post I want to talk about how Micro.blog supports Mastodon, why I think it’s useful, and anticipate some questi...
There’s some awesome new functionality in micro.blog now. It looks like it’s still got some work to come, but, ideally, this is how most websites will work in the near future.Syndicated copies to:
I remotely attended the Displaying Responses session of IndieWebCamp Berlin 2018. It was very interesting and they made some good progress thinking though how to deal with how and when to display responses received to posts on your website. They came to the conclusion that there are four groups of people that you want to treat their responses differently: Accepted / Immediate Connections 2nd level connections Everyone Mute or Blocked Accepted / Immediate Connections These are essentially your friends on Facebook or your follow list on Twitter. These are people that you have chosen to connect with in some way and this logical conclusions can be drawn around the level of interactions you're willing to have. My plan is to display these responses completely (name, photo and content of response). This list will be generated for me by adding anyone I follow, as well as anyone I have sent a reply to. This will NOT add people to whom I have liked, emoji reacted, quoted, or bookmarked. Those are lower level responses that do not indicate a deeper level of a desire to connect with that person. 2nd Level Connections These are "friends of friends". You can assume they won't do anything TOO bad, but you might not want them posting all over your site. There is a deeper level of trust here because of mutual connection but still some care should be taken. This can be determined through different ways. One way that has been brainstormed in the IndieWeb is Vouch. I don't currently track 2nd level connections but I liked how Tantek thought this through, so my plan is for replies to display their photo and name as "other people that have responded to this post", but not display the content of their reply. I also think if they send a like, emoji reaction or quote, I'll display it just like I would an Immediate Connection. Everyone This is the World Wide Web, and anyone could send anything to my website via webmention. So this is a category you likely want to moderate. My initial thought is I will accept likes, quotes and emoji reactions from them but I won't list attribution of who did it while moderated, just the reaction itself. For replies I am considering potentially listing the url of the author of the post under "other people who have replied" but no name, photo or content while moderated. Mute or Blocked These are people who you do not trust for whatever reasons have happened for you. You don't want to associate with them in any way. Responses are not displayed from these people and they are not listed in the moderation queue. Some thoughts on moderation This means I'll need a moderation queue. Anything from a 2nd level connection or from the Everyone group will enter the moderation queue. Responses from 2nd level connections should appear higher in the queue than responses from the Everyone group. From there I can choose to: approve a response (display it like an immediate connection) approve response and accept author (makes this author an immediate connection so they aren't moderated anymore) ignore response (this leaves the response as is, it leaves the queue but doesn't display additional details) remove response (this removes the response from my storage) remove response and block author (this both removes the response from my storage and makes sure I don't receive responses from them in the future) All in all, it was a great session that I really enjoyed and I'm looking forward to actually working on implementing some of these features into my site.
A well laid out synopsis of how this could be done well. Filing for future templating.Syndicated copies to:
This year is marked as the ‘Year of the Reader’, and indeed, there was a lot of Reader talk last weekend. I really like the progress we are making with Microsub and apps like Indigenous, but I also noticed we’re not there yet for me. But that’s not a discouragement, quite the opposite!
This blogpost has three parts: first I describe the painpoints I feel at the moment, then I describe what I have been hacking on yesterday, and in the last part I share some other ideas we talked about over dinner in Nürnberg, that where not recorded in any form other than short notes on some phones.
Highlights, Quotes, Annotations, & Marginalia
this is another single point of Aaron in our stack. ❧
As opposed to another single point of Ryan….
November 08, 2018 at 08:59AM
I have discovered new interesting posts by looking at the likes my friends post. ❧
November 08, 2018 at 09:07AM
More ways to combat feed overwhelm
Before IndieWebCamp, we had a discussion about Readers in a traditional Nürnberger restaurant. Here also, people came up with some ideas to deal with accruing unread-counts.
One idea came from how Aperture deletes posts after 7 days. This actually prevents the overload. It would be nice if you can tell your reader that, for example your Twitter feed, is ephemeral and that the posts can be discarded if you did not read them in time.
One other idea that came up was to keep track of the average time between posts of a certain feed. This way a Reader could boost posts when they are from a feed that is not regularly updated. These kind of posts are usually lost in piles of more posts from more frequently updates feeds.
Yet a last idea was to tell your reader to leave out posts with certain words for a small period of time. This can come in handy when you haven’t watched the newest episode of Game of Thrones yet, but want to stay connected to your feeds without spoilers. ❧
Some good ideas here to deal with feeds.
November 08, 2018 at 09:10AM
In every start-up we have sleepless nights. Yet nothing kept us up more than the pain of trying to add new data processing servers to each of the three instances we added to https://nuevacastra.glitch.me. At first we started each instance off on a small stream of data. It was a very bespoke system a...
Want to see what the bleeding edge of the web and the future of social media looks like? Join an inclusive and welcoming group of creators at IndieWebCamp NYC on 9/28-29 either in person or live streaming.
You don’t see it until you’re right there, and even then, you remain confused. Did you miss a turn in the road, or misread the map? You are now driving through someone’s yard, or maybe even their house. You slow to a stop.
On rural road R575, also known as the Ring of Beara and more recently rebranded as part of the Wild Atlantic Way, you are making your way along the northern coast of the Beara Peninsula in far southwestern Ireland. You are in the hamlet of Gortahig, between Eyeries, a multicolored strip of connected houses on the bay, and Allihies, where the copper mines once flourished. The road, like the landscape, is raw, and it is disconcertingly narrow, often too narrow for two cars to pass one another.
An interesting example of how small local decisions can have complex and interesting ramifications in the future.Syndicated copies to:
“Gutenberg” is the codename for the new WordPress editor focus. The goal of this focus is to create a new post and page editing experience that makes it easy for anyone to create rich post layouts. This was the kickoff goal: The editor will endeavour to create a new page and post building experi...
(Further update: webmentions are working!!!) (UPDATE: It’s now been a year since I first posted this. Just today I discovered a year-old blog post which mentioned this one, and an ensuing discussion. Of course I knew nothing of this because – well, I couldn’t get webmentions to work! I have ...
I tinker on my own website and frequently write about IndieWeb related technologies because the web is my social media platform. The feed you might appreciate most is https://boffosocko.com/category/indieweb/feed/.
I have feeds for nearly every tag/category or post type on my site for convenience (just add
/feed/ to almost anything). You could subscribe to my firehose feed, but I suspect even my mother would tire of it quickly.
I’m curious if you have OPML files or similar bundles of feeds you follow that are shareable or subscribe-able?Syndicated copies to:
If you've ever developed software you've surely had users ask you to add an option. "Rather than forcing everyone into behavior A," they'll reason, "why not add an option so users can choose between behaviors A and B?" This post is an attempt at producing a canonical consolidated answer to why the answer to this is often "no".