👓 Your Licenses? Frankly My Dear… | CogDogBlog

Read Your Licenses? Frankly My Dear… by Alan Levine (CogDogBlog)
I have openly shared, published online, gave away the store on just about everything I have created since getting into ed-tech in the early 1990s (c.f. “old dude”). I did this before there was a Creative Commons, I embrace and advocate CC, yet I don’t find all that much interesting in debating the various license flavors. While I understand the reasons for having so many two letter alphabet combos to string along after CC BY, frankly my dear, I think there are way too many of them. I’d rather be making stuff than dissecting licenses.

tl;dr: Is it really worth the effort to put a license on anything? Who’s going to steal it? And if they do, god bless them.

I could go with this…

Syndicated copies to:

8 thoughts on “👓 Your Licenses? Frankly My Dear… | CogDogBlog”

  1. Chris, I think something is broken on your site. I tried replying to this piece using the Webmentions WordPress plugin but it kept getting blanks entries. I made my post and then tried that using the “PING ME!” form but I got this error response.

    {“code”:”target_not_found”,”message”:”Cannot find target link”,”data”:{“status”:400}}

    1. Khürt, a webmention wasn’t sent to my site because the URL for my post doesn’t appear on your page. The URL you’ve wrapped around my name in your post is the permalink for your post instead. The better option is to put my URL into the URL field in the Post Kinds meta box in the admin UI as seen here: http://boffosocko.com/2017/08/11/post-kinds-plugin-for-wordpress/#How+to+use+Post+Kinds+in+practice
      This will cause the URL to be wrapped with the appropriate microformat class “u-in-reply-to” that will trigger your webmention plugin and send your response to me. Without my URL on your page, the webmention plugin won’t send me one, and then on my end, my page won’t accept a webmention if your page doesn’t have my URL on it.

        1. Khürt, I’ve figured it out then. I’d seen the issue I initially thought you were having a few dozen times.
          Your actual issue is far more subtle, but is a known issue with WordPress. Because the title of my original post contains the glasses emoji (indicating it’s a “read” post, or something that I read and made some sort of comment on), WordPress “eats” or filters out all of the data you’re trying to save. If you put the URL in again and then retrieve the data, but this time delete out just that pesky emoji, it should save properly as you expect it. Let me know if that doesn’t work.
          I’ve noticed the issue before and reported it officially here: https://github.com/dshanske/indieweb-post-kinds/issues/117

  2. @khurtwilliams Kudos for your tenacity! I just saw your notes on my site. The first http://boffosocko.com/2017/10/28/content-bloat-privacy-archives-peter-molnar/#comment-37986 appears to have been sent first as the webmention. The second two (http://boffosocko.com/2017/10/28/content-bloat-privacy-archives-peter-molnar/#comment-37984 and http://boffosocko.com/2017/10/28/content-bloat-privacy-archives-peter-molnar/#comment-37985) appear to have been input manually in the comment section of my site.
    I’m guessing you didn’t see (or possibly get the webmention–unless you’re careful WordPress can often put webmentions into your spam queue) my other reply the other day that explained the issue. You can find it here (http://stream.boffosocko.com/2017/kh%C3%BCrt-ive-figured-it-out-then-id-seen-the-issue or here threaded into the commentary http://boffosocko.com/2017/10/25/your-licenses-frankly-my-dear-cogdogblog/#comment-37780), but I’ll also manually syndicate my replies to you as well. Hopefully the explanation will solve your mystery.
    By the way, once you fixed the URL on your first original webmention, it did come through and is listed in the Mentions subsection at the bottom of the comments: http://boffosocko.com/2017/10/25/your-licenses-frankly-my-dear-cogdogblog/#comments It shows up as a mention instead of a reply, because the URL that fed through was the raw one (i.e. without a class in the body of your response). If you fix the emoji portion and click save that URL will have a u-in-reply-to which should cause your response to show up and be parsed properly as a reply instead of just a vanilla mention).
    If you’d like to discuss the subtleties of any of this in person, feel free to catch me on my phone number on my homepage. 🙂

    Syndicated copies to:

Mentions

  • Chris Aldrich
  • Khürt Williams

Leave a Reply

Your email address will not be published. Required fields are marked *