Open sourcing pouet.net ?

category: offtopic [glöplog]

So all we ended up with this open source bull-shit thread was that we are to deploy crap "renderTop10Prods()" code but no proper api?

And instead of a proper api per general we ask lawyers if we can publish the database?

LOL.

Ok might as well scrap me from the site aswell. Together with all the products ive added since they are not facts, they are all pouet statements and most of them never existed.

BBL with new accounts.

added on the 2013-05-12 10:50:59 by Hatikvah

Why don't you empty all that emotion into a well crafted pull request and patch, Haktivah?

added on the 2013-05-12 11:11:03 by rc55

Quote:

Hatikvah:
So all we ended up with this open source bull-shit thread was that we are to deploy crap "renderTop10Prods()" code but no proper api?

And instead of a proper api per general we ask lawyers if we can publish the database?

Hey, things take time. The people contributing to Pouet (on the source or otherwise) can't do everything at once, and are otherwise busy with their jobs, etc. Most of this thread was done during the last week. So assuming a full work week, that leaves only evenings to do something.

It's also not like anyone has backtracked on putting in a "proper API", things just have to get there. Unless you're going to start contributing to the code yourself, I think you should have a little patience and some faith! :)

We don't need to start a whole other argument over in here. We've already had 38ish pages of that.

I think this needs repeating:
BB Image

added on the 2013-05-12 11:51:16 by Starchaser

Perhaps we should go make a demo about this...

added on the 2013-05-12 11:58:12 by trc_wm

Hi
can you explain if you can, in laymans terms, just what is missing or is wrong with the current version of pouet? It is fast and is up all the time, and its main features (bbd, demo db and oneliner) are working fine. I honestly dont know ?!!

added on the 2013-05-12 12:52:23 by Navis

@ Navis
Well, non-technically, no, there isn't anything "wrong". It works.

However, as noted after the first short period of being open source on GitHub, there were at least a few SQL injection security holes, that even if it weren't open could have eventually been found and used.

The code itself is also complicated and doesn't take in to account newer technologies that would make it easier to avoid such mistakes. The complicated nature of it also makes it hard to add new features without increasing the maintenance complexity or chance of breaking other existing features. There are plenty of new features or improvements to existing features that could be integrated if it were easier to do.

added on the 2013-05-12 13:01:07 by Starchaser

If you want an explicit list of things "missing", you can check the roadmap in the main readme or the issues listed at the project's github project repository.

added on the 2013-05-12 13:03:25 by Starchaser

Quote:

by AMcBain:
there were at least a few SQL injection security holes

holes found and fixed*

added on the 2013-05-12 13:04:15 by Starchaser

I guess ideally the new commits should not go to 'live pouet' immediately and should be reviewed to make sure that new exploits are not being introduced?

added on the 2013-05-12 14:48:16 by Dbug

Normally if you use the pull model and topic branches, merging / commiting to master *is* the result of a review.

added on the 2013-05-12 14:56:52 by _-_-__

Dbug: the readme at https://github.com/kebby/pouet.net/tree/master/contribs explains the process. Changes aka pull requests are first tried out on a staging version of the site, and when they're approved they go to the master branch which will auto-deploy on the live site.

added on the 2013-05-12 15:02:54 by kb_

Now we've got everything pretty much sorted, we can get cracking on the next problem: deleting iq's account. :P

added on the 2013-05-12 16:52:13 by psonice

lator: API is planned, no worries, it's gonna happen !

/!\ DONT PANIC /!\

added on the 2013-05-12 21:17:20 by analogue

damn, this thread is growing super fast!

I'm kinda lost here, can someone please try to summarize the last 42 pages in few paragraphs?

added on the 2013-05-12 21:46:45 by TLM

Everything is well again. Sort of.

added on the 2013-05-12 21:49:20 by Saga Musix

TLM: Analogue wanted to open up the Pouet codebase, but people were concerned that this would interfere with Gargaj's work on Pouet v2. So then PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES PONIES and both versions were open-sourced, and Gargaj is still an admin and is still going to work on Pouet v2, and a bunch of other people have submitted security patches and new features, and people are working on getting as much data as possible available while staying on the right side of privacy/copyright, and everyone learned an important lesson about friendship.

added on the 2013-05-12 22:11:41 by gasman

so friendship IS magic!

added on the 2013-05-12 22:16:17 by ted

I do not understand what is issue with pouet open sores and pouet API ??? Pouet has had API for years !! I recently discuss with Gargaj and he say this not dangerous feature!! I implement following high-tech bash script for direct pouet.NET DB interface:

Code:

#!/bin/bash

function urlencode {
    echo -ne "$@" | xxd -plain | tr -d '\n' | sed 's/\(..\)/%\1/g'
}

POUET="http://pouet.net/bbses.php"
MAGIC="0%20%55%4e%49%4f%4e%20%41%4c%4c%20%53%45%4c%45%43%54%201"
QUERY="which=${MAGIC},("`urlencode $1`"),0xba,0xdc,0xed,0xbe,0xef,0xba,0xbe%23"
curl -s "${POUET}?${QUERY}" | grep "which=1" | cut -c 37- | awk -F '</a>' '{print $1}'

is use is simple. normal SQL interface, lets find prod with most votes:

Code:

$ ./pouet.sh "SELECT name FROM prods ORDER BY voteup DESC LIMIT 1"
fr-041: debris.

see, easy for average SQL/Webmonkey!! One restriction here.. we can only is limit to ONE column and row per result. but clever monkey can is make use of GROUP_CONCAT and friends hehhheh.

I call this Pouet BOP interface! (BBS Oriented Programming) Have fun!!

added on the 2013-05-12 22:20:39 by blasty

there's an error in your code man, it should be MAGIC="FRIENDSHIP"

added on the 2013-05-12 22:30:57 by nic0

Oh, is one more problem. if user want use string literals, cannot use normal notation 'like this' or 'LIKE THAT'. Will have to use hex encoded string literal to is make bypass of quote characttre.

For example we want find group ID of most famous BITS (HERMAN SAMSO) group. We is convert "BITS" to hex -> 42 49 54 53 and make craft SQL query:

Code:

$ ./pouet.sh "SELECT id FROM groups WHERE name = 0x42495453"
5718

Bingo! Group ID 5718 is BITS!

added on the 2013-05-12 22:31:43 by blasty

Another practic exampl. Say if you dont like person called MAGIC and want to know where he hang on Pouet BBS. So you can avoid direct contact with this guy..

We find ID for MAGIC guy:

Code:

$ ~/pouet.sh "SELECT id FROM users WHERE nickname = 0x4d61676963"
4627

Now.. we find all post for evil magic guy:

Code:

 for i in `seq 0 100`; do ~/pouet.sh "SELECT DISTINCT topic FROM bbs_posts WHERE author = 4627 LIMIT $i,1" ; done
1293
1710
1603
640
1754
1806
1812
1830
1799
1842
..

get creative!!!

added on the 2013-05-12 22:38:02 by blasty

Quote:

so friendship IS magic!

<3 <3 <3 (:

added on the 2013-05-12 22:48:37 by gaspode

Gloom: I'm really concerned about what you did here. Page after page, you did nothing but fuel the fire.

In my opinion, the opposite of "let's pretend nothing happened and move on" isn't what you did.

Gloom, these are your words (emphasis mine):

Quote:

As a community, I can't accept that we just stand back and watch while these events unfold.

Quote:

Analogue is getting resistance because he's in the wrong, and doubly so because of the way he responds to the resistance. The fact that he's unable to grasp just how badly he has behaved and mismanaged the situation just makes it worse.

Gloom, you don't accept the situation: I get it. You raise your voice: perfectly fine by me. But please acknowledge my humble (hopeless?) resistance against your violent behavior. I feel outraged by the way you handled it: you mismanaged it, really. Post after post, you just spread more and more hate.

Gloom, since we're not sharing projects together I believe we'll never have to disagree on something else than comments on Pouet. And in fact I feel relieved because you apparently use everything it takes to crush your opponents (from your own fame to networking). Again, that doesn't mean I'm with Analogue (we don't even know each other bla bla bla etc.)

All in all Gloom, we didn't need your campaign against Analogue. We needed Analogue to have the guts to apologize. We needed Gargaj to get through the difficult pride/trust situation. Hopefully, that's how it ended.

Gloom, I wish we could have all read you after Analogue apologized.
Gargaj, you impressed me.

added on the 2013-05-12 23:25:43 by guardian ٩๏̯͡๏۶

Q439#2!:

Quote:

All in all Gloom, we didn't need your campaign against Analogue.

Not sure about that. I think he made a difference. I think you're just reacting to his style. When Gloom is right, he is usually loud about it. And Gloom is seldom wrong.

And if things like style could rub you the wrong way, you should steer clear of pouet. It's a dreadful place. In fact, if there was no pouet tomorrow, I would shed no tears. But if I did, it would be on behalf of the poor sod that kept the site alive and functional before it was shot down by a nostalgic jerk.

added on the 2013-05-13 00:36:53 by Hyde

Quote:

by ٩๏&#:
We needed Analogue to have the guts to apologize. [...] Hopefully, that's how it ended.

Yes, yes it did. Please read back a page two pages, thanks.

added on the 2013-05-13 00:39:13 by Starchaser

pouët.net

Open sourcing pouet.net ?

login