Hacker News Reader

Comment by dmonitor | Hacker News Reader

I haven't seen any porn site with tagging, search, or browse features as well made as e621 (or any booru website)

I think because most of these sites are dominated by user uploads, it doesn't really help to have a great tagging system, because inevitably you end up with a huge library of videos with insufficient/wrong tags. Arguably the majority will have shitty tags, lots of misspellings, etc. The consequence is if you did an AND search with 6 tags say, you'd end up exclude most if not all the results that would match your query if properly tagged.

Weeaboo sites seem to be an exception for some reason, probably because the average community member is obsessive/hoardy enough to give a shit about tagging at all.

IDK, feet people have their own wiki. I think it would really depend on the fetish. Engineers are into BDSM, etc.

IMO the only booru like site that has a better tagging/searching system than esix is derpibooru. It is fast enough to be almost scary. Even with highly complex filters.

I was curious because I am a back-end tech nerd, and apparently "derpibooru" (I had no idea what to expect) is running on Elixir (I assume Phoenix) specifically this:

https://github.com/philomena-dev/philomena

Edit: PLEASE BE AWARE OF THE LICENSE, it is AGPL licensed, which means if you copy any of the code into your back-end, your whole back-end must be open sourced, as a back-end nerd I stay away from anything AGPL'd just to be on the safe side of the law.

Fud. To quote section 13 of the AGPL license: "Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License."

AGPL Section 13 as you quote it discussed the interaction of AGPL and GPL v3. It has nothing to do with the scenario the parent commenter was discussing involving the interaction of AGPL and closed-source non-GPL code.

Well, does that allow you to have the rest of your backend GPL licensed and simply not distributed? Nobody has a right to see the code unless they have the executable, and you're not giving anyone the executable, so...

Kind of unfortunate if there's a leak though.

A leak of an executable doesn't imply a requirement to provide source anymore than a theft implies a warranty.

I meant a leak of the source code, not the executable. If the source code comes with a license that was intentionally applied by the copyright holder, does it matter that it wasn't intended to be released if the license allows for general use?

If I make changes to a GPL3 library, but never distribute it, and you come along and leak it, you've distributed my changes without a license. Those changes are toxic, and the result cannot be distributed by anyone. It's not really any different than the usual dance one has to perform to combine two components with incompatible licenses: you can mix the ingredients yourself, you can tell people how to mix the ingredients themselves, but you can't distribute the cake.

Sounds like generic copyright feature, when you assign license on per file basis in source form. Such compiled combined work will be licensed under AGPL:

13. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

"but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such."

I'm not sure where you got this, but that phrasing is not part of the AGPL license as posted on https://www.gnu.org/licenses/agpl-3.0.html

It's from GPL3.

> if you copy any of the code into your back-end, your whole back-end must be open sourced

That’s a feature, not a bug. If you don’t want that, don’t use it.

Correct, but it would be foolish not to warn people BEFORE they peek around the code. GPL (and by extension I assume AGPL) states that even translating the work to a new language still constitutes as copying and therefore the resulting code must be GPL'd.

All projects like this prominently include the license file in the root directory of their code repository. If you don’t read that, you only have yourself to blame. If you have read it but still don’t understand how the license works, don’t touch it or ask a lawyer to help.

https://cdn.discordapp.com/attachments/662895347911098368/92...

a demo of the search engine running locally. Yes, it is that fast. And its not just counts, but the actual result sets. (in this case, no fetching is done though)

Also supports and/or, even nested, along with ranking by whether it has a specific search term (called boosting in the documentation) Oh, and in the example, the default blacklist was used. https://derpibooru.org/pages/search_syntax

That fucking website man. I literally googled the MSG "e number" one time, which is "e621" and in that moment my innocence was ruined.

Is it also surprising that the "booru" websites, which are likely frequented by the most ASD of the ASD inflicted men, would be well cataloged? It is simply what our brains do.

Reply on news.ycombinator.com