Navigation: /b/ - Random [Archive] | Search | [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 (903 KB, 707x1000) Image search: [Google]
Goth Sloth.png
903 KB, 707x1000
>>
did some practice here yesterday, post something for me to copy or make a request, single character only
>>
File: 1389822337246.png (1 MB, 690x861) Image search: [Google]
1389822337246.png
1 MB, 690x861
>>
File: 24.jpg (175 KB, 1280x1080) Image search: [Google]
24.jpg
175 KB, 1280x1080
>>
File: 1389822694120.jpg (591 KB, 1100x701) Image search: [Google]
1389822694120.jpg
591 KB, 1100x701
>>752395565
Draw a stronk tigress doing squats.
>>
File: 1389832290878.png (1 MB, 900x1522) Image search: [Google]
1389832290878.png
1 MB, 900x1522
>>
File: 1389834649195.jpg (398 KB, 791x612) Image search: [Google]
1389834649195.jpg
398 KB, 791x612
>>
File: 1389835353862.jpg (1 MB, 1280x768) Image search: [Google]
1389835353862.jpg
1 MB, 1280x768
>>
File: 1389841611075.png (1 MB, 1044x1272) Image search: [Google]
1389841611075.png
1 MB, 1044x1272
>>
File: 1376347202681.jpg (55 KB, 571x800) Image search: [Google]
1376347202681.jpg
55 KB, 571x800
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 (330 KB, 1265x752) Image search: [Google]
1389841952485.png
330 KB, 1265x752
>>752395950
You've been here too long when fur posting becomes your priority. Been here since Feb 2012.
>>
File: 1389908207112.png (605 KB, 1000x1277) Image search: [Google]
1389908207112.png
605 KB, 1000x1277
>>
>>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 (83 KB, 640x828) Image search: [Google]
1389909029805.jpg
83 KB, 640x828
>>
File: 1389916768553.png (296 KB, 597x876) Image search: [Google]
1389916768553.png
296 KB, 597x876
>>
File: 1390004179182.jpg (248 KB, 887x560) Image search: [Google]
1390004179182.jpg
248 KB, 887x560
>>
File: 1390004191982.jpg (59 KB, 500x500) Image search: [Google]
1390004191982.jpg
59 KB, 500x500
>>
File: 1390005703220.png (581 KB, 800x1066) Image search: [Google]
1390005703220.png
581 KB, 800x1066
>>
File: 1475478695104.png (1 MB, 997x768) Image search: [Google]
1475478695104.png
1 MB, 997x768
>>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 (209 KB, 1087x810) Image search: [Google]
1390007807497.png
209 KB, 1087x810
>>
File: 1390008792328.png (625 KB, 633x954) Image search: [Google]
1390008792328.png
625 KB, 633x954
>>
File: 1390009619677.png (980 KB, 1200x1115) Image search: [Google]
1390009619677.png
980 KB, 1200x1115
>>
File: 1390015517293.png (265 KB, 1000x1000) Image search: [Google]
1390015517293.png
265 KB, 1000x1000
>>
>>
>>752395686
this is what i came up with, hope you like it!
>>
File: 1390019922381.jpg (614 KB, 1100x988) Image search: [Google]
1390019922381.jpg
614 KB, 1100x988
>>
File: 1390021595008.png (912 KB, 1000x1111) Image search: [Google]
1390021595008.png
912 KB, 1000x1111
>>752396577
Bretty gud. Thanks, anon.
>>
File: 1390024267596.jpg (391 KB, 800x817) Image search: [Google]
1390024267596.jpg
391 KB, 800x817
>>
File: 1390024631253.jpg (333 KB, 1227x1280) Image search: [Google]
1390024631253.jpg
333 KB, 1227x1280
>>
>>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 (197 KB, 765x990) Image search: [Google]
1390102920003.jpg
197 KB, 765x990
>>
>>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 (953 KB, 829x981) Image search: [Google]
1390109717012.png
953 KB, 829x981
>>
>>752396728
>>752396794
1.8Tb. wat.
>>
File: 1390110840506.jpg (1 MB, 1280x1120) Image search: [Google]
1390110840506.jpg
1 MB, 1280x1120
>>
File: 23.jpg (158 KB, 707x1000) Image search: [Google]
23.jpg
158 KB, 707x1000
>>
File: 1504749475657.png (927 KB, 1481x1422) Image search: [Google]
1504749475657.png
927 KB, 1481x1422
>>
File: 1507870369568.jpg (156 KB, 1280x960) Image search: [Google]
1507870369568.jpg
156 KB, 1280x960
>>752396794
See: >>752396728

About 1.8 Terabytes
>>
File: 1390111788332.png (350 KB, 581x1000) Image search: [Google]
1390111788332.png
350 KB, 581x1000
>>
>>752396916
I saw. That's all deduplicated?
>>
File: 1390112213703.png (477 KB, 1200x886) Image search: [Google]
1390112213703.png
477 KB, 1200x886
>>
>>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 (1 MB, 1024x1020) Image search: [Google]
1390112913184.png
1 MB, 1024x1020
>>
File: 1390112949870.png (680 KB, 700x960) Image search: [Google]
1390112949870.png
680 KB, 700x960
>>
File: 1507871857272.png (629 KB, 695x900) Image search: [Google]
1507871857272.png
629 KB, 695x900
>>
File: 1390123990164.jpg (201 KB, 401x800) Image search: [Google]
1390123990164.jpg
201 KB, 401x800
>>
>>752396728
Doing gods work
When did you start downloading?
>>
File: 1390188094959.jpg (308 KB, 1200x1015) Image search: [Google]
1390188094959.jpg
308 KB, 1200x1015
>>
>>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 (1 MB, 932x1280) Image search: [Google]
1390193762127.jpg
1 MB, 932x1280
>>
File: tumblr_ozodb10ZCV1s01bj0o1_1280.png (326 KB, 1280x1404) Image search: [Google]
tumblr_ozodb10ZCV1s01bj0o1_1280.png
326 KB, 1280x1404
>>752395565
This is great art.
Requesting a character inviting anon on her lap.
>>
File: 1508308014026.jpg (357 KB, 848x1200) Image search: [Google]
1508308014026.jpg
357 KB, 848x1200
>>
File: 1390194060022.png (160 KB, 505x800) Image search: [Google]
1390194060022.png
160 KB, 505x800
>>
File: 1390194672976.png (125 KB, 334x486) Image search: [Google]
1390194672976.png
125 KB, 334x486
>>
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 (776 KB, 619x900) Image search: [Google]
1390194836931.png
776 KB, 619x900
>>
File: 1507875755970.png (456 KB, 1000x1294) Image search: [Google]
1507875755970.png
456 KB, 1000x1294
>>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 (1 MB, 1200x1000) Image search: [Google]
1390194878822.png
1 MB, 1200x1000
>>
File: tumblr_nv44lpSNtJ1ugw7cmo1_540.jpg (52 KB, 540x648) Image search: [Google]
tumblr_nv44lpSNtJ1ugw7cmo1_540.jpg
52 KB, 540x648
>>
File: 1390195019123.jpg (286 KB, 879x1171) Image search: [Google]
1390195019123.jpg
286 KB, 879x1171
>>
File: IMG_0802.jpg (288 KB, 1019x1723) Image search: [Google]
IMG_0802.jpg
288 KB, 1019x1723
ok so someone said this mare was urinating, I believe it to be arousal, whats your opinion?
>>
File: 1390195052485.jpg (132 KB, 800x660) Image search: [Google]
1390195052485.jpg
132 KB, 800x660
>>
File: 1390195085505.jpg (285 KB, 600x830) Image search: [Google]
1390195085505.jpg
285 KB, 600x830
>>
>>752397638

Water bender
>>
>>752397638
squash soup looks different than piss. That looks like piss.
>>
File: 1502192988212.gif (839 KB, 450x402) Image search: [Google]
1502192988212.gif
839 KB, 450x402
>>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 (1 MB, 989x1280) Image search: [Google]
1390195653918.png
1 MB, 989x1280
>>752397638
Considering that it's coming out in a stream just above her clit, definitely pee. Which is hot too.
>>
File: 1390195789081.png (285 KB, 700x700) Image search: [Google]
1390195789081.png
285 KB, 700x700
>>
>>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 (782 KB, 829x1099) Image search: [Google]
1390195965016.png
782 KB, 829x1099
>>752397905
>peeing so long as it's not on me
But that's the best part!
>>
File: 1390275292063.jpg (727 KB, 1280x953) Image search: [Google]
1390275292063.jpg
727 KB, 1280x953
>>
File: 1390275993627.jpg (415 KB, 900x675) Image search: [Google]
1390275993627.jpg
415 KB, 900x675
>>
File: 1390276349122.jpg (360 KB, 452x800) Image search: [Google]
1390276349122.jpg
360 KB, 452x800
>>
>>752397501
here she is, hope you like!
>>
File: 1507168028044.jpg (373 KB, 728x1000) Image search: [Google]
1507168028044.jpg
373 KB, 728x1000
>>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 (313 KB, 584x992) Image search: [Google]
1390276968552.jpg
313 KB, 584x992
>>
>>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 (2 MB, 960x1280) Image search: [Google]
1390282951930.png
2 MB, 960x1280
>>752398187
That's probably not pee, but that would be really hot.
>>
File: 1390620397659.jpg (340 KB, 530x793) Image search: [Google]
1390620397659.jpg
340 KB, 530x793
>>
File: 047 - fliKFQs.jpg (351 KB, 1920x1080) Image search: [Google]
047 - fliKFQs.jpg
351 KB, 1920x1080
>>752397952
That's not how those glasses work...
>>
File: 1390620937731.jpg (93 KB, 1280x1224) Image search: [Google]
1390620937731.jpg
93 KB, 1280x1224
>>
>>
File: 1390620954168.png (356 KB, 573x909) Image search: [Google]
1390620954168.png
356 KB, 573x909
>>752398370
Welcome to furry art.
Hey, Gears.
>>
File: 1390621686496.png (999 KB, 914x1588) Image search: [Google]
1390621686496.png
999 KB, 914x1588
>>
Hey degenerates, I have a question. Where do I find more fur porn? Specifically, cubs.

thanks
>>
File: 1390622528197.png (725 KB, 553x1280) Image search: [Google]
1390622528197.png
725 KB, 553x1280
>>
File: 1507841430.virate-chip_birdie.png (220 KB, 750x1140) Image search: [Google]
1507841430.virate-chip_birdie.png
220 KB, 750x1140
>>
File: g1.png (549 KB, 1200x1200) Image search: [Google]
g1.png
549 KB, 1200x1200
Anyone know how to contact the stairsync guy?
>>
>>752398494
e621.net
inkbunny.net
>>
File: 1390698899406.png (334 KB, 444x650) Image search: [Google]
1390698899406.png
334 KB, 444x650
>>
>>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 (303 KB, 750x975) Image search: [Google]
g2.png
303 KB, 750x975
>>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 (130 KB, 559x661) Image search: [Google]
1390700678953.jpg
130 KB, 559x661
>>
File: 1390706371226.jpg (606 KB, 800x1200) Image search: [Google]
1390706371226.jpg
606 KB, 800x1200
>>
File: 1502940474207.gif (863 KB, 500x500) Image search: [Google]
1502940474207.gif
863 KB, 500x500
>>752398548
>>752398402
PLS STOP
>>
File: 1390708690067.png (876 KB, 1500x953) Image search: [Google]
1390708690067.png
876 KB, 1500x953
>>
File: 058 - snUn5Dc.png (2 MB, 1586x892) Image search: [Google]
058 - snUn5Dc.png
2 MB, 1586x892
>>752398424
greetings
>>
File: 1390785360609.jpg (149 KB, 1500x1500) Image search: [Google]
1390785360609.jpg
149 KB, 1500x1500
>>
File: tumblr_ouwjzkmNi71slai5do1_1280.jpg (119 KB, 802x917) Image search: [Google]
tumblr_ouwjzkmNi71slai5do1_1280.jpg
119 KB, 802x917
>>752398713
no
>>
File: 1390788440575.jpg (129 KB, 867x1200) Image search: [Google]
1390788440575.jpg
129 KB, 867x1200
>>
File: 1510042982503.jpg (43 KB, 600x600) Image search: [Google]
1510042982503.jpg
43 KB, 600x600
>>752398838
pls stob
>>
File: 1390791005312.jpg (134 KB, 768x1280) Image search: [Google]
1390791005312.jpg
134 KB, 768x1280
>>
File: 1390795557799.jpg (750 KB, 800x1200) Image search: [Google]
1390795557799.jpg
750 KB, 800x1200
>>
File: 1390795894013.jpg (99 KB, 853x1280) Image search: [Google]
1390795894013.jpg
99 KB, 853x1280
>>
File: 1390802174019.jpg (407 KB, 668x1200) Image search: [Google]
1390802174019.jpg
407 KB, 668x1200
>>
File: 84568.jpg (197 KB, 1109x1194) Image search: [Google]
84568.jpg
197 KB, 1109x1194
>>752398891
she loves cock
>>
File: 1390802444439.jpg (676 KB, 1100x937) Image search: [Google]
1390802444439.jpg
676 KB, 1100x937
>>
File: 1505318136818.png (27 KB, 733x640) Image search: [Google]
1505318136818.png
27 KB, 733x640
>>752399086
NO SHE DOESNT
PLS NOE MORE
>>
File: 1390802479640.png (906 KB, 1056x900) Image search: [Google]
1390802479640.png
906 KB, 1056x900
>>
File: 1390802972464.png (2 MB, 1280x1280) Image search: [Google]
1390802972464.png
2 MB, 1280x1280
>>
>>752399178
>>
File: 1505163117514.jpg (46 KB, 480x480) Image search: [Google]
1505163117514.jpg
46 KB, 480x480
>>752399249
>>
File: 1390803219682.jpg (725 KB, 841x1111) Image search: [Google]
1390803219682.jpg
725 KB, 841x1111
>>
File: 1390803229595.jpg (168 KB, 905x1280) Image search: [Google]
1390803229595.jpg
168 KB, 905x1280
>>
File: 1390803283217.jpg (191 KB, 766x1280) Image search: [Google]
1390803283217.jpg
191 KB, 766x1280
>>
File: 1500757549916.jpg (122 KB, 826x1280) Image search: [Google]
1500757549916.jpg
122 KB, 826x1280
>>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 (247 KB, 900x675) Image search: [Google]
1390803324169.png
247 KB, 900x675
>>
File: 1511827116423.jpg (910 KB, 1310x1185) Image search: [Google]
1511827116423.jpg
910 KB, 1310x1185
>>
File: 1390803460434.jpg (167 KB, 639x762) Image search: [Google]
1390803460434.jpg
167 KB, 639x762
>>
File: 1503551089969.png (1 MB, 1280x1531) Image search: [Google]
1503551089969.png
1 MB, 1280x1531
Also, sorry for nerding up this thread.

Already bought Christmas presents?
>>
File: 1390803679053.jpg (100 KB, 942x1280) Image search: [Google]
1390803679053.jpg
100 KB, 942x1280
>>
File: 1503551448286.png (992 KB, 1280x1166) Image search: [Google]
1503551448286.png
992 KB, 1280x1166
>>752399485
what a bed wetter
>>
File: 1390803713800.jpg (197 KB, 754x1000) Image search: [Google]
1390803713800.jpg
197 KB, 754x1000
>>
File: 1390803957347.jpg (151 KB, 700x982) Image search: [Google]
1390803957347.jpg
151 KB, 700x982
>>
>>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 (66 KB, 453x1280) Image search: [Google]
1390804551944.jpg
66 KB, 453x1280
>>
File: 1390804699821.jpg (318 KB, 778x1000) Image search: [Google]
1390804699821.jpg
318 KB, 778x1000
>>
File: wew2.jpg (199 KB, 1164x1280) Image search: [Google]
wew2.jpg
199 KB, 1164x1280
>>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 (784 KB, 600x893) Image search: [Google]
1390804777758.jpg
784 KB, 600x893
>>
>>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 (719 KB, 695x1000) Image search: [Google]
1390804960972.png
719 KB, 695x1000
>>
File: 1390804961217.jpg (461 KB, 872x757) Image search: [Google]
1390804961217.jpg
461 KB, 872x757
>>
File: 1503553466828.jpg (428 KB, 1200x1175) Image search: [Google]
1503553466828.jpg
428 KB, 1200x1175
>>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 (137 KB, 544x661) Image search: [Google]
1390804995416.jpg
137 KB, 544x661
>>
File: 1390805027279.jpg (381 KB, 1210x725) Image search: [Google]
1390805027279.jpg
381 KB, 1210x725
>>
File: 1390805120315.png (1 MB, 900x934) Image search: [Google]
1390805120315.png
1 MB, 900x934
>>
>>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 (673 KB, 3000x2000) Image search: [Google]
1493485250356.jpg
673 KB, 3000x2000
>>752395565
>>
File: 1390805370712.png (774 KB, 700x906) Image search: [Google]
1390805370712.png
774 KB, 700x906
>>
File: 1390806040992.jpg (251 KB, 1100x747) Image search: [Google]
1390806040992.jpg
251 KB, 1100x747
>>
File: 1390806154693.jpg (347 KB, 600x800) Image search: [Google]
1390806154693.jpg
347 KB, 600x800
>>
File: 1503555104457.png (482 KB, 891x900) Image search: [Google]
1503555104457.png
482 KB, 891x900
>>
File: 1390806227742.png (726 KB, 1000x1000) Image search: [Google]
1390806227742.png
726 KB, 1000x1000
>>
File: 1390862121043.jpg (127 KB, 1280x853) Image search: [Google]
1390862121043.jpg
127 KB, 1280x853
>>
File: cat1.jpg (112 KB, 758x517) Image search: [Google]
cat1.jpg
112 KB, 758x517
>>
File: 1390862155435.jpg (148 KB, 1280x853) Image search: [Google]
1390862155435.jpg
148 KB, 1280x853
>>
File: 1390862309153.png (723 KB, 1000x863) Image search: [Google]
1390862309153.png
723 KB, 1000x863
>>
File: 1390862446638.png (380 KB, 850x617) Image search: [Google]
1390862446638.png
380 KB, 850x617
>>
File: 1390862556496.jpg (196 KB, 1000x1200) Image search: [Google]
1390862556496.jpg
196 KB, 1000x1200
>>
File: 1390863012844.png (354 KB, 600x999) Image search: [Google]
1390863012844.png
354 KB, 600x999
>>
File: 1390863566493.jpg (319 KB, 1280x932) Image search: [Google]
1390863566493.jpg
319 KB, 1280x932
>>
File: 1390864001551.jpg (140 KB, 592x821) Image search: [Google]
1390864001551.jpg
140 KB, 592x821
>>
File: 1390884380524.jpg (311 KB, 965x800) Image search: [Google]
1390884380524.jpg
311 KB, 965x800
Night.
>>
File: b2.png (486 KB, 1200x1000) Image search: [Google]
b2.png
486 KB, 1200x1000
>>752400671
Night, Dash.
>>
File: 1508925387643.jpg (2 MB, 2361x3056) Image search: [Google]
1508925387643.jpg
2 MB, 2361x3056
>>
File: 1501393281919.jpg (2 MB, 2361x3056) Image search: [Google]
1501393281919.jpg
2 MB, 2361x3056
>>
File: 1494861863958.jpg (476 KB, 1233x2027) Image search: [Google]
1494861863958.jpg
476 KB, 1233x2027
>>
File: 1482904348813.jpg (368 KB, 1233x2027) Image search: [Google]
1482904348813.jpg
368 KB, 1233x2027
>>
File: 1500789616782.jpg (429 KB, 1233x2027) Image search: [Google]
1500789616782.jpg
429 KB, 1233x2027
>>
File: 1488230070183.jpg (429 KB, 1233x2027) Image search: [Google]
1488230070183.jpg
429 KB, 1233x2027
>>
File: 1486122345646.jpg (373 KB, 1233x2027) Image search: [Google]
1486122345646.jpg
373 KB, 1233x2027
>>
File: 1495494296803.jpg (290 KB, 1233x2027) Image search: [Google]
1495494296803.jpg
290 KB, 1233x2027
>>
File: 1501797893613.jpg (435 KB, 1233x2027) Image search: [Google]
1501797893613.jpg
435 KB, 1233x2027
>>
File: 1482202789254.jpg (337 KB, 1233x2027) Image search: [Google]
1482202789254.jpg
337 KB, 1233x2027
>>
File: 1493553840176.jpg (369 KB, 1233x2027) Image search: [Google]
1493553840176.jpg
369 KB, 1233x2027
>>
File: 1487608912388.jpg (389 KB, 1233x2027) Image search: [Google]
1487608912388.jpg
389 KB, 1233x2027
>>
File: 1507915680217.jpg (362 KB, 1233x2027) Image search: [Google]
1507915680217.jpg
362 KB, 1233x2027
>>
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 [Archive] | Search | [Home]
Navigation: /b/ - Random [Archive] | Search | [Home]


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 Bitcoins at 1516QPvvjaBRziqhWPPJLvTaYxfUSBJswe
All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.
This is a 4chan archive - all of the content originated from that site. This means that RandomArchive shows their content, archived. If you need information for a Poster - contact them.