- nanopub - Micropub for Static SitesMicropub endpoint for static sites.

Ekster was mentioned at the Social Readers presentation by @aaronpk

I just made a change to Ekster that allows it to receive Micropub requests from Indiepaper. In a way this already worked, but only with source_id and JF2 request bodies. This change allows the auth token to be in the Authorization header and JSON micropub requests.

I just created a Microsub client for the command line. Find it at #indieweb #microsub
Test with Omnibear patch with different syndication code
An example of a service like this is You upload your own OPML and you can subscribe to other peoples feeds and OPML.
There are many parts to the microsub spec. My server implements follow and preview. But Monocle doesn't, and Together does. Perhaps there is a place for external tools that help with following and add feeds to your microsub reader.
Thinking about creating project pages on my this website, where replies will be added as issues and replies to issues will be comments. Similar to how supports Github.

I will like to combine my old and new websites into one page. The old site is statically generated. I have been writing there since 2004. So there is quite a bit of history there. I would need to convert all that to the new backend, so I fill in the gap from 2004 to now.

I have heard of people also convert Facebook and Twitter posts into their new websites. Perhaps this is something that I should also do, especially since Facebook and Twitter, may one day stop working.

In the current situation I have some more posts and Facebook, Twitter and perhaps Github. All of it could be transported here (somehow).

What do I still need:

  • Public/private settings for posts
  • Photo album style pages
  • A page where I can list all the companies that are getting some of my information 😉
Most of my current stuff happens on my own website. Find me there. #indieweb
It seems to be be the tags that get a mention as well.
The bookmark part of the app should get the title of the page it points to and allow to add tags and a short description.

Microsub changes

Yesterday I made an improvement to support paging with ZADD and ZRANGEBYSCORE. This allows me to get range of entries based in the timestamp of the published date (converted to Unix timestamp). The problem is that the unread entries are still available in the list. It's hard to find the first unread entry in the list. That entry is the starting point of the list of entries for the first page of items.

I implemented the solution like this: keep two lists. One with all unread items and one with the read items. In principle an entry moves from one list to the other in a linear fashion, because that's the reading order. So now when there is no after or before argument the server can send the first twenty items of the list. The first and last item contain the next before and after values. Nice thing is that I now get unread count for free with ZCARD.

Social Graph problemPeople are getting sick of registering and re-declaring their friends on every site.

Bookmarks should be added to the bookmarks channel automatically. The old posts need to be added to the right channels.
Yesterday I improved the authorization endpoint. It will work now with more clients. I found that still quite a few clients need the "me" parameter, which I think should not be needed, because there is a "state" parameter.
Next I will need to implement the channels that I added to the authentication screen. This will allow to connect auth tokens with channels. The channels will be special "feeds" so not all items will end up on the homepage.
Now the test: is it possible for me to use the new token endpoint with Quill?
I still need to improve the way Twitter is handled by the micropub server. If I reply to a post on a #indieweb website, I should read the syndications from the entry and try to post a reply on Twitter to that post.
I think there are still quite some bugs in the current code of the #micropub #android #indieweb app. But syndication, replies and categories all work.
Using #docker with nginx-proxy is pretty simple. Add some docker compose files and you have automatic SSL and hosting of docker images, webmail, continuous integration and delivery, and a simple #indieweb feed with microsub.
The grade in which #indieweb works is bound by the number of people not using your software. How much can you communicate with them without using the software they use?
Yesterday I wrote a microsub server in golang. It contains most of the feature that I need to connect with the Together reader app.

Some observations:

- search is pretty strange to implement, it now only supports full urls.
- it does support automatic fetching of feeds
- it doesn't have caching support of items. It always fetches the full page
- no support for smart or automatic feed downloading, no WebSub. It should in the future
- mute and block are not implemented

Load more