-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing Silently #142
Comments
@scott-joe I had no idea this was a for profit project. This is news to me. Apparently @lambtron decided to make that change without telling anyone on this repo. |
@scott-joe see #143 . I'm out! Good luck with the issues though. |
thank you for the issue @scott-joe. i will resume maintaining this. your comment about the copyright stuff is 100%. i threw the monetization together really quickly and wasn't sure if it would amount to anything. but making the necessary changes to avoid legal issues is on the road map. thank you! |
This took a minute to figure out because even
-d
had nothing to say, but I had a few issues using this tool.It uses
isURI
and thus cannot load files from the local system. I'm sure this has something to do with what I later discovered is Cheerio running an automation on the web form instead. The SlackAPI lets you list, but not write emoji. The error it gives around this is pretty confusing though.There is no error or explanation on why one portion of the tool has access to a private Github org or repo, but another part does not. As I discovered, the CLI tool can get the
.yaml
file because my Terminal is authenticated, but Cheerio is injecting private, yet valid URIs into a page that does not have access but does not stick around to wait for errors in uploading, so it fails silently.Just FYI. I realize this is 2 issues in one and I'm going to script a workaround using a public Github resources mirror, but I just wanted to share with you some error reporting issues and documentation upgrades you could make.
Oh, also, the https://emojipacks.com/ project can certainly provide copyright-protected content without getting sued because who cares, but selling that copyright-protected content is definitely going above and beyond a Cease and Desist letter and straight into sued for damages territory. I'd recommend you stop accepting payment for copyright-protected content you don't own immediately and pretend that never happened.
Cheers!
The text was updated successfully, but these errors were encountered: