🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

When I try to use face.camp on my laptop with my external monitor plugged in, it defaults to my monitor camera. I don't see a way of switching cameras unless I disconnect my monitor.

The devDependency eslint-config-prettier was updated from 6.7.0 to 6.8.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-config-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

• I made one and posted
• made a another and tried to post
• it did not post, but reset the preview window and caption text box

If this is open source:

• link to add an issue in GitHub
• contribution guidelines to README (plus, probably more robust install instructions + license)
• Email address + twitter?

If not open source:

• Email address + twitter?

✏️ Edit
We are going to open source so I vote we ask for feedback via GitHub issue and Twitter. That seems reasonable to me, I don't think we need a form or an email address.

1. Create test auth deployment with new credentials
2. Deploy latest face.camp
3. Resubmit app to slack directory
4. Get app approved
5. Redeploy auth.face.camp with new credentials
6. Redeploy face.camp with auth url set
7. Remove unused oauth urls

Possible flow would be:

1. Switch teams button
2. Slack oauth page
3. Redirect to app
4. App checks if it already has a valid team and if so adds a new auth token instead of replacing it

https://brandfolder.com/slack/logos

If you hold down the Record button too long (after the gif has been captured), it resets the gif when you release the button.

The devDependency @typescript-eslint/parser was updated from 2.19.0 to 2.19.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

on ios if I press and hold the record button, it doesnt record. But it does record for the minimum length (1 second) if I just tap the button

two people experienced this

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

• Use browserlist config to be more selective about supported browsers since getusedmedia is only supported by these browsers
• We could probably even ship some ES6 code and minify it with uglify-webpack v4
• Babel: transform spread to object.assign and dont transform object.assign
• gif worker isnt getting minified
• use route splitting for app.js
• use file loader for image urls

This might or might not be worth doing.

Some steps I see:

• Fix redirect from PWA to auth and back to PWA (might not be possible in iOS)
• iOS icons

• Intro + a logo maybe?
• Clear install instructions with maybe a screenshot
• A credit to Phil
• Contribution guidelines / code of conduct

And get current host name from context. This would allow for deploy previews to be testable as long as the url was added to the list of valid redirect urls

Reference: https://community.netlify.com/t/knowing-the-current-public-hostname-of-a-netlify-function/7160

Expected Behavior

When you select Private Channels before logging in, you should see your private channels in the list to post to.

Current Behavior

Private channels do not show in the list. They do for some people, but not all.

Browser / Environment

Chrome on Mac OS

I was thinking it'd be nice to show how many megabytes are about to be uploaded.

#21 (comment)

We just need a:

• Privacy policy link in the footer ("next to from your friends at &yet")
• /privacy page with this content:

&yet will never to gather, store, or sell information about you, log your messages or gifs, or engage in any other behavior that would compromise your privacy and security in any way. Facecamp is a static web application with no database, so your gifs and messages are uploaded directly to Slack with no data passing through our servers.

Now that #26 is done, I think the non-scrolling / fixed UI from #19 is possible.

• Max height for tall windows
• Min height to display "Use a taller browser" message
• Min height to force some scrolling to keep it usable
• Use flex to naturally space UI groups (nav, image, input/post)

┌─┬─────────────────┬───┬────────┬─┐
│ │    Team Name    │   │        │ │
│ └─────────────────┘   └────────┘ │
│ ┌──────────────────────────────┐ │
│ │                              │ │
│ └──────────────────────────────┘ │
│ ┌──────────────────────────────┐ │
│ │                              │ │
│ │                              │ │
│ │                              │ │
│ │                              │ │
│ │                              │ │
│ │                              │ │
│ │                              │ │
│ │                              │ │
│ │                              │ │
│ │                              │ │
│ ├──────────────────────────────┤ │
│ │                              │ │
│ └──────────────────────────────┘ │
│ ┌──────────────────────────────┐ │
│ │                              │ │
│ └──────────────────────────────┘ │
│ ┌──────────────────────────────┐ │
│ │                              │ │
│ └──────────────────────────────┘ │
└──────────────────────────────────┘

There's currently a semi-scary looking yellow banner at the top saying This app hasn't been reviewed or approved so it'd be good if that went away before posting publicly.

It would be cool to be able to use these gifs in private messages too!

My specific face gets washed out during the compression, so I could be a good test subject for if we have enough colors going on or not :)

The devDependency @typescript-eslint/eslint-plugin was updated from 2.6.1 to 2.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Would love the ability to download and/or copy and paste!

• Update face.camp and www.face.camp DNS records
• Verify DNS
• Delete zeit face.camp deployment
• Test Slack auth inside Netlify functions
• Update auth url to face.camp/.netlify/functions
• Delete auth.face.camp DNS record
• Delete auth.face.camp k8s deployment
• Figure out and document local dev with netlify-lambda serve
• Figure out local https testing #111
• Figure out Slack redirect_uri issue when using localhost and/or ngrok #109
• Test netilfy functions #110

Heard back from Slack that approximately 2MB is the threshold they use for whether to display a preview of an animated gif on iOS.

Many of the ones I've uploaded have been 4-5MB, so if we can reduce the size by half, that seems like it would be pretty impactful.

Definitely, there are some ways to reduce our total size which would have a significant impact:

• Ideally, we should reduce the resolution to half(?) its current size before uploading. I don't believe that Slack even shows the full resolution in previews.
• Reducing the max amount of time recorded would also be fine, I think. I don't think we need the full amount of time we're currently recording to have a meaningful impact gif.

From there, we have some options:

• We could not allow for gifs to be created that are larger than 2MB
• Alternatively, we could inform the user when their image was greater than 2MB and that the preview wouldn't be displayed on mobile

If we end up reducing the height of the image capture area (which might help with file size/compression as well), maybe we could stick the footer from the login page onto the app page?

Any thoughts, @lukekarrys?

Tokens can be invalidated by the user or through other means, so if a request is made and that is the error then the app should probably automatically logout and force the user to reauth

This is blocked by iOS 11.3 not having getUserMedia available in WKWebView (chromium bug report) which is what runs PWAs on iOS.

I researched finding a way to signal to Android devices but not iOS that this app is PWA capable, but couldn't find a way to do that. So it's possible that all this is currently possible on Android, but I don't have a way to test that. So for now, I'm waiting until iOS 11.4 or later to see when WKWebView gets access to getUserMedia

Checklist to make this a functional PWA

• Change manifest.json display to standalone
• Change web-app-capable meta tags to yes (Research required this might not be necessary since those are used for older browsers which probably dont support getUserMedia anyway)
• Use manifest.json scope to signal which URLs are navigable by the app
• Change auth flow to happen inside PWA
  • Test on android
  • Wait for iOS support related Pinafore PWA bug

Is that possible?

Dependent on #104 happening first

iOS zooms in when input controls are focused and have less than 16px font

I have face.camp and auth.face.camp running locally. This is what currently ends up in the address bar after attempting to auth:

http://localhost:8080/#{%22ok%22:true,%22access_token%22:%22xoxp-2252352428-2739147668-346727530357-9a3a812b961faeb97f6a649a3c6b6737%22,%22scope%22:%22identify,channels:read,chat:write:user,files:write:user%22,%22user_id%22:%22U02MR4BKN%22,%22team_name%22:%22&yet%22,%22team_id%22:%22T027EACCL%22}

Which results in:

This site can’t be reached
localhost refused to connect.

From #19 (comment)

I was thinking about the same thing and did a little research. From what I found, all cameras have aspect ratios that they support, and you can't force them into an unsupported aspect ratio. So iOS is always going to have a taller aspect ratio that most computer webcams.

But what we could do is crop the displayed video to a square and then crop each frame of the video that gets rendered to the gif. That would be more work, but it doesn't seem that difficult

Related to #33, since the PWA doesn't work in iOS, it seems the best approach for now is to remove the manifest.json when iOS is detected. Here's how pinafore does it: https://github.com/nolanlawson/pinafore/pull/443/files

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Would be really great for UX to be able to fit everything in one view without scrolling, with fixed position interface controls.

Note that this is on an iPhone X (aka TallPhone™), so I'm assuming it's definitely vertically overflowing an iPhone 7 or 8 or typical Android, but I have no idea.

some thoughts:

• shrink the input fields a bit
• move the logout to the footer?
• instead of "posting to &yet" show the team icon inside the dropdown where the slack logo is?
• make the "hold to record" button directly connected to the video?

just thoughts about how to save some space, nothing I'm set on suggesting

Splash screen should get for getusermedia and show a different message instead of the auth button.

The devDependency eslint was updated from 6.4.0 to 6.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴