Navigation: /b/ - Random [+18] | Search | Interact with people having sex for free! [+18] | [Home]
RandomArchive logo

s/fur

The stories and information posted here are artistic works of fiction and falsehood.
Only a fool would take anything posted here as fact.

Thread replies: 190
Thread images: 151

s/fur
>>
File: Goth Sloth.png (903KB, 707x1000px) Image search: [Google] [Yandex] [Bing]
Goth Sloth.png
903KB, 707x1000px
>>
did some practice here yesterday, post something for me to copy or make a request, single character only
>>
File: 1389822337246.png (1MB, 690x861px) Image search: [Google] [Yandex] [Bing]
1389822337246.png
1MB, 690x861px
>>
File: 24.jpg (175KB, 1280x1080px) Image search: [Google] [Yandex] [Bing]
24.jpg
175KB, 1280x1080px
>>
File: 1389822694120.jpg (591KB, 1100x701px) Image search: [Google] [Yandex] [Bing]
1389822694120.jpg
591KB, 1100x701px
>>752395565
Draw a stronk tigress doing squats.
>>
File: 1389832290878.png (1MB, 900x1522px) Image search: [Google] [Yandex] [Bing]
1389832290878.png
1MB, 900x1522px
>>
File: 1389834649195.jpg (398KB, 791x612px) Image search: [Google] [Yandex] [Bing]
1389834649195.jpg
398KB, 791x612px
>>
File: 1389835353862.jpg (1MB, 1280x768px) Image search: [Google] [Yandex] [Bing]
1389835353862.jpg
1MB, 1280x768px
>>
File: 1389841611075.png (1MB, 1044x1272px) Image search: [Google] [Yandex] [Bing]
1389841611075.png
1MB, 1044x1272px
>>
File: 1376347202681.jpg (55KB, 571x800px) Image search: [Google] [Yandex] [Bing]
1376347202681.jpg
55KB, 571x800px
How do you know when you've been lurking s/fur/ too long.
Just dug through my fur downloads folder and found threads from 2013.
The ride truly never ends

Pic related first ever image I downloaded from a fur thread.
>>
File: 1389841952485.png (330KB, 1265x752px) Image search: [Google] [Yandex] [Bing]
1389841952485.png
330KB, 1265x752px
>>752395950
You've been here too long when fur posting becomes your priority. Been here since Feb 2012.
>>
File: 1389908207112.png (605KB, 1000x1277px)
1389908207112.png
605KB, 1000x1277px
>>
>>752395950
>1376347202681.jpg

Monday, August 12, 2013 3:40:02.681 PM

to be precise. I have a script that downloads any thread that has the word "s/fur" in the OP. I may have gone too far.
>>
File: 1389909029805.jpg (83KB, 640x828px) Image search: [Google] [Yandex] [Bing]
1389909029805.jpg
83KB, 640x828px
>>
File: 1389916768553.png (296KB, 597x876px) Image search: [Google] [Yandex] [Bing]
1389916768553.png
296KB, 597x876px
>>
File: 1390004179182.jpg (248KB, 887x560px) Image search: [Google] [Yandex] [Bing]
1390004179182.jpg
248KB, 887x560px
>>
File: 1390004191982.jpg (59KB, 500x500px) Image search: [Google] [Yandex] [Bing]
1390004191982.jpg
59KB, 500x500px
>>
File: 1390005703220.png (581KB, 800x1066px) Image search: [Google] [Yandex] [Bing]
1390005703220.png
581KB, 800x1066px
>>
File: 1475478695104.png (1MB, 997x768px) Image search: [Google] [Yandex] [Bing]
1475478695104.png
1MB, 997x768px
>>752396091
How many dupes you end up with?
Not to mention all the hetty posting that used to happen in these threads.
>>
File: 1390007807497.png (209KB, 1087x810px) Image search: [Google] [Yandex] [Bing]
1390007807497.png
209KB, 1087x810px
>>
File: 1390008792328.png (625KB, 633x954px) Image search: [Google] [Yandex] [Bing]
1390008792328.png
625KB, 633x954px
>>
File: 1390009619677.png (980KB, 1200x1115px) Image search: [Google] [Yandex] [Bing]
1390009619677.png
980KB, 1200x1115px
>>
File: 1390015517293.png (265KB, 1000x1000px) Image search: [Google] [Yandex] [Bing]
1390015517293.png
265KB, 1000x1000px
>>
>>
>>752395686
this is what i came up with, hope you like it!
>>
File: 1390019922381.jpg (614KB, 1100x988px) Image search: [Google] [Yandex] [Bing]
1390019922381.jpg
614KB, 1100x988px
>>
File: 1390021595008.png (912KB, 1000x1111px) Image search: [Google] [Yandex] [Bing]
1390021595008.png
912KB, 1000x1111px
>>752396577
Bretty gud. Thanks, anon.
>>
File: 1390024267596.jpg (391KB, 800x817px) Image search: [Google] [Yandex] [Bing]
1390024267596.jpg
391KB, 800x817px
>>
File: 1390024631253.jpg (333KB, 1227x1280px) Image search: [Google] [Yandex] [Bing]
1390024631253.jpg
333KB, 1227x1280px
>>
>>752396373
Not a lot since I store files by their md5 sum. deduplication happens automatically.

> $ du -abch 4chan/ | tail -n 1
> 1.8T total


So, alot.
>>
File: 1390102920003.jpg (197KB, 765x990px) Image search: [Google] [Yandex] [Bing]
1390102920003.jpg
197KB, 765x990px
>>
>>752395377
KILL YOURSELF! OOOHH YEAAAAAH!
>>
>>752396091
>I have a script that downloads any thread that has the word "s/fur" in the OP. I may have gone too far.
That probably is too far. How big is your folder now?
I wrote a thread fetcher to download these threads, but don't really use it much anymore. It's easier to find what I want on image booru sites.
>>
File: 1390109717012.png (953KB, 829x981px) Image search: [Google] [Yandex] [Bing]
1390109717012.png
953KB, 829x981px
>>
>>752396728
>>752396794
1.8Tb. wat.
>>
File: 1390110840506.jpg (1MB, 1280x1120px) Image search: [Google] [Yandex] [Bing]
1390110840506.jpg
1MB, 1280x1120px
>>
File: 23.jpg (158KB, 707x1000px) Image search: [Google] [Yandex] [Bing]
23.jpg
158KB, 707x1000px
>>
File: 1504749475657.png (927KB, 1481x1422px) Image search: [Google] [Yandex] [Bing]
1504749475657.png
927KB, 1481x1422px
>>
File: 1507870369568.jpg (156KB, 1280x960px) Image search: [Google] [Yandex] [Bing]
1507870369568.jpg
156KB, 1280x960px
>>752396794
See: >>752396728

About 1.8 Terabytes
>>
File: 1390111788332.png (350KB, 581x1000px) Image search: [Google] [Yandex] [Bing]
1390111788332.png
350KB, 581x1000px
>>
>>752396916
I saw. That's all deduplicated?
>>
File: 1390112213703.png (477KB, 1200x886px) Image search: [Google] [Yandex] [Bing]
1390112213703.png
477KB, 1200x886px
>>
>>752396954
>I saw. That's all deduplicated?
right now it only deduplicates across a single board. It scrapes >>>/trash/ too. Also, I keep revisisions of the thread text so I can find where pics were deleted. At 1-2 MB per pic, it gets big pretty fast.
>>
File: 1390112913184.png (1MB, 1024x1020px) Image search: [Google] [Yandex] [Bing]
1390112913184.png
1MB, 1024x1020px
>>
File: 1390112949870.png (680KB, 700x960px) Image search: [Google] [Yandex] [Bing]
1390112949870.png
680KB, 700x960px
>>
File: 1507871857272.png (629KB, 695x900px)
1507871857272.png
629KB, 695x900px
>>
File: 1390123990164.jpg (201KB, 401x800px) Image search: [Google] [Yandex] [Bing]
1390123990164.jpg
201KB, 401x800px
>>
>>752396728
Doing gods work
When did you start downloading?
>>
File: 1390188094959.jpg (308KB, 1200x1015px) Image search: [Google] [Yandex] [Bing]
1390188094959.jpg
308KB, 1200x1015px
>>
>>752397043
Are you only removing exact duplicates? There's often a lot of images with the same content with a different res or quality.

With that many images, have you considered lossless jpeg & png optimisers?
>>
File: 1390193762127.jpg (1MB, 932x1280px) Image search: [Google] [Yandex] [Bing]
1390193762127.jpg
1MB, 932x1280px
>>
>>752395565
This is great art.
Requesting a character inviting anon on her lap.
>>
File: 1508308014026.jpg (357KB, 848x1200px) Image search: [Google] [Yandex] [Bing]
1508308014026.jpg
357KB, 848x1200px
>>
File: 1390194060022.png (160KB, 505x800px) Image search: [Google] [Yandex] [Bing]
1390194060022.png
160KB, 505x800px
>>
File: 1390194672976.png (125KB, 334x486px) Image search: [Google] [Yandex] [Bing]
1390194672976.png
125KB, 334x486px
>>
https://youtu.be/72kis_9r8Yc?t=300

I'm curious about this clip where the face is hidden. Do you think they were aware of gateway furrying kids back then so they hid the face or are we to assume that it was a human Goofy gets a boner for.
>>
>>752397325
sure, any preference?
>>
>>752397415

Time stamp is 5 mins
>>
File: 1390194836931.png (776KB, 619x900px) Image search: [Google] [Yandex] [Bing]
1390194836931.png
776KB, 619x900px
>>
File: 1507875755970.png (456KB, 1000x1294px) Image search: [Google] [Yandex] [Bing]
1507875755970.png
456KB, 1000x1294px
>>752397200
Around 2011? I scraped threads manually for a long time

>>752397279
Yeah. A lot of times people upload a jpg version of something, so the md5 sum doesn't match. I have more advanced algorithm for finding dupes, but it requires manual intervention since it isn't exact. It uses signal processing.


Like I said, probably too far.
>>
>>752397429
Anything motherly, pudgy female character with a sweater perhaps.
>>
File: 1390194878822.png (1MB, 1200x1000px) Image search: [Google] [Yandex] [Bing]
1390194878822.png
1MB, 1200x1000px
>>
>>
File: 1390195019123.jpg (286KB, 879x1171px) Image search: [Google] [Yandex] [Bing]
1390195019123.jpg
286KB, 879x1171px
>>
File: IMG_0802.jpg (288KB, 1019x1723px) Image search: [Google] [Yandex] [Bing]
IMG_0802.jpg
288KB, 1019x1723px
ok so someone said this mare was urinating, I believe it to be arousal, whats your opinion?
>>
File: 1390195052485.jpg (132KB, 800x660px) Image search: [Google] [Yandex] [Bing]
1390195052485.jpg
132KB, 800x660px
>>
File: 1390195085505.jpg (285KB, 600x830px) Image search: [Google] [Yandex] [Bing]
1390195085505.jpg
285KB, 600x830px
>>
>>752397638

Water bender
>>
>>752397638
squash soup looks different than piss. That looks like piss.
>>
File: 1502192988212.gif (839KB, 450x402px) Image search: [Google] [Yandex] [Bing]
1502192988212.gif
839KB, 450x402px
>>752396915
NOOOOOOOOOOOOOO
NOOOOOOOOOOOOO
LEAVE HER OUT OF THIS
MNOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

MY CHILDHOOD
NOOOOOOOOOOOOOOOO
>>
>>752397469
I wrote an algorithm that compares the histograms of images for that. It does a good job of finding near duplicates. It lists them for me and I can decide what I don't want to keep.

Image optimisation usually saves 10-20% of space, and it can get some pics under 2mb for here on /b/.

I only have ~21,000 pics. I'm slowly going through it and getting rid of things I don't like because even what I have is a lot to manage.
>>
File: 1390195653918.png (1MB, 989x1280px) Image search: [Google] [Yandex] [Bing]
1390195653918.png
1MB, 989x1280px
>>752397638
Considering that it's coming out in a stream just above her clit, definitely pee. Which is hot too.
>>
File: 1390195789081.png (285KB, 700x700px) Image search: [Google] [Yandex] [Bing]
1390195789081.png
285KB, 700x700px
>>
>>752397847
i always assumed it was like when a mare is on heat which is kinda a mixture of both but i don't mind peeing so long as it's not on me
>>
File: 1390195965016.png (782KB, 829x1099px) Image search: [Google] [Yandex] [Bing]
1390195965016.png
782KB, 829x1099px
>>752397905
>peeing so long as it's not on me
But that's the best part!
>>
File: 1390275292063.jpg (727KB, 1280x953px) Image search: [Google] [Yandex] [Bing]
1390275292063.jpg
727KB, 1280x953px
>>
File: 1390275993627.jpg (415KB, 900x675px) Image search: [Google] [Yandex] [Bing]
1390275993627.jpg
415KB, 900x675px
>>
File: 1390276349122.jpg (360KB, 452x800px) Image search: [Google] [Yandex] [Bing]
1390276349122.jpg
360KB, 452x800px
>>
>>752397501
here she is, hope you like!
>>
File: 1507168028044.jpg (373KB, 728x1000px) Image search: [Google] [Yandex] [Bing]
1507168028044.jpg
373KB, 728x1000px
>>752397815
>I wrote an algorithm that compares the histograms of images for that. It does a good job of finding near duplicates. It lists them for me and I can decide what I don't want to keep.

That's cool, how do you store the histograms? I used a 2d cosine transform and then compared if components were above or below average

>Image optimisation usually saves 10-20% of space, and it can get some pics under 2mb for here on /b/.

Yeah, the tricky thing is then there are two md5 sums (since the file is now different).


>I only have ~21,000 pics. I'm slowly going through it and getting rid of things I don't like because even what I have is a lot to manage.

That's why having a lot is helpful. One day I'll correlate pics I like with the others in the thread. That way If other threads have duplicates of things I like, I can quickly cross reference them. For example:

I see thread A and like pic A1. If Thread B, which I haven't seen also has A1, then pics B1, B2, and B3 may be more interesting to me. (since pics in a thread are usually upload by a few people, who hopefully have similar tastes).

One day...
>>
File: 1390276968552.jpg (313KB, 584x992px) Image search: [Google] [Yandex] [Bing]
1390276968552.jpg
313KB, 584x992px
>>
>>752397952
Get back to work, Trump.
>>
>>752397952
How is she drinking carbonated pee? How do you carbonate it?
>>
>>752398146
Thanks for the request fill! See you around, adios
>>
File: 1390282951930.png (2MB, 960x1280px) Image search: [Google] [Yandex] [Bing]
1390282951930.png
2MB, 960x1280px
>>752398187
That's probably not pee, but that would be really hot.
>>
File: 1390620397659.jpg (340KB, 530x793px) Image search: [Google] [Yandex] [Bing]
1390620397659.jpg
340KB, 530x793px
>>
File: 047 - fliKFQs.jpg (351KB, 1920x1080px) Image search: [Google] [Yandex] [Bing]
047 - fliKFQs.jpg
351KB, 1920x1080px
>>752397952
That's not how those glasses work...
>>
File: 1390620937731.jpg (93KB, 1280x1224px) Image search: [Google] [Yandex] [Bing]
1390620937731.jpg
93KB, 1280x1224px
>>
File: 1390620954168.png (356KB, 573x909px) Image search: [Google] [Yandex] [Bing]
1390620954168.png
356KB, 573x909px
>>752398370
Welcome to furry art.
Hey, Gears.
>>
File: 1390621686496.png (999KB, 914x1588px) Image search: [Google] [Yandex] [Bing]
1390621686496.png
999KB, 914x1588px
>>
Hey degenerates, I have a question. Where do I find more fur porn? Specifically, cubs.

thanks
>>
File: 1390622528197.png (725KB, 553x1280px) Image search: [Google] [Yandex] [Bing]
1390622528197.png
725KB, 553x1280px
>>
>>
File: g1.png (549KB, 1200x1200px) Image search: [Google] [Yandex] [Bing]
g1.png
549KB, 1200x1200px
Anyone know how to contact the stairsync guy?
>>
>>752398494
e621.net
inkbunny.net
>>
File: 1390698899406.png (334KB, 444x650px) Image search: [Google] [Yandex] [Bing]
1390698899406.png
334KB, 444x650px
>>
>>752398166
>That's cool, how do you store the histograms?
In an xml database file, so they they can be quickly referenced. Generating them is kinda slow.
I was considering looking into using an edge detection algorithm to find duplicates, because I have a few 'duplicate' images where one is coloured in, and the other is just the raw sketch. I think that would allow me to find those kind of duplicates.
>Yeah, the tricky thing is then there are two md5 sums (since the file is now different).
I store MD5 checksums too, but mine are generated from the image data, rather than the image file. So a jpeg and a png file could store the same exact image data, and as a result have the same checksum. Optimising images in my case has no effect on the checksum, because optimisation is lossless.

>That's why having a lot is helpful. One day I'll correlate pics I like with the others in the thread. That way If other threads have duplicates of things I like, I can quickly cross reference them.
I never store the actual thread, only the images.
>>
File: g2.png (303KB, 750x975px) Image search: [Google] [Yandex] [Bing]
g2.png
303KB, 750x975px
>>752398494
>Where do I find more fur porn?
e621 or an imageboard named after a german submarine.
>Specifically, cubs.
inkbunny, or e621 with the 'young' tag.
>>
File: 1390700678953.jpg (130KB, 559x661px) Image search: [Google] [Yandex] [Bing]
1390700678953.jpg
130KB, 559x661px
>>
File: 1390706371226.jpg (606KB, 800x1200px) Image search: [Google] [Yandex] [Bing]
1390706371226.jpg
606KB, 800x1200px
>>
File: 1502940474207.gif (863KB, 500x500px) Image search: [Google] [Yandex] [Bing]
1502940474207.gif
863KB, 500x500px
>>752398548
>>752398402
PLS STOP
>>
File: 1390708690067.png (876KB, 1500x953px) Image search: [Google] [Yandex] [Bing]
1390708690067.png
876KB, 1500x953px
>>
File: 058 - snUn5Dc.png (2MB, 1586x892px) Image search: [Google] [Yandex] [Bing]
058 - snUn5Dc.png
2MB, 1586x892px
>>752398424
greetings
>>
File: 1390785360609.jpg (149KB, 1500x1500px) Image search: [Google] [Yandex] [Bing]
1390785360609.jpg
149KB, 1500x1500px
>>
>>752398713
no
>>
File: 1390788440575.jpg (129KB, 867x1200px) Image search: [Google] [Yandex] [Bing]
1390788440575.jpg
129KB, 867x1200px
>>
File: 1510042982503.jpg (43KB, 600x600px) Image search: [Google] [Yandex] [Bing]
1510042982503.jpg
43KB, 600x600px
>>752398838
pls stob
>>
File: 1390791005312.jpg (134KB, 768x1280px) Image search: [Google] [Yandex] [Bing]
1390791005312.jpg
134KB, 768x1280px
>>
File: 1390795557799.jpg (750KB, 800x1200px) Image search: [Google] [Yandex] [Bing]
1390795557799.jpg
750KB, 800x1200px
>>
File: 1390795894013.jpg (99KB, 853x1280px) Image search: [Google] [Yandex] [Bing]
1390795894013.jpg
99KB, 853x1280px
>>
File: 1390802174019.jpg (407KB, 668x1200px) Image search: [Google] [Yandex] [Bing]
1390802174019.jpg
407KB, 668x1200px
>>
File: 84568.jpg (197KB, 1109x1194px) Image search: [Google] [Yandex] [Bing]
84568.jpg
197KB, 1109x1194px
>>752398891
she loves cock
>>
File: 1390802444439.jpg (676KB, 1100x937px) Image search: [Google] [Yandex] [Bing]
1390802444439.jpg
676KB, 1100x937px
>>
File: 1505318136818.png (27KB, 733x640px) Image search: [Google] [Yandex] [Bing]
1505318136818.png
27KB, 733x640px
>>752399086
NO SHE DOESNT
PLS NOE MORE
>>
File: 1390802479640.png (906KB, 1056x900px) Image search: [Google] [Yandex] [Bing]
1390802479640.png
906KB, 1056x900px
>>
File: 1390802972464.png (2MB, 1280x1280px) Image search: [Google] [Yandex] [Bing]
1390802972464.png
2MB, 1280x1280px
>>
>>752399178
>>
File: 1505163117514.jpg (46KB, 480x480px) Image search: [Google] [Yandex] [Bing]
1505163117514.jpg
46KB, 480x480px
>>752399249
>>
File: 1390803219682.jpg (725KB, 841x1111px) Image search: [Google] [Yandex] [Bing]
1390803219682.jpg
725KB, 841x1111px
>>
File: 1390803229595.jpg (168KB, 905x1280px) Image search: [Google] [Yandex] [Bing]
1390803229595.jpg
168KB, 905x1280px
>>
File: 1390803283217.jpg (191KB, 766x1280px) Image search: [Google] [Yandex] [Bing]
1390803283217.jpg
191KB, 766x1280px
>>
File: 1500757549916.jpg (122KB, 826x1280px)
1500757549916.jpg
122KB, 826x1280px
>>752398615
> I was considering looking into using an edge detection algorithm to find duplicates, because I have a few 'duplicate' images where one is coloured in, and the other is just the raw sketch. I think that would allow me to find those kind of duplicates.

Edges can work, but you need to store them some how, and it breaks down if the image is cropped.

> I store MD5 checksums too, but mine are generated from the image data, rather than the image file. So a jpeg and a png file could store the same exact image data, and as a result have the same checksum. Optimising images in my case has no effect on the checksum, because optimisation is lossless.

imagemagic does this too, but it changed to using a different algorithm in later versions. (using spatial Moments of the brightness and chroma channels?)

> I never store the actual thread, only the images.

At some point I noticed the most racy (and interesting) pics were the ones mods delete. If you have a copy of the original thread, you can find that out retrospectively. You can also find what pics tend to get the most replies.
>>
File: 1390803324169.png (247KB, 900x675px) Image search: [Google] [Yandex] [Bing]
1390803324169.png
247KB, 900x675px
>>
File: 1511827116423.jpg (910KB, 1310x1185px) Image search: [Google] [Yandex] [Bing]
1511827116423.jpg
910KB, 1310x1185px
>>
File: 1390803460434.jpg (167KB, 639x762px) Image search: [Google] [Yandex] [Bing]
1390803460434.jpg
167KB, 639x762px
>>
File: 1503551089969.png (1MB, 1280x1531px) Image search: [Google] [Yandex] [Bing]
1503551089969.png
1MB, 1280x1531px
Also, sorry for nerding up this thread.

Already bought Christmas presents?
>>
File: 1390803679053.jpg (100KB, 942x1280px) Image search: [Google] [Yandex] [Bing]
1390803679053.jpg
100KB, 942x1280px
>>
File: 1503551448286.png (992KB, 1280x1166px)
1503551448286.png
992KB, 1280x1166px
>>752399485
what a bed wetter
>>
File: 1390803713800.jpg (197KB, 754x1000px) Image search: [Google] [Yandex] [Bing]
1390803713800.jpg
197KB, 754x1000px
>>
File: 1390803957347.jpg (151KB, 700x982px) Image search: [Google] [Yandex] [Bing]
1390803957347.jpg
151KB, 700x982px
>>
>>752399414
>Edges can work, but you need to store them some how, and it breaks down if the image is cropped.
Never intended to store the result. Just wanted to use it as an alternative way to find duplicates. Even if it's slow it shouldn't matter because I won't use it often.

>At some point I noticed the most racy (and interesting) pics were the ones mods delete. If you have a copy of the original thread, you can find that out retrospectively. You can also find what pics tend to get the most replies.
Do you have any way of searching your collection for these pics currently?
>>
File: 1390804551944.jpg (66KB, 453x1280px) Image search: [Google] [Yandex] [Bing]
1390804551944.jpg
66KB, 453x1280px
>>
File: 1390804699821.jpg (318KB, 778x1000px) Image search: [Google] [Yandex] [Bing]
1390804699821.jpg
318KB, 778x1000px
>>
File: wew2.jpg (199KB, 1164x1280px) Image search: [Google] [Yandex] [Bing]
wew2.jpg
199KB, 1164x1280px
>>752399550
Nerd stuff is good. And no, since I don't know what anyone wants. If they don't make it known, they get nothing. I'm not going to guess, and waste money on something that someone doesn't want.
>>
File: 1390804777758.jpg (784KB, 600x893px) Image search: [Google] [Yandex] [Bing]
1390804777758.jpg
784KB, 600x893px
>>
>>752399710
Yeah, when I scrape the thread I parse the json and then look for posts that have changed. If the post is completely gone, i re serialize my copy back into a special file called deleted.js.gz
>>
File: 1390804960972.png (719KB, 695x1000px) Image search: [Google] [Yandex] [Bing]
1390804960972.png
719KB, 695x1000px
>>
File: 1390804961217.jpg (461KB, 872x757px) Image search: [Google] [Yandex] [Bing]
1390804961217.jpg
461KB, 872x757px
>>
File: 1503553466828.jpg (428KB, 1200x1175px)
1503553466828.jpg
428KB, 1200x1175px
>>752399796
If you do the white elephant thing, you can still get something. I bought fidget spinners so I can see the looks on their face.


Also your pic is like furception
>>
File: 1390804995416.jpg (137KB, 544x661px) Image search: [Google] [Yandex] [Bing]
1390804995416.jpg
137KB, 544x661px
>>
File: 1390805027279.jpg (381KB, 1210x725px) Image search: [Google] [Yandex] [Bing]
1390805027279.jpg
381KB, 1210x725px
>>
File: 1390805120315.png (1MB, 900x934px) Image search: [Google] [Yandex] [Bing]
1390805120315.png
1MB, 900x934px
>>
>>752399848
I meant for the images that have the most replies and such. My thread fetcher doesn't really care. It just grabs the webpage every 30 seconds and downloads every file posted in the thread. Never thought to do anything more. If the image isn't to my tastes it gets deleted, so for me it wouldn't really matter if it was removed by a mod/user if the image itself was of low quality.
>>
File: 1493485250356.jpg (673KB, 3000x2000px) Image search: [Google] [Yandex] [Bing]
1493485250356.jpg
673KB, 3000x2000px
>>752395565
>>
File: 1390805370712.png (774KB, 700x906px) Image search: [Google] [Yandex] [Bing]
1390805370712.png
774KB, 700x906px
>>
File: 1390806040992.jpg (251KB, 1100x747px) Image search: [Google] [Yandex] [Bing]
1390806040992.jpg
251KB, 1100x747px
>>
File: 1390806154693.jpg (347KB, 600x800px) Image search: [Google] [Yandex] [Bing]
1390806154693.jpg
347KB, 600x800px
>>
File: 1503555104457.png (482KB, 891x900px)
1503555104457.png
482KB, 891x900px
>>
File: 1390806227742.png (726KB, 1000x1000px) Image search: [Google] [Yandex] [Bing]
1390806227742.png
726KB, 1000x1000px
>>
File: 1390862121043.jpg (127KB, 1280x853px) Image search: [Google] [Yandex] [Bing]
1390862121043.jpg
127KB, 1280x853px
>>
File: cat1.jpg (112KB, 758x517px) Image search: [Google] [Yandex] [Bing]
cat1.jpg
112KB, 758x517px
>>
File: 1390862155435.jpg (148KB, 1280x853px) Image search: [Google] [Yandex] [Bing]
1390862155435.jpg
148KB, 1280x853px
>>
File: 1390862309153.png (723KB, 1000x863px) Image search: [Google] [Yandex] [Bing]
1390862309153.png
723KB, 1000x863px
>>
File: 1390862446638.png (380KB, 850x617px) Image search: [Google] [Yandex] [Bing]
1390862446638.png
380KB, 850x617px
>>
File: 1390862556496.jpg (196KB, 1000x1200px) Image search: [Google] [Yandex] [Bing]
1390862556496.jpg
196KB, 1000x1200px
>>
File: 1390863012844.png (354KB, 600x999px) Image search: [Google] [Yandex] [Bing]
1390863012844.png
354KB, 600x999px
>>
File: 1390863566493.jpg (319KB, 1280x932px) Image search: [Google] [Yandex] [Bing]
1390863566493.jpg
319KB, 1280x932px
>>
File: 1390864001551.jpg (140KB, 592x821px) Image search: [Google] [Yandex] [Bing]
1390864001551.jpg
140KB, 592x821px
>>
File: 1390884380524.jpg (311KB, 965x800px) Image search: [Google] [Yandex] [Bing]
1390884380524.jpg
311KB, 965x800px
Night.
>>
File: b2.png (486KB, 1200x1000px)
b2.png
486KB, 1200x1000px
>>752400671
Night, Dash.
>>
File: 1508925387643.jpg (2MB, 2361x3056px) Image search: [Google] [Yandex] [Bing]
1508925387643.jpg
2MB, 2361x3056px
>>
File: 1501393281919.jpg (2MB, 2361x3056px) Image search: [Google] [Yandex] [Bing]
1501393281919.jpg
2MB, 2361x3056px
>>
File: 1494861863958.jpg (476KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1494861863958.jpg
476KB, 1233x2027px
>>
File: 1482904348813.jpg (368KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1482904348813.jpg
368KB, 1233x2027px
>>
File: 1500789616782.jpg (429KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1500789616782.jpg
429KB, 1233x2027px
>>
File: 1488230070183.jpg (429KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1488230070183.jpg
429KB, 1233x2027px
>>
File: 1486122345646.jpg (373KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1486122345646.jpg
373KB, 1233x2027px
>>
File: 1495494296803.jpg (290KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1495494296803.jpg
290KB, 1233x2027px
>>
File: 1501797893613.jpg (435KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1501797893613.jpg
435KB, 1233x2027px
>>
File: 1482202789254.jpg (337KB, 1233x2027px)
1482202789254.jpg
337KB, 1233x2027px
>>
File: 1493553840176.jpg (369KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1493553840176.jpg
369KB, 1233x2027px
>>
File: 1487608912388.jpg (389KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1487608912388.jpg
389KB, 1233x2027px
>>
File: 1507915680217.jpg (362KB, 1233x2027px) Image search: [Google] [Yandex] [Bing]
1507915680217.jpg
362KB, 1233x2027px
>>
There are 270 pages of this, before this?>>752401203
>>
>>752401456
Well, yeah.
>>
Asd
>>
>>752398559
>>
>>752398559
What do you need?
>>
>>752402644
?
>>752402656
To report his TLS setup is broken.
Compare:
http://stairsync.org/
https://stairsync.org/
Both Firefox and Chrome explain why, though they give two different reasons. Either way, it could be fixed.
>>
>>752402760
The first reply was an accident, hit enter by mistake. Anyway, I'll pass it on to him, though he's been MIA for a good few months now so idk if it'll actually reach him.
>>
>>752401456
Where can I find them?
>>
>>752402871
I see. Thank you. Does he have a name?
It's also broken for https://www.stairsync.org/ too, with the www.
>been MIA for a good few months now
I sadly know that feel. Thanks though, Tordenbrak!
>>
>>752402940
his name's just stairs, he used to be a gfur poster till he dropped off the board
>>
>>752403157
Ahh, okay. That does happen to a lot of people, huh.
>>
>>752402760
lol that was broken for AGES.
Don't even remember for how long.
looks like from 2015. LOL
>>
>>752403384
I also noticed the year 2015, too. He should switch to letsencrypt, probably.
>>
>>752402929
Don't know. It's old, I have no links.
And it appears I don't have it locally for some reason...
>>
bump
Thread replies: 190
Thread images: 151



Navigation: /b/ - Random [+18] | Search | Watch live sex for free! |
Navigation: /b/ - Random [+18] | Search | Watch people while having sex |


If you need a post removed click on it's [Report] button and follow the instruction.
If you like this website please support us by donating with Bitcoin at 1516QPvvjaBRziqhWPPJLvTaYxfUSBJswe
All trademarks and copyrights on this page are owned by their respective parties. Posts and uploaded images are the responsibility of the Poster. Comments are owned by the Poster.
This is a 4chan archive - all of the content originated from that website. If you need information about a Poster - contact 4chan. This project is not affiliated in any way with 4chan.