823 karma · joined December 11, 2015
This makes perfect sense, and at the end of the day those who produce there content have a right to choose the conditions of how it's distributed
I would love to see this concept applied to news aggregators
As they get more interested I switch to https://tryruby.org then scraping with nokogiri then asking them about the problems they want to solve.
(Add `begin; rescue; end` where errors need to be handled)
2) Search if found keys are actual valid keys
3) Expire key, send explanatory email, issue new key
(I think that's what AWS does)
There are just so many of those it's crazy:
remove .env
YOURFAVORITEAPI_SECRETKEY
YOURFAVORITEAPI_PASSWORD
Also replace "remove" with delete/rm/replace/etc.And replace "YOURFAVORITEAPI" with CircleCI, Travis, Mailchimp, Trello, Stripe, etc, etc.
Also, companies I contacted consider it the customer fault and basically don't care.
That's some nice common sense there!
So, he just sends a gist link to his teammates? why not create a small pull request and then asking them to look over it?
And it's open source: https://github.com/dli/paint (I posted my issues there)
Ruby:
class X
attr_accessor :y
end
Crystal (full working example): class Y
end
class X
def initialize(y : Y)
@y = y
end
def y
@y
end
end
y = Y.new
x = X.new(y: y)
puts x.y