littlelogs

Keep a social journal of your work progress as you make and learn things.

Littlelogs

Littlelogs

littlelogs
How meta! Development progress on littlelogs is logged by me on littlelogs. https://littlelogs.co

June 2017

josh

FYI I’ve turned off nightly emails for anyone still with that option turned on. Still debating what to do about #littlelogs overall, we could leave it going if people really wanted to keep using it — it’s not a hassle to host it or anything — it just seems pretty pointless if it’s only 2 or 3 people other than us.

May 2017

josh

Hey littlelogs. Sorry we haven’t been around lately. @belle and I have been debating shutting #littlelogs down, actually, because it was only ever a side project and it’s clear that it’s not of use to many people. We sort of half-heartedly meant for our logs to be useful to our users in seeing what we’re working on, but in practice I’m not sure many of them ever look, which is fair enough. We’re going to try adding the ability to write progress logs to our public roadmap thing https://changemap.co, where users will be more likely to see them, which means there’s little need to keep this around. Nothing certain yet, of course, but that’s why we’ve not been diligently logging — doesn’t feel like much point any more.

You’re all still lovely though. Don’t take it personally.

March 2017

josh

Regular reminder that you can invite people to #littlelogs from your account page, and if you’d like to see a bigger, more diverse community on here, you should do that! There’s less point to logging your progress if you feel like nobody cares, so why not invite someone with similar interests who can like your stuff and post interesting stuff of their own?

Okay great, good job everyone 👍

October 2016

josh

I should’ve worked on #exist today, but I got some more done on #changemap instead. More productive procrastination.

Tonight with some help from Linode I moved the #hellocode server (which has all the small things, like the hellocode.co domain, #littlelogs etc) from its legacy, memory-constrained Tokyo server to a shiny new one in Singapore with 4x the RAM (for the same price). Hopefully won’t have any more issues with out-of-memory errors now.

February 2016

josh

Trying out some of our #littlelogs experiments tonight after a bit of a hiatus. There’s a new tab called Following that replaces the old Home tab, which is now composed solely of your own logs. Littlelogs is primarily about logging your own progress, so the place where you log should be the place where you can actually see your own logs.

Also, there are some headers denoting months in some lists now, making it a bit easier to mark the flow of time as you scroll. And finally, projects and their related tags now get a bit more precedence compared to tags denoting tasks and technologies. It’s kind of awkward that most of the top projects on the trending list are ones I’m working on, but you can fix this!

  1. Create a project description for your tags by clicking on the tag then “add a description”
  2. Use the tag when you log about the project!

Let me know your thoughts. I’m open to feedback, new ideas, and threats of violence if you hate it (I guess).

josh

Had a big chat with @belle about #exist, #littlelogs, and #larder plans for the year.

We have some good ideas for enhancing littlelogs, and making a stronger story out of the progress you make on a project. It might also help distinguish between posting everyday progress, milestones, asking questions, and off-topic stuff.

Larder-wise, Belle is going to put some effort into marketing short-term and later switch her time to mostly building the iOS app. The plan is that in 12 months it’ll bring in another $3k a month (at least!), doubling #hellocode income and meaning Belle can ease off on her client work.

As for Exist… we’re going to focus on adding the “event streams” stuff for custom/real-time tracking, and then stop and plan again. Maybe a pivot?

josh

Tonight I made a tiny new addition to #littlelogs. Now you can create project details and relate them to a tag, so people browsing the tag from your profile or for all logs can see further details. Anyone can add details to any tag, so it’s basically an honour system until someone abuses it — but I’d encourage you to only add more detail to tags relating to your own projects, not generic tags. I hope you folks find this useful for providing more context on your work, as a way to link to your projects without feeling spammy by casually dropping links into your logs, and as a reminder to tag your logs each time they relate to a project ;)

As an example you can see my tag description for #exist.

January 2016

December 2015

josh

Spent some frustrating hours trying to fix an html parsing issue in #littlelogs for #android — paragraph tags in list items break the parsing, so the app just crashes repeatedly right now. Found the issue but cannot get my head around the code for parsing text spans, so I’m giving up for today. Onward to more fun things.

josh

And in #littlelogs, I quietly deployed a version of the NVD3 stream graph I was working on yesterday. It’s live, but hidden unless you know the link: basically littlelogs.co/:username/stats/ for any user. Here’s my stats page. I’m not sold on it in this form, but I thought I’d share so you can all enjoy this first iteration. See, this is why you should always tag logs with their relevant project! 😉

josh

Tonight I attempted to create one of these #D3 graphs for some #littlelogs stats based on tag frequency per week. I got it working on my dev server, but with silly testing data, it looks pretty bad — lots of tags, mostly only showing up once. NVD3’s tooltip legend also shows all values, even if they’re zero, so it gets very tall. I’ll have to see if I should recreate it all in plain D3, or if I’m able to customise NVD3 to that level. Anyway, more fiddling required, so it may not be ready as a littlelogs christmas present as was my vague plan.

josh

Merry Christmas 🎄 (if that’s your thing) and a happy New Year 🎆 to all of our #littlelogs friends! Thanks for sharing your progress with us and being a part of ours as we turned littlelogs into an ever-so-slightly larger community of people doing cool things :) @belle and I will probably be around right through until the new year, but to everyone logging off, have a good break and don’t forget to come back and log some progress in 2016 😊

josh

Finished the full preview/post flow in #littlelogs for #android tonight. You now get a nice modal dialog with a log preview, and you can edit or post. It looks pretty good! Almost ready to send beta testers a new build. (And if anyone else wants to try it, let me know.)

josh

And tonight in #littlelogs #android I worked out how to parse images out of log content (with regexes — I know, I know) and add them into the log layout as ImageViews instead. Then I pushed an update to beta testers so they can see images too.

josh

Just submitted #littlelogs for #android to the Play Store’s beta testing channel, woo! 😄 I want to stress that it’s still very early, but for browsing littlelogs on your phone, I think you’ll find it good enough. Plus I’m working on it all the time to bring it to feature parity.

So, who’s keen to test it? Comment here and I’ll email you an opt-in link! Android 5.0+ required.

josh

Added a preview endpoint to the #littlelogs #api, so clients can preview the parsed HTML of a log before posting it. Handy for emulating the web’s preview/post flow. Also updated the #docs to mention this endpoint, and clarified the params needed to post and preview a log, and post a comment. They’re still pretty sparse though 😐

November 2015

josh

Also made some more good progress on #littlelogs #android, going deep into HTML parsing as I style and replace code spans, list items, and links. I’m particularly proud of how I’m handling links — because you can’t always see the URL in markdown, I’m popping up a snackbar containing the URL, with the action being an “Open” button to follow the link. If you don’t click it after a few seconds, it dismisses itself.

There’s still some more HTML to support, like code blocks, blockquotes, and images. But I’m getting closer to showing the full rich-text of each log.

josh

This afternoon I sorted out caching for global #mood averages in #exist, which was until now being computed whenever the mood stats page was loaded. Much reduced page time, woo.

Tonight I added the list of likers to the #littlelogs #android log view, and also started parsing log HTML, turning tag links into static spans with the correct hash colour, removing images (they’ll need to be rendered separately in a later pass), and linkifying links in logs. I’m using Android’s Html.fromHtml(someString) to turn the original log content into a set of text spans I can manipulate (with properties like style and colour), which might be shortsighted but is working well for now.

josh

Tonight I added comments to the log view in #littlelogs #android, so aside from seeing the list of people who liked a log, and some content formatting for links and images, it’s pretty much complete as a very basic read-only app. Woo! Maybe I’ll open it up to some beta testers soon, if anyone is interested — partly to get feedback, but partly just so you can start having an app experience. Web is good, but native feels nice :)

josh

Today I sent some more #exist #mood feedback emails, though I didn’t get around to following up on the people who previously replied. Maybe tomorrow.

Then tonight I made some more progress on #littlelogs #android showing like and comment counts, and created a new activity to show the expanded single-log-with-comments view. It shows the log, but not yet the comments. Also maybe tomorrow. Regardless, I feel like I’m making pretty quick progress :)

josh

Today I did what #exist #support needed to be done, but to be honest, not a lot else. I have a lot of emails about the #mood stuff waiting to be replied to, with lots of conflicting opinions, so I’m kind of just putting it all off because I’m not sure what to do next…

So tonight to make up for that I worked on #littlelogs #android and made some pretty good progress. I can see all timelines with avatars and timestamps! Next up I need to make the single log view with comments, and then I’ll probably work on write actions like logging, liking, and commenting.

screenshot

josh

Today I worked a little more on #littlelogs for #android, mostly setting up things like custom colours and adding the font we use on the site. It probably seems backwards but I’ll happily spend a lot of time tweaking UI elements before I get more than basic functionality working, as the app looking “right” makes me more comfortable to treat it as a real thing and keep working on it. I don’t really do this on the web though… I wonder why mobile apps are different.

Also this evening I took @belle through making her #ios code more generic. We had lots of places with multiple methods whose only difference was a string or a differing constant, so we worked on changing this to one method that could take these dynamic values as arguments, saving lots of duplicated code.

josh

Today while @belle was playing with coding an iOS app for #littlelogs we happened to find our secure connection was only being served over TLS 1.0 (now regarded as insecure by iOS and Chrome, among others). Following the trail through many red herrings I eventually found that my #nginx + #openssl + #ubuntu version combo meant nginx wasn’t able to serve anything newer! Fortunately upgrading it fixed the issue.

josh

Because it’s been a while since the last one, let’s share some #littlelogs stats!

Last 30 days:

  • 75 users active
  • 47 users posted at least one log
  • 390 logs posted
  • 416 comments posted
  • 545 likes added
  • 1251 notifications created

Overall:

  • 262 registered users
  • 2524 logs
  • 2518 comments
  • 2502 likes
  • 6329 notifications
  • 3 OAuth2 clients created

It’s crazy how close those log, comment, and like totals are! I wouldn’t have predicted that.

Anyone else who’d like to share some stats from their own projects, please go ahead — I think we all find this kind of transparency very interesting.

As you can see, we’re still a small, ragtag team of creative people just logging one day at a time. If you’d like to see more activity here, invite your friends! Spread the word.

josh

I deployed my #littlelogs #api changes! You can see some new pages for managing your apps (both as a user and a dev) on your account page, and read the (very sparse) developer docs I've just added. I'll flesh those out over the coming week.

The most exciting part of this is that the littlelogs API is open for business! Anyone can create an OAuth2 API client application and make a native iOS app, or a Slack bot, or a terminal client, or do some cool visualisation with tags or something, I don't know. Go forth and create!

October 2015

josh

Set up the #ssl cert for #littlelogs today and tried really hard to get the #api management stuff ready... But didn't quite make it today. Still have to finish the "connected apps" page where a user can revoke access, and write some really basic docs. Maybe tomorrow though!

josh

Purchased an SSL cert for #littlelogs, finished off all the #api endpoints, and started setting up the docs. Using slate again because it worked nicely for Exist. Now there are a lot of docs to write! This step might take a while.

josh

This afternoon I've been working on the #littlelogs #api. I've got the write endpoints for logs, comments, and likes completed. Just need to do deleting. Next will be some docs and then the api branch will be ready for a merge and deploy! Hopefully sometime in the next week.

josh

Switched over the signup process to require manual approval from moi, the approval-master. Made it easy to tap "approve" in the signup request email I get, which will send the invite email to the new user, so it shouldn't be too much of a hassle. Looks like I'll still have to be vigilant though — just took down another spammer 😑 #littlelogs

Older