1. I originally registered https://papyrus.dev, with the original idea being a newsletter aimed at developers. I pivoted to be more broader, and with that, changed the TLD to .so. I haven't gotten around to setting up mail on the new TLD yet, so still using the old one for everything.
2. I'm not sure yet. One of the selling points is no third-party trackers, so I'm not sure how readers will feel if some of their blogs started tracking them.
3. Thanks for the feedback, and I appreciate the mockup! Agreed that section can be clearer - I've added this to the backlog.
If you ever want to use a ccTLD, I recommend starting by looking at the registration restrictions in the infobox in the ccTLD’s Wikipedia article, e.g. https://en.wikipedia.org/wiki/.so says “Limited to institutions and organizations in Somalia, residents of Somalia, others who have a legitimate, clear and provable connection to Somalia”. Also consider whether you trust the country in question to operate its registry well, not to have hostile takeovers that mess up the entire thing, &c.
Generally speaking, I recommend avoiding using ccTLDs in this way. Even new gTLDs are mostly safer. One possibility there is papyrus.pub (“pub” being nominally short for public houses, the eating places and such, but also definitely being used for publishing).
I have seen about three other .so domains, notion.so being by far the best-known; and Notion has definitely had trouble at least once either with their registration or with the operation of the registry.
1. I noticed that the signup email comes from papyrus.dev instead of papyrus.so. Any reason in particular for using 2 domains for the service?
2. Do you plan to support adding third-party tracking JS for services like Google Analytics, Umami etc?
3. I also shared some feedback elsewhere in the thread, not sure if you saw it: https://hackertimes.com/item?id=29083365