DHdhruvbhatia·Dec 11, 2017Submission
Is it time for new maintainers of Paperclip?
2 points · Open discussionthoughtbot
paperclip
Ruby2010–2017
thoughtbot / paperclip · Archived
paperclip
Easy file attachment management for ActiveRecord
7Distinct people
7Mentions
0Explicit recommenders
9KGitHub stars
What to know before exploring
What it is
Easy file attachment management for ActiveRecord
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year7 dated mentions
Observed mentions: 2010-03-31 04:22:51 UTC to 2017-12-11 12:08:13 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2010 | 2010-01-01 00:00:00 UTC | 2011-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
7 sourcesApparently Paperclip library already covered this long before this vulnerability is published.
https://github.com/thoughtbot/paperclip/issues/2190#issuecom...
In Remote code execution vulnerability in ImageMagickI haven't done much Web work in Ruby, but in my head the first thing that comes to mind for file uploads is Paperclip[0]. I'd be curious to hear thoughts on the various alternatives (e.g. CarrierWave, Refile, Shrine).
[0] https://github.com/thoughtbot/paperclip
In Shrine – A new solution for handling file uploads in RubyInclude a photo of yourself in a monkey suit.
1 points · Open discussionBe sure to check out: http://github.com/thoughtbot/paperclip (this also has an amazon s3 integration api)
I share the same sentiment in that I know I could code out a solution in an afternoon and avoid spending 50 bucks a month for the rest of eternity.
But I also do understand what OP is pitching. Services like these make prototyping that much faster, so I see it as a win for the agile development community. If the prices come down to "scrappy developer" levels, then much more people here on HN will certainly get it. But hey, your first job is to make money so what the hell do i know?
In Ask HN / Review my startup: TransloaditAll of your examples still portray uniformity:
> git://github.com/thoughtbot/paperclip.git
You are accessing a resource that is partially identified by the username.
> smtp://user:pass@hostname/domain
The username and password is used for authentication to access the resource, but is part of its unique identification.
> http://news.ycombinator.com/user?id=krainboltgreene
The mistake actually lies with HN, because part of what should be used to identify the resource is instead a param.
> chrome://history/
This still fits because you are accessing a uniquely identified resource. Just because it is user-dependent does not mean it breaks REST.
In URLs Are The Uniform Way to Locate ResourcesExcept URI's aren't uniform. They're used in so many ways as to be confusing. For instance:
"git://github.com/thoughtbot/paperclip.git"
vs
"smtp://user:pass@hostname/domain"
vs
"http://news.ycombinator.com/user?id=krainboltgreene
vs
"chrome://history/"
The user name appears in the path, the username section, and the query params. All of these are pretty "standard" uses. So while they might be called "uniform" the reality is absolutely different.
In URLs Are The Uniform Way to Locate Resources