Anonymous ID: d11628 Feb. 5, 2020, 1:36 p.m. No.8039924   🗄️.is 🔗kun   >>0029

>>8038621

CM seems to have changed some things in the page's source.

Occasionally there's also some dns-guard script in there.

So as long as my weblink isn't spoofed changes are caused on CM's/websource's side.

The most significant changes are that the unixtime now is

<time unixtime=[xxxx]

when before it was

<time unixtime="[xxxx]".

Btw, all class-parameters (also class=poster_id, class=fileinfo, class=post_no etc) now come w/o quotes, when before they were all in quotes (i.e. class="poster_id", class="fileinfo", class="post_no" etc).

 

When using savepage_we, they are still in quotes, but when using firefox's "save page as" or wget they are all w/o quotes (likely with other browsers as well).

This has been like that before, but only for a coupe of breads before it had been corrected.

I don't know if this is an error or a new format of the 8kun-source. So, for now, I'm observing things before making changes to the source code.

QCV is hard-coded to look for the old format (i.e. with quotes). This is what most likely causes your seg-fault/core dump.

Apologies for that – don't know what CM is doing in the background and why this is changing. Will adapt the code if it persists …..

The 3-timezone html is up to date. I'm using this for now.

Anonymous ID: d11628 Feb. 5, 2020, 1:59 p.m. No.8040422   🗄️.is 🔗kun   >>2020

>>8040029

Unlikely CM is reading the clock thread, but just in case I'm the only one observing these changes, and because nobody mentioned it in the General yet, I thought I'd better explain what I've observed.

Doesn't help you much, I know, sorry. Please for now try using the 3-TZ html (HTMLonly version if you have all the images). Thanks.

 

>>8015835

>illustrate/highlight the years

Thought about this before, but dismissed it back then.

Highlighting/painting fields was "too much of color" for me (i.e. distracting from other info/highlights).

Will think about it – maybe I could draw the thin black spiral line in different colors acc. to years … Would that do the job?

Anonymous ID: d11628 Feb. 11, 2020, 7:03 p.m. No.8109008   🗄️.is 🔗kun   >>2037 >>3765

>>8103207

I've tried a lot of things today. Changed the color of dots, changed the color of lines, letters and whatnot.

It all looks weird in a four colored blank, that's meant to be a template for clockfags making connections to tweets/news etc.

 

Tbh, one cannot be a clockfag w/o knowing when Q started posting. Years easily emerge in the clock from the change from 12/31 (higher numbers) to 01/01 (lower numbers).

So having thought about that previously (and discarded the idea), I still don't see much use in marking years in some way.

Maybe there's arguments that can convince me (all clockfags, feel free to chime in) – currently I'm certainly not.

(images are examples)

Anonymous ID: d11628 Feb. 16, 2020, 9:04 a.m. No.8155067   🗄️.is 🔗kun

>>8137731

>Maybe this issue will become clearer when Q posts a new image?

It's still the same cause (missing quotes in HTML source format).

There was a parameter (original filename of image) that was not being corrected when updating. Hope in the current version on mega.nz the problem is fixed.

Anonymous ID: d11628 Feb. 22, 2020, 5:41 p.m. No.8221345   🗄️.is 🔗kun   >>1501

>>8205986

Have thought about a 24hr clock more than once previously. 11/3 would be 17:42. We're at 13:27 today.

As long as 60 mins correspond to 360 deg around the clock, and because we still go with 1min per day the 12hr display almost does the same job, I believe.

Grown up with military time (24hrs), I never had a problem to remember if the current time on a 12hr-clock shows a.m or p.m. So for me it's really almost the same.

The way you thought about it, what do you think would change with a 24-hr clock?

Anonymous ID: d11628 March 3, 2020, 7:03 a.m. No.8307825   🗄️.is 🔗kun

>>8303374

>>8303305

Indeed, some time ago there was the idea to let the clock start from 10/05/17, that day when POTUS mentioned "the calm before the storm" (pic).

At some later point, I reverted the clocks back to starting from 10/28.

However, the anon >>8296108 must have drawn dates & spiral by himself since I never made a clock until 09/21/20, and font is different as well.

It doesn't matter much though for the distribution of primes around the clock, as it results from the maths and what dates/days are at [0] position. There's a related prime sieving technique (Sieve of Atkin) using modulo-60 math.

I think I've drawn such a clock previously (first clock bread), with dates that are a prime number of days away from the start date drawn in red.

 

>>8296108

Thanks for that clock. Would have three questions though:

Why are some dates marked yellow as well, when otherwise only prime numbers are written in yellow above dates?

Why is 12/17 (800th day) marked red?

Why did you stop at 09/21/20, but marked 11/11/20 specifically?