I'm researching how to handle the listen-of property, so I can respond to Chris and David. Especially since they mentioned my Android app and both mentioned they used it.
Mystery solved: the reason not all posts were indexed after being posted was because of an extra job worker running a previous version of the code. Quite a few times it was quicker than the real workers and it seemed it didn't work.
Around the 1h mark, Chris and David start talking about my Android app.
I should add a <pre> tag to the code snippets.

Changes on March 18

Data storage

I changed the way that the post are saved in the data backend. The backend is Redis and the ids of the posts were added to channel lists. That works great for a while. The list are sequential, which keeps the posts in order on the website. I changed to type of the channels to be sets. The advantage of this is that I can merge the sets of ids. The problem however is that sets don't have a sequential order. This can be solved with the SORT command. It sorts ids by a differents keys and also allows to limit the result. Both limits and sorting works this way.

Checkins

Next I made checkins work. I now use Own your swarm to send micropub posts to this blog. Now I can use the Swarm app to check-in to locations and have them send automatically to this blog. Then I improved the design of check-in posts. And added Mapbox to show the locations on the map.

Bookmarks should be added to the bookmarks channel automatically. The old posts need to be added to the right channels.
This is a note that was added to the notes channel
Having two workers running "fixes" the problem. Probably two pieces of code are writing the same information. And overwriting it with the information from the first.

Load more