“By focusing on growth and growth only and ignoring the problems, they amassed a large set of cultural norms on their platforms…from harassment or abuse or bad behavior… they’re completely defensive and they can just never catch up on the problem.” http://nymag.com/selectall/2018/04/dan-mccomas-reddit-product-svp-and-imzy-founder-interview.html #indieweb

Why we need to bring back the vision of the read-write web

@matthilt There's a number of ways of doing this typically under the titles of POSSE or PESOS. Some for WordPress are documented here: https://indieweb.org/WordPress/Plugins#POSSE_Plugins
Specifically for Instagram, I think the majority use OwnYourGram.
Typically the more control you want over output for syndication means a bit more work upfront, while the easy solutions give you less control over how things look. Feel free to ask for opinions in chat as well either in the main channel or the #WordPress channel.

At @TheWebConf today or Tuesday? Do you post to your personal site? Find me for an @IndieWebCamp sticker!

Episode 2: IndieAuth

This Week in the IndieWeb Audio Edition • April 14th - 20th, 2018

#podcast #IndieWeb #this-week-indieweb-podcast

"On this day..." reminded me that I set up my user page on indieweb.org exactly a year ago. I don't think I'd updated it since and it was sorely out of date. Fixed!

I'm going!

Can’t wait! IndieWeb Summit was one of my favorite events last year. Really looking forward to seeing what’s changed since last summer. More importantly, looking forward to catching up with everyone and hopefully meeting some new folks as well!

Yeah, that’s great to reduce mental pressure. The options already exist for each channel to either not track read/unread status, only show an unread indicator (the read dot in the screenshot) or to display unread counts. I actually find that not knowing the unread count in many cases creates MORE mental pressure because I don’t know how many are there. I do use it in select cases like the Saved and IndieWeb tweets channels.

Promises

Liked: Wrapping My Head Around Micro.blog and IndieWeb – JSON Writes...

Even the IndieWeb website doesn’t do a great job of explaining what it is, or what it means to “join the IndieWeb”. As far as I can tell, it’s a collection of practices and technologies that connects independent blog-type websites together into a quasi social network.

In discussing micro.blog and the #indieweb, Jason makes a valid point which others, and myself, have echoed. Social networks are so ingrained, so easy and so obvious that people don't need to think about them. It's by design, of course - make them sticky, make them frictionless.

To have to put real effort into what you are doing and actually adopt a philosophy for how you engage on the web is further than many are willing to go without having a real sense of why they should or what benefits they might gain from it.

As much as the technology needs to be easy to use the rationale is, perhaps, more important.

The Social Web

Homebrew Website Club Baltimore

#event #HWC #IWC #IndieWeb #HWCBaltimore
@dajbelshaw Noterlive is primarily a posting interface to Twitter (mostly for livetweeting though it could continue to add some of that functionality in the future) that gives you back your data. You would still want to pay some attention to your account for side conversations and replies as well as other conference activity. In many cases I use it primarily as a note taking tool to keep content for archival purposes after the fact.

For additional two-way interaction you could use WordPress plugins like Webmention and Brid.gy Publish to get the comments, likes, etc. back to your website. I've outlined a piece of that type of workflow here: http://boffosocko.com/2017/04/15/mentions-from-twitter-to-my-website/ (This might also be useful to you if you've left Twitter, but still want to know when you're being mentioned without needing to log into Twitter to check it.)

Otherwise, you might also consider going full IndieWeb, in which case you could post everything directly from your website and syndicate to Twitter and then getting all the responses directly back to your site. Some of this depends on how much work you want to do to get the moving pieces working properly. You'll notice this is roughly what I'm doing on my own site with you now. Example: http://stream.boffosocko.com/2018/dajbelshaw-in-future-if-you-prefer-to-keep-your-content

@jgmac1106 I've often wondered about potential expanded vocabularies for microformats within the educational space. I know many use a variety of other metadata including schema and dublin core, but I've never really come across any application which consume these or do anything useful for them other than add an administrative tax to the user who are doing them. Perhaps we should begin documenting some of them to build a more long term valuable solution?
@jgmac1106 Perhaps we might create and use a corner of the IndieWeb wiki to begin documenting the use of these types of things? We could start on the https://indieweb.org/Indieweb_for_Education page and subsection them out as they grow in size and scope? If there are consuming applications for differing types of metadata, let's list those. The best answer may be to begin documenting pieces of what are out there and then figuring out a way to create more IndieWeb or decentralized and open versions of them. Having an editable, but centralized source of information can certainly be helpful. (Unless you know of another that already exists?)

Photography, Graves Disease, Insulin pumps and a lot of other things

Improving the h-card in Grav

I spent a little time fixing up the way this site presents my h-card on the summary of blog posts. In case you're wondering, an h-card is a way of presenting information about yourself or your organisation on your website that makes it easy for other websites to identify you with your work, for example in webmentions. More this way ...
There is also the counterpart: 'untag-of' posts (https://indieweb.org/untag) which are more of a brainstorm at this point, but I figured worth pointing out as a future enhancement, in case that helps generalize the code for 'tag-of' support.

Problem: currently you have to use Github’s web UI to remove a label from an issue.

If you could post an 'untag-of' response to a GitHub issue, and Bridgy Publish recognized that, it could call the GitHub API to (attempt to) remove the respective label from that issue.

The current brainstormed markup is similar to that for a 'tag-of' post, but with class name 'untag-of' instead.

Feedback and contributions welcome on https://indieweb.org/untag

Also reasonable to consider 'untag-of' support a potential future separate issue rather than as part of implementing 'tag-of' support.