We're a group of makers shipping together. We help each other stay accountable and reach our goals.
Apply for access
Florian Gmeiner
@floriang
Maybe I'm not sure what your database schema is set up as but perhaps dividing this in two would be a good idea.
Make the invite list backlog a separate dedicated page (as Omar McPizza suggested) in your leaderboard style. This makes even the applicants list work in the open.
Perhaps you can create a new class of comment for non-members that is delete-able by members (hopefully self moderating for non-community fitting comments). These comments could also maybe be limited to a sub-section of the WIP.co site. (e.g. only in in the "Questions" section). This could lead to more "ask the crowd" type value.
@floriang @McPizza These are the type of massive code changes I'd like to avoid 😅
Anything requiring separating the website into two parts, or adding a separate user type with different privileges would complicated a lot of the code.
I don't mind adding some complexity in a specific area, but if it's something so fundamental, it tends to slow down all product development going forward.
I prefer a solution that's more isolated.
Maybe one of the application questions could be "pick a question from the forum and answer it in a helpful way". And we'd save that answer not as a regular answer, but simply as part of the application. We'd then also link it to the original question and notify the author of that and get their vote on whether the answer was helpful or not.
Something like this would still allow applicants to demonstrate their value-add, without requiring structural changes throughout the code.
I'm curious if we can come up with more ideas like this or fine-tune the one I mentioned?
As someone who was looking for an invite until very recently, I would be interesting if there were a way for non-members to contribute and based on interaction be pushed up on the waiting list.
Kind of a "give first" mentality to enrich the community and the reward would be a potentially quicker invite processing or application review.
I like this idea a lot. I'm just not sure how to implement it without massive code changes.
Any suggestions?
Could we have a "guest" user type that only allows commenting/reacting?
Could have separate (stripped down) interface on separate domain that posts comments to primary
Maybe I'm not sure what your database schema is set up as but perhaps dividing this in two would be a good idea.
Make the invite list backlog a separate dedicated page (as Omar McPizza suggested) in your leaderboard style. This makes even the applicants list work in the open.
Perhaps you can create a new class of comment for non-members that is delete-able by members (hopefully self moderating for non-community fitting comments). These comments could also maybe be limited to a sub-section of the WIP.co site. (e.g. only in in the "Questions" section). This could lead to more "ask the crowd" type value.
@floriang @McPizza These are the type of massive code changes I'd like to avoid 😅
Anything requiring separating the website into two parts, or adding a separate user type with different privileges would complicated a lot of the code.
I don't mind adding some complexity in a specific area, but if it's something so fundamental, it tends to slow down all product development going forward.
I prefer a solution that's more isolated.
Maybe one of the application questions could be "pick a question from the forum and answer it in a helpful way". And we'd save that answer not as a regular answer, but simply as part of the application. We'd then also link it to the original question and notify the author of that and get their vote on whether the answer was helpful or not.
Something like this would still allow applicants to demonstrate their value-add, without requiring structural changes throughout the code.
I'm curious if we can come up with more ideas like this or fine-tune the one I mentioned?
In the same vein, what if accounts that were opened by invites that go stale (>90 days without activity / login) get "frozen" with the invites returned to the invite provider and the account holder would need to get a new invite.
It does sound tricky though. Do stale accounts get culled?
I use these for listening:
* Bose QC 35 II - for focus when noisy and but only when it cold/ or there's AC
* AirPod 2 - travel and hot environments
I have mixed results with Linux bluetooth drivers. Audio/BT/Linux still not flawless. I keep a pair of ???? Amazon wired in ears with mic just in case audio connection is bad.
Good enough for most things. Once these machines die I might switch to a Mac and use a Shadow server for GPU intensive work.