A proposition about tripfag cancer

Name
Email
Subject
Comment *
Verification *
File	Select/drop/paste files here
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Password	(For file and post deletion.)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, swf, pdf Max filesize is 8 MB. Max image dimensions are 10000 x 10000. You may upload 5 per post.

File: 1439943191783.png (708.28 KB, 593x882, 593:882, 12.png)

A proposition about tripfag cancer Anonymous 08/19/15 (Wed) 00:13:11 16b40f No.513

I am not sure if posting this on this board or /operate/ would be more appropriate.

I am reposting this from /b/, it's about tripcodes.

________

Trips are sometimes important, for example if someone is posting a long greentext story or if someone is giving advice, you get the idea.

I have a very limited understanding of cryptography but I know how tripcodes work on a very basic level. A "password" is input and a function, known as a hash function, turns the input to random letters and numbers. Obviously this function is the same for every thread on /b/, that means input 1234 generates the same output on all threads.

An overwhelming majority of /b/ dislikes tripfags, however, tripcodes are a valuable tool when needed, as specified before. My proposed solution to this is as follows, every new thread created on /b/ also has it's unique hash function for generating tripcodes. Since tripcodes, when used for legitimate reasons, are only useful in one thread. Tripfags now cannot identify their superior selves in every thread since anyone can now claim to be any tripfag.

What do you think? Does something like this take a long time to program and implement? is hotwheels lazy?

Tl;dr: make tripcodes unique to threads i.e tripcode input "1234" generates "fhvt&!4" in one thread while generating "hkug!!" in another thread.

________

Does that sound like a good idea?

Anonymous 08/19/15 (Wed) 06:18:12 79e91e No.516

That doesn't change anything. Namefags will still namefag.

Just add optional threadly IDs that you can toggle in the post options.

Anonymous 08/19/15 (Wed) 08:56:47 f2e15f No.517

>>513

That doesn't change anything.

1. On /intl/, any time a Philippines flag appears on a post, they assume it is me and spam the thread.

2. There are a few people who use no name but post exclusively with a single character as their file attachment to create an avatar.

3. Nothing stops me from signing my posts, "t. Josh", even with thread IDs / name fields / even attachments disabled.

In short, if someone wants to be not-anonymous, nothing can be done to stop that, besides maybe banning them / ignoring them / chasing them off the site.

copypaste's current project is a cool revision of tripcodes I think people will like.

Anonymous 08/19/15 (Wed) 13:46:40 2abbc1 No.519

File: 1439992000081-0.gif (2.79 MB, 377x240, 377:240, Tripfags.gif)

File: 1439992000081-1.png (364.72 KB, 1141x1024, 1141:1024, tripfag cancer.png)

>>513

You hate tripfags? Watch pic related.

This is literally all everybody needs to do, tripfags would go away if you just stopped replying to them.

Anonymous 08/19/15 (Wed) 21:31:18 16b40f No.530

>>519

yes, the majority of people already know that. It only takes 1 or 2 anons to feed the tripfags.

It's like having a bank vault without a lock and telling people to not rob it. Most people wont attempt to rob but it only takes one thief to empty it

Anonymous 08/19/15 (Wed) 21:36:04 16b40f No.531

>>517

If you sign your post T.josh you are still anonymous since anyone can do the same. With tripcodes only you can "sign" your posts with your unique trip

>There are a few people who use no name but post exclusively with a single character as their file attachment to create an avatar.

there is no way to know that the anons who post avatars are the same. Each avatar post could be from a different anon since anyone can post with avatars.

Also my proposition wasnt to eliminate avatarfags or the likes, only tripfags

Anonymous 08/21/15 (Fri) 01:12:19 b22f33 No.644

>>639

that does nothing to stop the determined/autistic

look at this

>https://8ch.net/settings.php?board=next

>"image_reject_repost":true

This means that reposts of images should be rejected, right? You shouldn't be able to post the same image twice?

Anonymous 08/21/15 (Fri) 01:13:24 b22f33 No.645

File: 1440119604233.png (120.45 KB, 324x433, 324:433, gnome.png)

>>644

take this dank meme for example

Anonymous 08/21/15 (Fri) 01:15:55 b22f33 No.646

File: 1440119755665.png (120.45 KB, 324x433, 324:433, gnome.png)

>>645

now open it up in hex editor and add some 0/NULL bytes to the end (or just use GNU truncate)

Anonymous 08/21/15 (Fri) 01:17:31 b22f33 No.647

>>645

>>646

now, if you compare them using imagemagick, you'll see that the images are the exact same, pixel for pixel, yet the two images still have different MD5 hashes

http://www.imagemagick.org/Usage/compare/

Anonymous 08/21/15 (Fri) 01:22:41 b22f33 No.648

File: 1440120162104.png (37.62 KB, 324x433, 324:433, difference.png)

>>647

just like I said, no difference at all between the images


$ compare gnome.png gnome1.png difference.png

Anonymous 08/21/15 (Fri) 01:33:43 b22f33 No.649


$ cp "/home/anon/Pictures/dank memes/gnome.png" "/home/anon/Desktop/"
$ md5sum "/home/anon/Desktop/gnome.png"
83b4e1751a01016d61743cf1be37209a */home/anon/Desktop/gnome.png
$ truncate -s +1 "/home/anon/Desktop/gnome.png"
$ md5sum "/home/anon/Desktop/gnome.png"
7af98dc13caa04d753868f302952444c */home/anon/Desktop/gnome.png

Anonymous 08/21/15 (Fri) 01:35:44 b22f33 No.650

>>649

83b4e1751a01016d61743cf1be37209a is the md5 hash of gnome.png, posted >>645

and

7af98dc13caa04d753868f302952444c is the md5 hash of gnome.png, posted >>646

Anonymous 08/21/15 (Fri) 02:26:16 b22f33 No.652

>>651

oh, then yeah, that sounds cool

I think this is already planned, but if it isn't, I know that it was definitely suggested more than once previously

I thought you were referring to banning specific images

Anonymous 08/21/15 (Fri) 03:01:44 2f46ba No.653

i keep on telling people that md5 is borked but they say "no it's not" "it doesn't matter" or "that doesn't affect me"

this is concrete example of how md5 is harmful when used in software

Anonymous 08/21/15 (Fri) 03:51:26 dde8fa No.654

>>513

Isn't that just how the IDs work now on /v/ and suchlike?

Anonymous 08/24/15 (Mon) 05:14:21 9dbf51 No.689

>>513

Not every board is /b/.

For some threads (like generals for a game that has devs for the game posting in it) they need to last more than one thread

Anonymous 09/04/15 (Fri) 16:20:55 000000 No.799

File: 1441383655846.png (58.34 KB, 324x433, 324:433, dank meme.png)

>>645

>>646

>>648

md5sum would work in this scenario if it there was an additional check after the thumbnail creation. The thumbnail for both the proposed gnomes is 1de1ae907c05261db45191f7bff60a96.

So, it would be enough to

- check the md5sum after the thumb creation server-side

- check the md5sum twice; the first check saves server resources (if the image is unmodified, it's filtered directly without even creating a thumb)

Filtering identical thumbnails could have unintended side effects (i.e. two users on the tech board are in a contest for the "smaller png", their thumbs could be the same) (I've seen threads like that) but I guess the BO knows best

Anyway,

>still md5sum

quite inane tbh

Anonymous 09/04/15 (Fri) 16:33:24 000000 No.800

>>799

>Filtering identical thumbnails could have unintended side effects (i.e. two users on the tech board are in a contest for the "smaller png", their thumbs could be the same)

It seems it's not what's happening. "dank meme.png" is just an (identical) re-compressed gnome.png,,, but the thumbnail differs.

Anonymous 09/22/15 (Tue) 00:14:38 dde8fa No.1061

>>516

This nigger has the best idea.

Surely it isn't that much work if we've already got a thread ID system anyway?