feed

TIL my wife sometimes checks my website. She asked me out of nowhere why was there so much snow here and I didn't even know where to begin.

But you do realise you proved my point a bit? If one needs to go searching the GitHub issues to figure out how to do it, then people would need to be really motivated to do it.

I completely agree with this. A big challenge for me has been finding the right example that is maybe linked in the wiki. When nothing is found I usually ask at HWC and get more pieces of the puzzle but in cases where something isn't defined as well as other things, like watch posts, it's a dead end.

And yet, sometimes I have a feeling that people (not you personally) just sort of assume that we all understand the microformats.

This is specially important in this case. When there's not an example anywhere it's up to the person that wants to define the microformats to do it. For me it's a bit intimidating and I have struggled with this because I don't think I understand enough and sometimes do it completely wrong.

Luckily like you mentioned in your reply to gRegor, people I've interacted with in the IndieWeb have always been very helpful and I have not felt judgement for being wrong. But I don't know if this would be immediately apparent to a newcomer.

Not sure what the rule is but based on the length it feels like that reply should've been an article.

I brought it up again at HWC Pacific since its one of the main ways I use my site and the lack of consensus has always bothered me.

I create watch posts with sparkles where the u-watch-of property is an h-cite with name, year, IMDB ID, and IMDB URL. I also add a rating and progress which can be "want", "started", or "finished" based on these discussions.

In the watched feed they used to be h-reviews but was pointed to this discussion about switching over to h-entry with an u-review-of at HWC. Not 100% on board but it feels better than h-review.

If we take RSVPs as an example where a in-reply-to and rsvp means its an RSVP post, it would seem like an h-entry with a p-rating is enough to classify a post as an review. This way we could review a u-watch-of, u-read-of, or anything else. I think there might be a conflict if a post where to have a u-watch-of and a separate property (location for example) where the question would be: Is this review of the movie, the venue, or seeing the movie at this venue.

For now, this is how I'm using watch posts. I need to start adding some of this stuff to the wiki and other discussions since it feels like if someone were to want to add watch posts they could either use this as a starting point or tell me how it can be improved.

Inspired by James and Mark's holiday decorations, I decided to add a winter theme to my site. If you're patient, you might even get to experience what a MN winter is like.

This is old news but I find it annoying that last.fm's API does not return a valid image for artists. None of the other APIs I've tried are great either so this might just be something I'm going to have to be OK with.

I'm not sure who's also using my micropub endpoint implementation but I've been thinking about doing a major refactor for it.

My plan is to finally split it up into different libraries and finally stop the need to fork the full repo to run it for yourself.

This might be my goal for this years IndieWeb Gift Calendar.

Not sure if the test from the other day worked but I'm realizing I need to start writing more.

Retry this test