Back
Philip Thomas

Philip Thomas

@philipithomas

Making products like Postcard and Booklet at Contraption Co.
Load previous page…

@marc I want one good email summary per day of what's being discussed. That way, info gets pushed to me - but in a calm way, where I don't have to remember to check all the time. I miss web forums, which are close to this. But, they are all so clunky.

The best asynchronous, modern forum I've used is YC bookface. I've been working on a project called #booklet, which is inspired by YC Bookface. If you're interested in testing it out - I'd love to keep developing it for a community like WIP. It's made to be high-polish and realtime, but able to be used over just email with one good summary per day.

The closest I've seen to what I want today is groups.io/ - but it's still pretty clunky.

Do you subscribe to the current daily WIP email?

It only shows todo activity of the people you follow, but there's a lot more we can like you suggest. Include new discussions, recently added projects, etc.

What would you like to see in such a daily email?

I've been building out our own forum software which we're having this conversation in right now. Are you saying you want more of an email interface for this, including the ability to reply to comments, etc?

No, I do the weekly email - I'll switch to daily.

The main point of a forum for me is non-realtime discussions. Replying via email is secondary for me.

I think paying for access to the community makes sense. I just honestly don't like Telegram - it's a blocker to me engaging more with the community. I prefer something more asynchronous.

Yeah people seem quite divided over Telegram. Some people like myself use it all the time with friends etc so it makes sense to also have WIP accessible there.

But if you don't use Telegram already, I can how it's not ideal having to use that for WIP.

Would you mind elaborating on a more asynchronous solution you'd prefer? Is it something where the website could play a role?

@marc I want one good email summary per day of what's being discussed. That way, info gets pushed to me - but in a calm way, where I don't have to remember to check all the time. I miss web forums, which are close to this. But, they are all so clunky.

The best asynchronous, modern forum I've used is YC bookface. I've been working on a project called #booklet, which is inspired by YC Bookface. If you're interested in testing it out - I'd love to keep developing it for a community like WIP. It's made to be high-polish and realtime, but able to be used over just email with one good summary per day.

The closest I've seen to what I want today is groups.io/ - but it's still pretty clunky.

Do you subscribe to the current daily WIP email?

It only shows todo activity of the people you follow, but there's a lot more we can like you suggest. Include new discussions, recently added projects, etc.

What would you like to see in such a daily email?

I've been building out our own forum software which we're having this conversation in right now. Are you saying you want more of an email interface for this, including the ability to reply to comments, etc?

No, I do the weekly email - I'll switch to daily.

The main point of a forum for me is non-realtime discussions. Replying via email is secondary for me.

Thanks @marc - I meant the inverse. Do you have any good resources on how to learn + set up a graphql server without knowing Node?

I'm building something, should be live soon. Building a bot

@marc Any advice for learning GraphQLl in the Rails world? All the resources seem to revolve around Node, and I have trouble going through those tutorials.

You can use this code as a starting point: gist.github.com/marckohlbrugg…

I don't have any great resources other than that, but I think if you just tweak the query it should go a long way.

You can also experiment with queries on wip.co/graphiql

Thanks @marc - I meant the inverse. Do you have any good resources on how to learn + set up a graphql server without knowing Node?

I'm building something, should be live soon. Building a bot

I used Basecamp's open-source policies: github.com/basecamp/policies

I like this cause I can read it and understand it and make changes... Doesn't need to be written in lawyerese

Thanks for the feedback! @marc and @gvrizzo - could I poll you on these potential taglines to put in the hero of the homepage?

  1. “Personal homepage + newsletter, made easy”

  2. “Start a personal newsletter on your own site”

  3. “Start a personal newsletter on your own domain”

  4. “Create your personal homepage”

Which do you prefer? (1, 2, 3, or 4)

I commit code every single day and build a streak. It doesn't matter how big the commit is - but it needs to happen every day. I like this approach because I'm constantly thinking subconsciously about what I'm going to do next. So, when I sit down to do the work - it's really easy to jump straight into building because my conscious memory already has context.