In fact, there has been conversation lately about how nickname caches are really just h-cards. If you take that and the conversations around collections, you can make private collections of h-cards to essentially create lists. This would be an h-card with children h-cards. You could even use this to say represent your co-workers if you had an h-card collection with the info of your employer and then it had children h-cards of the employees of the company, you could then easily share certain items with your co-workers.
This means I can post a code snippet, select some specific lines and then share the resulting url with fragment to someone and the code snippet will automatically highlight the specific lines to them. Also, the possibility exists that someone could include a code line fragment in the url when sending a webmention to my code snippet and like media fragment, I would then be able to consume the code line fragment and associate the webmention with the specific code snippet lines.
One more step towards owning my own data AND replacing GitHub functionality through distributed means.
They came to the conclusion that there are four groups of people that you want to treat their responses differently:
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.
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.
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.
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.
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:
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.
So where do we go from here? Now that we can read and interact with people quickly and easier the question is how we manage those people? I think that is one of the next large hurtles for the IndieWeb community to overcome.
There are a couple aspects to this:
The first step following someone is that you end up on someone's website and you want to subscribe to their content. Currently that involves:
That's at minimum 5 discrete steps and it prevents me from subscribing to new feeds all the time. Most of the time I use my iPhone's share sheet to send the url into my task manager with a task "Follow this site". Then, I get lazy and I never sit down and actually follow them until something significant happens and reminds me, then I will eventually do it.
There are two ways we can and should solve this problem, in Native Apps and on the Web.
One of my open source projects is Indigenous for iOS, which is a native iOS social reader. Native Apps can make this a lot easier by integrating subscribing to feeds in the share sheets.
In this scenario, you would visit the page you want to subscribe to, tap the share sheet, tap your native app and tap Follow. It would then allow you to select a channel and a feed type if there are multiple available. You could also preview the different feeds before selecting if you aren't sure which one you want. There are several taps but they are all pretty easy and intuitive without having to open new browser tabs or apps.
Option 1: Follow Buttons Before the social readers got going, Aaron experimented with a subscription workflow on his website. At the bottom of his feed pages he includes a button that says "Follow".
When you click that button it takes you to a new page that allows you to select one of three feeds to subscribe to (the current page, his home page and all posts) while providing information on how many posts that feed has received in the last 30 days. Then you enter your url and click follow.
Aaron's website will look at your website for a rel="subscribe" link, then it will forward you to that url with a query parameter at the end (?subscribe-to=http://url.com/of/feed). This would then allow the social reader of your choice to bring up a subscribe screen with the url already pre-filled. This allows the web interaction to then mirror the native app interaction very similarly. One downfall is that not every website will end up providing follow buttons. What is an alternative?
Option 2: Browser extensions While I think it would be useful for many websites to implement that type of interaction, some just won't and others can't (for example: static-sites).
Another option is adding Microsub support through browser extensions. For example, Omnibear could add Microsub support for scanning the current website for feeds and allowing a user to subscribe to a feed from their current page. This would allow following functionality similar to a native mobile app but from any desktop browser that has the extension installed. One added benefit compared to the follow button is that you don't have to enter your url into a website, because you will already be logged in to your browser extension.
So now you've made it easy to be visiting a website with a feed and to subscribe to that feed within a channel of your social reader. What is missing when compared to social silos today? Well typically you can notify that person that you are following them as well as their information gets added to your website so you can communicate with them more easily, and more. I think the two missing pieces there are the (optional) notification issue and storing their information in your website for easier communication.
Because of the way that social readers enable two way communication, most of them will not only have access to your Microsub server but also your Micropub server. This means that with your permission when you subscribe to a new feed, a Microsub client could also create a follow post through your Micropub server. Your micropub server would of course handle this anyway it saw fit (making them public posts, private posts, sending webmentions, etc).
The other missing piece is the fact that when you follow someone, often times this is also an indication that you want to communicate with them. So far, brainstorming on easing communication has come in the form of a nicknames cache. They haven't taken off too much, and I think one reason for that is there is no easy way to add and maintain a nicknames cache unless you build an interface for it, and who enjoys manually maintaining contacts anyway?
One interesting use case of following is that when you subscribe to someone's feed and begin "following" them, the Microsub client could ALSO parse the author information and then send a Micropub post to your server of an h-card as opposed to an h-entry or h-event. When your Micropub server receives an h-card object it can know that this should be stored in your nicknames cache instead of as a post on your website.
Nicknames caches provide support so that a Micropub client can help to auto-complete personal contacts as well as potentially dealing with @-mentions across services or silos.
When you combine this with the experimental Micropub extension for Querying for post list, you could potentially maintain your nicknames cache through Micropub, retrieving existing entries by using q=source&post-type=card.
Of course, once this is all done it would be super useful to create a Micropub Card <-> CardDAV bridge so that without everyone having to worry about the CardDAV spec, nicknames caches could also become our phone's contact list. Maybe card.brid.gy, Ryan?
I have downloaded some historical Facebook content, but definitely have a long way to go on that journey. Instagram however has become much easier. Thanks to Manton Reece, the creator of Micro.blog I was able to use the Micro.blog macOS app (Which is a Micropub app so it works natively with my website) to Import my Instagram Archive using the instructions provided by Micro.blog.
As of today, I now have all my previous Instagram content on my own website. One of the best parts about this is that I was able to import all of 2012 photos which was the year my wife Ashley and I courted, and all the 2013 photos which was our first year of marriage.
In order to make sure all the photos came in, I also built a new view into my website that allows me to display a grid of my photos by year, month or day. I'm pretty excited about how my website is developing this year. I'll have more to say about how my website is developing in Part 2 of My IndieWeb Story, coming soon.
After recording the microcast, I spent on time playing around with some homepage redesigns and came up with one I decided to start trying out and I actually pushed it up to become the new live homepage of my site. I've included some screenshots in case it changes over time:
The focus on the homepage was to introduce me, what I've been doing recently, show some recent articles, microposts (kind of like tweets but hosted on my own website) and social responses.
I was feeling pretty good about my direction, and then I received an email from Manuel, which completely surprised me! Among other things he said something that stuck with me:
My only thought about your current site/idea is to don't add too many things.
People already live in a cluttered world, both digitally and physically and it's refreshing to land on a site where there are just a few things you must look at and you're not distracted by the latest tweet and photo and video and activity so on an so forth.
I think this makes a lot of sense. It also battles against my desire to kind of have a "homebase dashboard" that outlines what I've been up to recently. This has led me to thinking through do I want a single site, EddieHinkle.com that contains everything about me, or do I want some smaller separate sites that host smaller focused segments of my life. Not everyone wants everything about my life, so it makes sense that it could be broken up into smaller segments.
I started in this general direction earlier this year when I created 30andcounting.me which was created because I wanted to host my microcast on Micro.blog and so when doing that, I thought it would be nice to give it it's own domain. However, recently, I felt like I missed being able to reference the microcast from EddieHinkle.com so while the "canonical" copy of my microcast is still hosted on Micro.blog, I have been creating copies on EddieHinkle.com.
So as I was pondering this, I was looking around and noticed that Chad is the author of Where the Light Gathers, and I checked out his personal site. It was an interesting idea to me, his identity url (his name), is a landing page that introduces himself points you into some general directions: About, Now, Social, Blog. It got me thinking I could do something similar.
I could potentially see EddieHinkle.com being a landing page similar to Chad's where it introduces myself simply and provides links to an about page, a now page, a social page, a microcast page and a blog page. I already own the domain Eddie.today which currently just links to EddieHinkle.com so what if I created the following sites:
eddiehinkle.com (Landing Page/About Page)
eddie.today (Now Page that looks similar to the current EddieHinkle.com homepage)
micro.eddiehinkle.com (A social site that lists my microposts/photos/etc)
30andcounting.me (My microcast website)
TBD (A minimalistic blog site for my long-form articles)
So that's what I've been thinking through and am interested in your feedback on, either by email, Micro.blog or Webmention. What do you think about the idea of either separate content/identities or having a single location for all the information on a single person? Is the idea I've been thinking about good and taking it in a direction of simplicity? Or did I completely miss the point and just make every messier?