Giter Club home page Giter Club logo

socatar's People

Contributors

greenkeeper[bot] avatar greenkeeperio-bot avatar renovate-bot avatar renovate[bot] avatar terales avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

Forkers

puzanov

socatar's Issues

Upgrade node.js to v10

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The engines config in 1 of your package.json files was updated to the new Node.js version

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

HTTPS is absent on redirect

I'm trying this:

$ curl -I https://socatar.com/github/yegor256/192-192
HTTP/2 302
date: Mon, 12 Feb 2018 13:44:10 GMT
content-type: text/plain; charset=utf-8
content-length: 189
set-cookie: __cfduid=d00dd786735697103fe864aace277bcc31518443050; expires=Tue, 12-Feb-19 13:44:10 GMT; path=/; domain=.socatar.com; HttpOnly; Secure
x-powered-by: Express
cache-control: public, max-age=31536000
location: http://res.cloudinary.com/hah9f7pyw/image/fetch/s--xAB3vnmu--/c_thumb,d_fallback.svg,f_auto,g_faces,h_192,w_192/https://avatars3.githubusercontent.com/u/526301%3Fv%3D4
vary: Accept
via: 1.1 vegur
cf-cache-status: HIT
expires: Tue, 12 Feb 2019 13:44:10 GMT
strict-transport-security: max-age=15552000; includeSubDomains; preload
x-content-type-options: nosniff
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 3ebffb277ee397b0-FRA

It redirects me to http://res.cloudinary.com/hah9f7pyw/image/...

The https part is replaced with http. It is wrong, I believe.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Warning

These dependencies are deprecated:

Datasource Name Replacement PR?
npm codacy-coverage Unavailable
npm raven Unavailable
npm request Unavailable

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

  • Update dependency cloudinary to v2
  • Update dependency dotenv to v16
  • Update dependency nodemon to v3
  • Update dependency nyc to v17
  • Update dependency rimraf to v6
  • Update dependency standard to v17
  • Update dependency streamsearch to v1
  • Update dependency supertest to v7
  • 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

npm
package.json
  • cloudinary 1.26.0
  • dotenv 10.0.0
  • express 4.17.1
  • lodash.get 4.4.2
  • lodash.set 4.3.2
  • raven 2.6.4
  • request 2.88.2
  • streamsearch 0.1.2
  • ava 3.15.0
  • codacy-coverage 3.4.0
  • coveralls 3.1.0
  • nodemon 2.0.7
  • nyc 15.1.0
  • rimraf 3.0.2
  • standard 16.0.3
  • supertest 6.1.3
  • node 14.17.x
travis
.travis.yml
  • node 12.13

  • Check this box to trigger a request for Renovate to run again on this repository

Image requests are redirected to lower quality cloudinary images

I'm reporting a trouble encoutered in usage

When I visit socatar to get an image from twitter (https://socatar.com/twitter/filrfreire) or github (https://socatar.com/github/filfreire), I'm directed to the following page:

https://res.cloudinary.com/hah9f7pyw/image/fetch/s--zRkvprgx--/c_thumb,d_fallback.svg,f_auto,g_faces,h_100,w_100/https://twitter.com/filrfreire/profile_image%3Fsize%3Doriginal

And no longer get a higher resolution image with the current URL being socatar.

Screenshot:
image

/cc @terales

Get written permissions to be used in the test cases and on the home page

As stated in the Code of conduct:

Publishing others' private information, such as a physical or electronic address, without explicit permission is an example of unacceptable behavior

To I want to ask if anybody could agree to share ANY of those and give project a permission to use profile photos in test cases and on the home page:

  • facebook slug
  • twitter name
  • email, preferably from GMail and with user pictures with GMail and Gravatar
  • Google+ id
  • GitHub username

Compare images mathematically instead of checksums

I'm regularly facing issues with Travic CI errors like this:

df0612c6367f537c53cce7f0a37dcb5f35232b31 a075635500ff0ce3234cbc7d520ef26749d461d0 google/sample1.jpg
2730 2731 'google/sample1.jpg'
2ee2dae364f0abe93ab39e0f65a3e9fe71af5e03 aa9c99acd15af25c0a049e8e95231d57169e3a87 google/sample2.jpg
2394 2395 'google/sample2.jpg'

Images received by Travis CI for some reason are one byte different from samples I've saved from my local PC. I've tried ti fix it with AppVeyor's Windows machines, but it has the same results :(

I think we should compare images by their content, not as black box files even if it would take more memory and time. It's more important to have reliable test results that saving several seconds here and there

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.