Anonymous ID: e5f52e July 17, 2019, 1:44 p.m. No.15649   🗄️.is 🔗kun   >>5675 >>5707

>>15558

 

>>15547

>>15385

>>15532

 

> I have this JS (customized to have no color for my and Q's posts, and no nope buttom; for caps).

 

https://pastebin.com/Jh4Mqwpj

 

> It doesn't let me make new threads from the catalog and only the index. Any idea why that'd be?

 

I suspect that your runq() may be recursive.

 

have you instrumented any part with console.log()

Anonymous ID: e5f52e July 17, 2019, 1:55 p.m. No.15708   🗄️.is 🔗kun   >>5769

>>15675

 

heh.

 

in previous life, wrote linux kernel code, js is pretty much out of the wheelhouse.

 

but, code is code, once you understand the underlying engine, and the syntax, everything is possible.

 

I would suggest wrapping the whole thing in the test like I did, the

 

if (window.location.pathname.search("/catalog") == -1) {

... your code goes here

}

 

should turn off anything you are doing when on the catalog.

Anonymous ID: e5f52e July 17, 2019, 1:59 p.m. No.15723   🗄️.is 🔗kun   >>5740

>>15695

 

localstorage includes the imageBlacklist, or whatever it's called. so when you download "localstoage" whatever is in there comes along for free.

Anonymous ID: e5f52e July 17, 2019, 2:19 p.m. No.15811   🗄️.is 🔗kun   >>5871

>>15795

 

it's the array of the image id's. technically, it's the id of the thumbnails, but they match the main images, just different path, /file_store/ v. /thumb/ or something.

Anonymous ID: e5f52e July 17, 2019, 2:47 p.m. No.15918   🗄️.is 🔗kun   >>5995

>>15871

 

yeah, saving to your system doesn't actually change anything about it, and at some point, it will get full. current understanding is the limit is 5meg. in my case, whacking porn and cp with the nope button stops me from accidentally downloading those when I download the bread. in my case the list is only a few 100k. each file id is 64 bytes.

 

I have some code that when saving images looks to see if the image was seen before. if it was, don't download as it's already here.

Anonymous ID: e5f52e July 17, 2019, 7:11 p.m. No.17013   🗄️.is 🔗kun   >>8364 >>9809

>>16158

 

look into the code for qanon.pub, they have done that heavy lifting, it would prob be easier to port.

 

qrb-bells-whistles is targeted at general viewing of Q boards, with some visual enhancements. my work is top of someone else's work.

Anonymous ID: e5f52e July 22, 2019, 4:50 p.m. No.25186   🗄️.is 🔗kun

>>25032

>>25032

 

correct. the items in the array are ids of the image id as stored both as the main image, and the thumbnail, although in different paths.

 

this is useful to see if you have downloaded the image before if you grab the main link, rather than the second one, which is the name of the uploaded file from the anon's system.

Anonymous ID: e5f52e July 23, 2019, 6:26 p.m. No.26281   🗄️.is 🔗kun

2019-07-24

 

Updated user.js qrb-bells-whistles.

 

Rename the "Spam Free Bread" toggle button in the header "Spam Fader".

 

Source:

https://pastebin.com/2We1Nc2p

 

Compressed:

https://pastebin.com/jt1WN9pv

 

$ sha256sum qrb-bells-whistles.js.txt qrb-bells-whistles-190724-0112Z.min

e1da173ca0c40e6c70662b88f23c1a3bd074faf8d879eff850b1907ac9172424 qrb-bells-whistles.js.txt

c92a0c9c2a12103050a116742da6610397a235f86e27ffc03a5601b00d96988e qrb-bells-whistles-190724-0112Z.min

Anonymous ID: e5f52e July 26, 2019, 2:40 a.m. No.28768   🗄️.is 🔗kun   >>9073

>>15636

 

2019-07-26

 

Updated user.js qrb-bells-whistles.

 

The ordering and display of the toasts, and the post count have been

moved to align on the right side of the window, with the post count

stuck to the bottom right corner of the window. No image size changes

were made, just where the display is presented.

 

The net effect is that everything now lines up vertically on the

right edge, versus blocks floating on the upper right at the top.

 

$ sha256sum qrb-bells-whistles.js.txt qrb-bells-whistles-190726-0900Z.min

f68666c3eaf4f535a77103fdf2c76325b26aae43b81fc293783f6a5d1e784779 qrb-bells-whistles.js.txt

85fe05650d9b25ff9df9a4e08958f64cd3646f3ca245f6b12dc88f4f134a858e qrb-bells-whistles-190726-0900Z.min

 

Compressed:

https://pastebin.com/KJdiAHhC

 

Source:

https://pastebin.com/EjGtyX9z

Anonymous ID: e5f52e July 26, 2019, 12:01 p.m. No.29073   🗄️.is 🔗kun

>>28768

 

2019-07-26-2

 

MOAR

 

qrb-bells-whistles.js: adjust the horizontal position of the toasts

 

The previous positioning had it slightly overlapping the post.

 

anon is always confused, are you sposed to measure once, cut twice, or measure twice and cut once?

 

whatever, have tested on both dissenter (chrome) and firefox, and the toasts no longer overlap.

 

$ sha256sum qrb-bells-whistles.js.txt qrb-bells-whistles-190726-1817Z.min

a51d95e9d837c6bf804320a2ff52f207d71554542f4463c7e311332f2734cc1b qrb-bells-whistles.js.txt

98a7a4930087c0723181e6182e86bb7a6789a7533c0db338e4a0f0a0e1b57b62 qrb-bells-whistles-190726-1817Z.min

 

Compressed:

https://pastebin.com/5jXy0VjE

 

Source:

https://pastebin.com/41SH6xkN

Anonymous ID: e5f52e July 26, 2019, 12:13 p.m. No.29093   🗄️.is 🔗kun   >>4908

>>28894

 

yeah, in the user.js, see the nopeSI:0, in the first block,

 

  • change the 0 to 1 without touching either the ':' or the ','.

  • save the user.js,

  • and you should be in bidness.

Anonymous ID: e5f52e July 31, 2019, 7:50 a.m. No.33828   🗄️.is 🔗kun   >>3842 >>5009

>>15636

2019-07-31

 

FREASHA TOASTA ONA CONVEYOR, SIGNOR

 

Was proud of meself for moving the breads all over to the edge of screen, aligned vertically. Looks good methinks. Goes away for a few hours, comes back, and toasts have spilled all over.

 

Turns out, there was at least one bug in the code that kept up with them, basically, nothing was timing out and leaving the list, the list continued to grow until you refreshed or changed breads.

 

When a new bread showed up, the toast was appended to the list, at the end, so that made it hard to determine which was the newest, you had to look at the color. I know, not that hard, but when a couple were not adjacent, it was easy to poke the wrong one.

 

Now, the list is actually timing out, with burnt ones getting tossed. To me though, the big deal is that the new toast is added to the top of the list. This allows you easily judge by the color gradations who is newer, at least I am able to compare visually as they are ordered in descending burntness.

 

The other bug that I think was present was that a variable was being use that was defined once when the new bread was opened, then a callback was called that used the same name but never initialized it, so may have be reusing the global var that was essentially static.

 

What I had noticed previously was when moving the sprite over the Q posts at the top of the bread, or even the notable was cause the parser to freak, and all the posts would disappear, only to come back with a refresh/reload. Not sure about this one, as it may have been fixed in the browser.

 

New Tuning Knobs

 

toastQuantum: 7200, // 2 hours. NB: Date().getTime() is milliseconds

toastThrottle: 3, // allow non qresearch board to run 3x longer before timing out.

 

When not on /qresearch, bump the toastQuantum to 6 hours to prevent losing older breads. You can change the multiplier in toastThrottle.

 

maxToasts: 13, // set this to prevent more toast display than screen real estate.

 

I have a desktop, so just picked 13 as the max to display. If you can adjust ilower if they still spill over. I don't plan on coding up a way to autocalc how much real estate is available.

 

$ sha256sum qrb-bells-whistles-190731-1433Z.js.txt qrb-bells-whistles-190731-1433Z.min

7b9d9123d65c292539ffa88ba567912963a7e6177ee31d0bebbc2ddec9c1d684 qrb-bells-whistles-190731-1433Z.js.txt

ebc828c7f72f211a630d0b386d7a6fae7f0e100dc98e8aae8076c741092edda6 qrb-bells-whistles-190731-1433Z.min

 

Compressed:

 

https://pastebin.com/jYj3kpyb

 

Source:

 

https://pastebin.com/zfK7QkGc