Anonymous ID: 842ee4 Feb. 15, 2020, 7:30 p.m. No.8151103   🗄️.is 🔗kun   >>1120

>>8151027

Here, I gibberished up your gibberish for you.

 

Timelines us to humans so much it layed is is back of you are timeline can mean a timelines can you right based on why it all leads you wasted on unknown but in then here and out you wasted out invaluable through thing we are end to humans so much to even hered on a slight based to the galaxy here everything at brings mean mean you right grip on unfathomable the sun but in front the to humans so much to the galaxy hered out of time beginning as to desting we are timelines are is no such to humans so

Anonymous ID: 842ee4 Feb. 15, 2020, 7:32 p.m. No.8151122   🗄️.is 🔗kun

>>8150956

Is the end user in control of encryption, or is the data to be held in cleartext on the Google servers?

 

Relevant point, needs to be addressed in evaluating this

Anonymous ID: 842ee4 Feb. 15, 2020, 7:35 p.m. No.8151142   🗄️.is 🔗kun   >>1154 >>1185 >>1285 >>1303

>>8151091

I've explained this repeatedly to dayshift.

There could be errored copies of the site's javascript (prior to the fix) in your browser's local web cache, or in intermediate web caches within your ISP's network.

To pull the corrected JS from 8kun's servers you need to:

1) Clear your web cache and cookies for 8kun

2) Restart your browser

3) If site is still funky, use CTRL-F5 or forced refresh to tell your browser to pull the HTML and all ancillary files from the host bypassing copies that may be in web caches.

 

Fixed the problem for most dayshift users. They stopped complaining after I told them what to do.

It should not be necessary to change browsers.