@jarrod yeah, that’s a good idea actually. It’s more of an app behaviour, I think, but I can see users wanting to just make the blog follow the readers’ preference.
Replies
@simonbc Looks very different from yours @dave but your blogroll was actually the main inspiration when I designed one for Tinypost. I love that it’s dynamic, that it updates based on what people are writing and includes the latest post. Is it a feed reader or a blogroll? :)
@tylerknowsnothing Good question. Jottit is a faithful revival of the 2007 tool I built with Aaron Swartz – intentionally minimal, markdown, no sign-up required, pages you can optionally collect on a profile. Tinypost is targeted towards more traditional blogging: WYSIWYG editor, images, email subscriptions, blogroll, social links. Think of Jottit as “publish a page in seconds” and Tinypost as “run a simple blog you actually own.” They share DNA but serve different needs.
@jarrod Thanks! Interesting idea. I think I want to keep the background (and the whole app, actually) clean for now, but I could see something like that working as an optional theme down the road.
@jarrod Yeah, I definitely hear you. Subdomains signal “this is a site”, which is why I switched to @usernames, but they also feel more personal and less “platform”. I might bring back subdomains as an option down the road for users who want to make a site out of their profile page.
@dave Me too :)
A network of writing tools… what do you have in mind? Jottit and Tinypost already support RSS. Tinypost supports OPML and blogrolls.
@dave Thanks for sharing this, Dave! Means a lot coming from you.
@jb.heydingus.net Thanks for trying Jottit and for the kind words! Love that you kicked the tires and made a page :) If you have any feedback, I’d love to hear it.
@ayjay very cool to see your jottit site from back then :)
@ayjay That means a lot! Would love to know what you think of the rebuild.
@tylerknowsnothing Thank you for sharing this! Seeing your post made me realise you were using Jottit in a way I hadn’t imagined, and it completely changed how I think about it. As a result I’ve spent the weekend redesigning Jottit.
@tylerknowsnothing Good news on the edit issue: I think I found and fixed the bug. Thank you so much for reporting this!
Dark mode is on the list :)
@tylerknowsnothing Thanks so much! Really glad you like the editor. If I understand you correctly, you clicked “Sign in” before creating a page? The login flow is a bit unusual: you write something, then claim it. So there’s nothing to sign into until you’ve made a page. I need to make that clearer.
@dave Thanks Dave. Native comments are next on my list, working on it now. And fair point on showing not telling, I’ll start including links and screenshots. from now on when I post about new features. I appreciate it!
@manton Interesting. I think there could be a lot of upside to integrating reading and writing on the web like this. Seems like the two should go together. Excited to see how you build it :)
@manton I’m dreaming of a minimalist feed reader, river of news, no unread counts, runs in the browser. Pretty much what Terry is building, except that it doesn’t run in the browser. How will you reader work? Is tied to micro.blog or is it a separate app?
@simonbc Today I’m adding RSS.
@simonbc So I burned it down. New Jottit looks the same but makes you a blog. Flask, Postgres, Jinja, vanilla CSS/JS. No build step. Nothing fancy. Reminds me of the original Jottit I built with Aaron in 2007.
@rom thanks for reporting this! sent you a reply through email, hope it helps :)
@rom Hey! There was a DNS configuration issue that may have caused some email providers to reject our claim emails. I haven’t experienced the issue myself, so I’d appreciate it if you could try claiming again and let me know if it works now. Thanks for the heads up!
@manton thanks
@manton Just started posting here and wanted to say hi. I’m rebuilding Jottit, a simple publishing tool I originally made with Aaron Swartz back in 2007. Relaunched as open source at jottit.pub. Love what you’ve built with micro.blog. Feels like we’re working on adjacent corners of the same problem.