monkey_slap

is there a space inside Campfire for more disposable type conversations?

Yes absolutely. We have messages (DMs and group) as well as calls. We have a ton of "throwaway" conversations in messages.

Thank you so much, yes we need to work on all of this

I do think we deliver $16/user/mo of value fwiw: unrestricted posting, DMing, video calls with recording + transcripts + LLM summaries, API, and tons more. But we're not doing a good enough job:

1. Giving people an on-ramp to try posting on Campsite without committing to $20/u/mo. What's your take if we had a $10/u/mo "starter" tier? 2. Telling the story on how working the "Campsite way" is so much better than Slack, and the craft in the product justifies the price (in my strong, very biased opinion).

Love being a traitor. Just can’t look at $META and do the math.

I worked at Facebook for 5 years and agree. Though the culture was a big driver too. It’s not like switching to Workplace will magically transform company culture.

Really appreciate the feedback, thank you

It's much better, but most of our users are on iPhones. The one (yes, one) Android PWA user is really happy.

Probably the best part about PWAs on Android is that you install it more like an actual app. iOS still makes you "Add to Home Screen" which is very unintuitive.

Check out https://github.com/cli/cli/blob/trunk/docs/gh-vs-hub.md

FWIW gh is built by some of the same people that built & maintain hub.

IncludeHealth | Full-stack, Senior | Full-time | Columbus, OH | ONSITE or REMOTE (<3h from HQ)

IncludeHealth's mission is to lower the barriers in keeping people healthy & active through technology. Started through the lens of accessibility, our founder originally saw a man in a wheelchair struggling while exercising and he believed that through technology, design, and collaboration there had to be a better way. That observation, and subsequent decade of exploration, spawned the creation of IncludeHealth. Teaming up with healthcare experts, developers, and designers IncludeHealth has created an internally awarded musculoskeletal (MSK) platform designed for providers to deliver care onsite and remotely through a collection of connected equipment, sensors, and body-tracking technologies.

We are seeking a midwest-based React/Next.JS Team Lead who is passionate about creating amazing web experiences to help IncludeHealth expand our platform. Our platform supports physical therapists and patients in recovery using a variety of IoT sensors and AR based machine learning techniques. We have current applications in customer’s hands and are looking to replace the web and iOS clients to remove technical debt and take full advantage of the devices we are distributing.

The web application will be the front-line in clinic management platform that allows our clinicians to integrate with their patients and now IncludeForm, our AR machineless human pose technology that will be deployed into people’s homes.

Tech stack: React, Next.js, ML5.js, tensorflow.js (PoseNet)

Contact: jobs@includehealth.com

Learn more about IncludeHealth: https://includehealth.com/

Feel free to post your feedback here or my email (bio). Sorry if we didn't get back to you on your feedback.

This is probably links within the readme (like #installation in a table of contents). Known problem that we didn't get to fixing, but we're going to fix this soon. Thanks for the report.

The app supports Enterprise Cloud today, and Enterprise Server is on the roadmap!

This is on our roadmap! Will be out soon.

Thanks for this, and sorry you got bumped from the beta. We're still actively shipping to our beta and if you'd like to rejoin please just email me (bio).

Really good feedback, I feel you on the text wrapping. We're trying to find creative ways to make this work better.

The main activity feed from / is nowhere to be seen, even though this is something I use daily on my laptops

Can you tell me more about what you use this feed for? You're talking about the one on the github.com home page?

Again thanks for the feedback, we have a lot of work to do still! Forwarding this comment to the team.

Thanks for this feedback, giving people more options for push notifications is on our roadmap! Including letting you set schedules for when you can receive them.

Both iOS (Swift) and Android (Kotlin) are fully native

gh is open source https://github.com/cli/cli/

I intend the app to be another option for how to get things done. I've been using it the last few months to manage building the app itself, and being a remote worker, it's freed me up to be a lot more mobile in where/how I do that work.

One of the most important next things we can build are more controls in when/how you can be reached (e.g. setting working hours).

Nope, just vanilla UIKit for the iOS app.

This has been top-of-mind since we started on the app. We're heavy users of the app ourselves and are prioritized WLB features already. The last thing I want to see is our app used an excuse for people to work more. Instead, my hope is we can help people work more efficiently on their own terms.

The iOS app is 100% Swift and the Android app is 100% Kotlin.

You can leave a comment-only review on the iOS beta that we released today, but we are committed to adding line-by-line commenting for Pull Request reviews before we launch broadly. I originally didn't think that it would work until our engineers built a prototype and changed my mind.

And since review comments are saved to the server as pending, you can even start a review on your phone, then finish on your computer (and vice versa).

That's me! Lots of lessons influenced our decisions on GitHub for mobile.

Working Copy is an amazing app! The GitHub iOS app works really well with Working Copy.

Working on a GitHub iOS app to make managing GitHub projects easier. Fun part is now that it's shipped I'm using it to manage itself.

https://github.com/rnystrom/Freetime

Turning this into more of a social experiment now, seeing where he community wants to take this. Publishing download reports and stuff.

Even made a landing page.

http://freetime-app.com/

Hey! I worked on this. If you have any questions let me know. Pumped that we could share this, eliminates a ton of common collection view problems.

That's the joke.

Isn't a "3D Touch" a physically more demanding action than just a traditional tap? Why should the former be associated with a "quick peek" and the latter with a committed selection, rather than vice versa?

Physically, it is. You use more energy to activate it. But after using it for a while, the real benefit comes from browsing a list of stuff by only peeking and then backing out. You can consume a ton of thumbnails much, much faster since you don't have to reach the back button or swipe to go back. Instead, you just let go of the screen and it returns to where you were.

I actually really like your analogy of single-click and double-click. 3D touch sort of fills the single-click void.

Avoiding the trap is a real issue. 3D Touch should absolutely not be applied to every single element in every single interface. Challenge is how do you teach someone what can use a 3D Touch and what can't? Not sure we have the answer yet.

Full disclosure, I work on this at Instagram and wrote the post.

I'm the engineer at Instagram who wrote and worked on this. Available to answer any questions you might have!