Closed vkz closed 1 year ago
I believe this has now been addressed sufficiently. We now serve users feed as well as the latest hoots from their feed after each message. Feed is available at /feed
e.g. mine is at https://vlad.git.ht/feed
Also here's how it looks after each hosted hoot, so that interested readers may discover more content by the same author. Each feed entry will use the first image in respective gist, title and description to create said entry. Entry missing an image will simply show git.ht logo to avoid sore eye.
Similarly, we show latest hoots by the user if you navigate to the root of their subdomain (for visitors not when you're logged in) which should make discovery easier. We also add link to their RSS to the <head>
to ensure RSS viewers can discover the feed when given the user's subdomain without any path. Again, here's mine:
These features have now been deployed and you need not do anything to get them. Maybe just add cute image to every hoot. But, hey, that's up to you. Enjoy.
Just sharing the
/latest
hoot is obviously extremely limiting. MVP ofgit.ht
assumed that the author would publish a hoot, then navigate to the/latest
e.g. https://vlad.git.ht/latest, which redirects to the hoot's permalink. This is fine for sharing your latest on social media.Naturally, if someone visits a post, enjoys the writing and would like to read more by the same author, we'd want to accommodate them right there and then and not necessarily limit them to RSS at
/feed/rss
and search and filter on Github at/feed
. Latter will query Github search and show them author's hoots on Github.Two additional features may simplify things and improve discovery:
author.git.ht/feed
and possibly author's rootauthor.git.ht
serve a list of latest hoots with pagination if necessary.If we replace
/feed
as per 2 above, readers can still search all author's hoots easily, since we offer the same functionality at/search
.