All new notes will be added to the index again. I don't think the "articles" (or notes with titles in my case) are enough to make the frontpage interesting enough.

Peter Stuifzand replied to a post on quickthoughts.jgregorymcverry.com

I set up drone.io to build the site and redeploy on push. I would like to experiment more with some changes, but this keeps me "honest".
I found that I have so many channels in my IndieReader that it was starting to create stress when I opened it. So I’m testing out viewing only channels with new content. Eventually this will be a filter setting you can quickly switch back and forth between
#

Peter Stuifzand replied to a post on eddiehinkle.com

For me, Twitter is up to 3926 posts now. I guess I should be a bit more specific about what I follow there.

Testing a bit with https://indiewebify.me.

The notifications for webmentions also work pretty well, but I guess it should show the author of the source post instead of myself.

What I don't understand: let's say I write a new issue with Quill and somehow get an issue title and markdown support. When this entry gets posted via Micropub to my website and webmentions are mentioned to https://brid.gy, how can Brid.gy convert the HTML from my entry back to Markdown in Github? Does it do that, or is there some other magic going on.

cc: @aaronpk, @snarfed

What I don't understand: let's say I write a new issue with Quill and somehow get an issue title and markdown support. When this entry gets posted via Micropub to my website and webmentions are mentioned to <https://brid.gy>, how can Brid.gy convert the HTML from my entry back to Markdown in Github? Does it do that, or is there some other magic going on.

cc: [@aaronpk](https://aaronparecki.com), [@snarfed](https://snarfed.org)

Code, commits and view-source are all a kind of documentation.

For example: Markdown support in a certain micropub client, uses the same keybindings to open the responsive design mode in Firefox.

Peter Stuifzand created a new issue for pstuifzand/test

Another test issue with some markdown

Let's test this. Quill expects at least backticks to support markdown.

But Github will need the Markdown and not the HTML version of this. How will this translate?

Load more