cbeams / chris.beams.io Goto Github PK

Hi,
I do always recommend people to refer the page https://chris.beams.io/posts/git-commit/ for "How to write a good commit message."

But I feel some important recommendation missing there. That is, if any of the rules conflicts with the project's rule, the project's rule should be taken into action. This may be added as rule 0 (or 8).

Say for example the guix commit messages always end up with a period: http://git.savannah.gnu.org/cgit/guix.git/log/

Thanks for a good article

Hi Chris,
I would like to re-use some of your commit-message article in a corporate standard I'm helping a customer with. Please could you confirm if you are happy with this? I wasn't able to find a licence at https://chris.beams.io or in the git repo
br
Paul

For feeds at:

• /
• /writing
• /writing/essays
• /talks
• [ ](and actually create the feeds above if the do not yet exist)

Name feeds /feed.xml or /atom.xml? The latter leaves open /rss.xml or another format.

Do so from a single /subscribe page?

Or: a /feeds page, which simply lists out the different feed urls. actual atom xml files are still within their respective sections of the site, e.g. /writing/feed.xml, simply indexed in one location at /feeds

Use rss image from winterbe's design to link to that page?

Use microformats for a review, etc. and then allow certain services to include them or not.

http://microformats.org/wiki/hReview | http://schema.org/Review

Microformats, RDFa and microdata: three stones, one bird: http://ablognotlimited.com/articles/microformats-vs.-schema

Google webmaster support on Rich Snippets: https://support.google.com/webmasters/answer/99170?hl=en

Today microdata / schema.org formats are mostly used to enhance search results and drive traffic. Seems to me they could be used for so much more. e.g. replacing centralized data silos like yelp with services that aggregate reviews that are already out there. These services become important and useful hubs, but are much more easily replaced than something like rottentomatoes or yelp would be today.

• About me
  • slightly longer bio than front page; stay 1st person
  • link to 3rd person bio? (i.e. version suitable for use in conference bios, etc)

• About this site
  • How it's built:
    • jekyll
    • gh-pages
    • cloudflare serving redirects from cbea.ms
  • how to build and run locally
  • how to test css changes with /test page
  • acknowledgements
    • mdo for poole
    • winterberg for darcula

Should read:

Chris Beams · Writing
Chris Beams · Essays
Chris Beams · Talks

etc.

• remove unused items
• extract any duplicated variables

Experiment with gaug.es for feedback on what people find interesting on the site.

at /writing/tweets

would have to be generated manually on my machine and the html checked in under _site. Rands does something like this at http://randsinrepose.com/tweetnest/. Probably best done as a separate site.

• Can comment threads be locked? (yes)
• Use igvita's loadDisqus() approach to avoid taxing those who don't care about comments at all.

From https://cbeams.disqus.com/admin/settings/universalcode/

      <div id="disqus_thread"></div>
      <script type="text/javascript">
        /* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */
        var disqus_shortname = 'cbeams'; // required: replace example with your forum shortname

        /* * * DON'T EDIT BELOW THIS LINE * * */
        (function() {
            var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
            dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
            (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
        })();
      </script>
      <noscript>Please enable JavaScript to view the <a href="http://disqus.com/?ref_noscript">comments powered by Disqus.</a></noscript>
      <a href="http://disqus.com" class="dsq-brlink">comments powered by <span class="logo-disqus">Disqus</span></a>

Test

• Add a Java example
• Add a .properties example
• Add an XML example
• Replace lorem ipsum text with better explanations where useful

• list all talks (manual entries for now)
• mention / link to lanyrd page
• provide a feed at /talks/feed.xml

The reasons why, by default I do not want to, and what I learned in the process of research.

It's this sort of thing: "Trust me". It's a believable story, and for what it's worth, I think he means it. Unfortunately, in practice these sort of earnest good intentions aren't worth much at all...

http://blog.whatsapp.com/529/Setting-the-record-straight
http://www.reuters.com/article/2013/01/28/us-whatsapp-privacy-idUSBRE90R0T520130128
http://www.forbes.com/sites/andygreenberg/2014/02/21/whatsapp-comes-under-new-scrutiny-for-privacy-policy-encryption-gaffs/
http://blogs.wsj.com/personal-technology/2014/03/17/whatsapp-adds-privacy-settings-says-facebook-wont-change-its-values/
https://en.wikipedia.org/wiki/WhatsApp#Privacy

The cynical, yet undoubtedly accurate response is that FB, like all large corporations who want to get something done, doesn't care about 'harsh fines'. They become regarded as a cost of doing business.

Even if he means it, and even if they don't collect today, it doesn't matter. How are we to know when that changes? I doubt there'll be such a prominent blog post when things get violated internally. I'm sure it'll all be very justified, rationalized by then.

Why we must move from "trust us" to "trustless".

From "don't be evil" to "can't be evil".

What do we do for now? Well, I won't use whatsapp. But there are some perhaps promising alternatives on the horizon:

http://kontalk.org/ looks like a step in the right direction. Looks like a federated model. Open source. Android only at the moment.

... when is federation vs. complete decentralization OK?

Goal: capture all of my writing in one feed at chris.beams.io, without actually cross-posting content if it's been written elsewhere (e.g. on some other blog).

Create an entry that has nothing more than a meta-refresh to the canonical content. This would allow for subscribing to one feed, being notified of everything, but jumping over to the canonical source when appropriate.

Note: I could actually copy the content into that same post as a failsafe for the canonical source going away. In such a case, I would just strip the meta-refresh (i.e. change the layout from "external" post to "regular" post, and the content would simply show up. This might be good to do anyway, just so I have a single place I can git grep for my own content, etc.

Need to see how this would behave in a feed reader.

• feedbin
• feedpress
• reeder 2
• opml support not dead (but not perfect either)

why we need rss. witness twitter removing rss/atom support (not often used).

https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=cbeams

<errors>
  <error code="64">
    The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.
  </error>
</errors>

https://dev.twitter.com/docs/api/1.1/overview

rss renaissance?

Distinguish 'essay' posts with a tag

• index them at /writing/essays
• serve them flat, however, directly in the /writing/{title} namespace

e.g. for a post at chris.beams.io/writing/some-post, offer a share-friendly shortlink in the form cbea.ms/some-post

And use BFG to prune them from the repo entirely. http://rtyley.github.io/bfg-repo-cleaner/

With links to

• /about (#8)
• /reading
• /places
• anything else that comes up...

i.e. how I became a high-end audio skeptic. "The room is the speaker", etc.

Jekyll has poor support for indenting markup properly. Instead, flatten all indentation and wrap included sections in comments.

http://stackoverflow.com/questions/13646945/indenting-generated-markup-in-jekyll-ruby

See http://gradle.1045684.n5.nabble.com/JDiff-td5709873.html
See https://github.com/cbeams/bitledger/issues/2
See http://docs.guava-libraries.googlecode.com/git-history/v12.0/jdiff/changes.html

https://twitter.com/cbeams/status/476155026285797376
https://twitter.com/aalmiray/status/477114982166175744

Particularly for Twitter card metadata. See https://github.com/jekyll/jekyll-seo-tag.

... if possible at all using gh-pages

See http://davidensinger.com/2013/03/generating-a-sitemap-in-jekyll-without-a-plugin/

Following on to #10, consider introducing a comment policy (on the /about page?)

What's the point?

• to make sure that comments add value
• not every post is a candidate for comments, i.e. some posts have comments enabled, some don't
• for posts that do have comments enabled, all comments are moderated before being posted
• be substantive.
• be civil. criticism is fine. indeed, that's my primary reason for putting comments up in the first place: to find out where I'm wrong or haven't thought through something completely, or am not aware of something!
• because everything is moderated, anonymous commenting is fine, too. but I'm not going to approve anything that's not substantive and civil.
• in the event that anonymous posting gets spammy, I'll change the policy above
• consider any comments you leave here as transient artifacts. They're stored by Disqus, and who knows how long they'll be around. Furthermore, I might decide to take down a post, or eliminate comments for any reason at any time. If you think what you're writing here is important, you should probably capture it elsewhere too.
  • Mention that I hope the day comes that we have a better solution for comments, i.e. ones that you (the commenter) truly own and can voluntarily display on my site, and that I (the blog author) can voluntarily include or not; a solution where middlemen like disqus are taken out of the picture. But we're not there yet, and in the meantime, having an imperfect option for user feedback is better than none at all.

• use gh-pages as default branch

e.g. pagination-related.