Page 6 of 22
Re: Catagolue Discussion Thread
Posted: January 14th, 2019, 8:52 pm
by 77topaz
benetnasch85 wrote:We have encountered server errors for more than 7 hours. Catagolue pages that do not need server data are displaying OK.
Yes, the server is currently over quota, as was pointed out in the thread
specifically about Catagolue outages.
Re: Catagolue Discussion Thread
Posted: January 14th, 2019, 9:59 pm
by dani
Saka, can you add the following to the main post:
Catagolue resets every 07:00 AM UTC.
It's 2 AM in my timezone and 2 PM in yours. c:
Re: Catagolue Discussion Thread
Posted: January 15th, 2019, 5:54 am
by Saka
danny wrote:Saka, can you add the following to the main post:
Catagolue resets every 07:00 AM UTC.
It's 2 AM in my timezone and 2 PM in yours. c:
done
Re: Catagolue Discussion Thread
Posted: January 16th, 2019, 4:43 am
by muzik
Will any of the non-outer-totalistic, non-isotropic-nontotalistic rules ever get animated pattern thumbnails?
Re: Catagolue Discussion Thread
Posted: January 17th, 2019, 2:31 pm
by muzik
Am I the only one who experiences intense lag on pages such as the following?:
https://catagolue.appspot.com/census/b3s23/stdin/xq6
Re: Catagolue Discussion Thread
Posted: January 17th, 2019, 7:22 pm
by 77topaz
No, it lags for me too. It's because the page has numerous GIFs of very large spaceships.
Re: Catagolue Discussion Thread
Posted: January 20th, 2019, 8:58 am
by muzik
Why doesn't Catagolue open LifeViewer for Generations patterns with more than one cell state present?
https://catagolue.appspot.com/object/xp ... s/g17b3s23
Re: Catagolue Discussion Thread
Posted: January 20th, 2019, 9:11 am
by calcyman
Extreme laziness on my part. The apgcode-to-RLE conversion is actually achieved by appropriating part of Chris Cain's glider synthesis javascript (and therefore happens client-side rather than server-side), and as far as I know is limited to 2-state patterns.
Re: Catagolue Discussion Thread
Posted: January 20th, 2019, 12:51 pm
by tod222
What do the colors signify in the root column on the haul pages?
Re: Catagolue Discussion Thread
Posted: January 20th, 2019, 7:15 pm
by 77topaz
tod222 wrote:What do the colors signify in the root column on the haul pages?
Brown = newly uploaded, not yet processed
Colours between brown and green = various stages in the verification/committing process
Green = this haul has been committed to the census
Red = this haul failed a statistical test, it is not included in the census
Blue = this haul contains something special, it is being permanently preserved (green hauls are deleted after a while)
Re: Catagolue Discussion Thread
Posted: January 24th, 2019, 1:09 pm
by muzik
Will we ever be able to do more with accounts on catagolue? e.g. deleting own comments, moderating comments, assigning payosha256 keys to our accounts
Re: Catagolue Discussion Thread
Posted: January 24th, 2019, 5:58 pm
by testitemqlstudop
Methuselahs! Methuselahs everywhere!
https://catagolue.appspot.com/census/b3 ... methuselah
https://catagolue.appspot.com/haul/b3s2 ... 4f411a0c33
I hacked apgsearch to only log methuselahs and also detail their complete lifespan. Hopefully calcyman's fine with this...
Re: Catagolue Discussion Thread
Posted: January 24th, 2019, 7:49 pm
by dani
You're using the wrong notation, it should be along the lines of '30k'
Re: Catagolue Discussion Thread
Posted: January 24th, 2019, 8:30 pm
by 77topaz
Did you really need to post that exact same message in two different threads? Anyway, here's an echo of my response in the other thread:
77topaz wrote:testitemqlstudop wrote:I hacked apgsearch to only log methuselahs and also detail their complete lifespan. Hopefully calcyman's fine with this...
That's a clever idea. Because it's
only storing the methuselah objects, it shouldn't cause any excessive strain on the server, so I don't expect calcyman would have a problem with it.
And also...
danny wrote:You're using the wrong notation, it should be along the lines of '30k'
testitem is
deliberately using a notation that logs the precise lifespan instead of the abbreviated form. Since it's in an unofficial symmetry, I don't see a problem with it.
Re: Catagolue Discussion Thread
Posted: January 24th, 2019, 9:13 pm
by dani
ah, thought he was using C1..
Re: Catagolue Discussion Thread
Posted: January 25th, 2019, 8:12 am
by 72c20e
Unavailable in China. Any mirrors?
Re: Catagolue Discussion Thread
Posted: January 25th, 2019, 8:17 am
by Bullet51
[deleted]
Re: Catagolue Discussion Thread
Posted: January 25th, 2019, 8:20 am
by muzik
72c20e wrote:Unavailable in China. Any mirrors?
http://gol.hatsya.co.uk/home
Re: Catagolue Discussion Thread
Posted: January 25th, 2019, 2:09 pm
by muzik
Currently Catagolue attempts to run custom ruletable rules with LifeViewer:
https://catagolue.appspot.com/object/xq ... xbzerotest
Since LifeViewer has been confirmed to not be supporting custom ruletables at any point in the near future, can these object pages be made to not bring up a LifeViewer applet if a custom ruletable is being used, and display a static image instead?
Re: Catagolue Discussion Thread
Posted: January 26th, 2019, 6:05 am
by 77topaz
Hmm... Lifelib
can support these ruletables - is there any way that could be used to create a similar viewport for those patterns?
Re: Catagolue Discussion Thread
Posted: February 1st, 2019, 4:31 pm
by testitemqlstudop
Re: Catagolue Discussion Thread
Posted: February 1st, 2019, 4:41 pm
by Moosey
What is the problem, exactly?
Re: Catagolue Discussion Thread
Posted: February 1st, 2019, 5:12 pm
by testitemqlstudop
Moosey wrote:
What is the problem, exactly?
They're red (i.e. invalid):
https://catagolue.appspot.com/haul/b3s2 ... emqlstudop
Re: Catagolue Discussion Thread
Posted: February 1st, 2019, 5:47 pm
by calcyman
Erm, how were you testing it? Hauls shouldn't be that small, firstly. Secondly, it's in no way release-worthy, and there's no public blockchain yet.
Re: Catagolue Discussion Thread
Posted: February 1st, 2019, 7:46 pm
by testitemqlstudop
calcyman wrote:
Erm, how were you testing it? Hauls shouldn't be that small, firstly. Secondly, it's in no way release-worthy, and there's no public blockchain yet.
Well, I lowered MIN_LOG_DIFFICULTY ("#define MIN_LOG_DIFFICULTY 0x407a400000000000ull") to 0x407a40000000000ull (one less zero) for two reasons:
1. my 4-core i5 computer would not mine a block for several hours;
2. I wanted to see if the difficulty could adjust it back to a reasonable amount of time.
In short, the answer to (2) was no; hauls were being uploaded twice (or even more) every minute, and the difficulty would not rise exponentially, but instead linearly. I stopped after about an hour after 100 or so hauls to not put excessive server strain. I'm thinking of replacing the difficulty function that directly limits increase with a function that just goes halfway to the normal expected difficulty (i.e. replace line 86 and afterwords of blockheader.h with
Code: Select all
// We update the difficulty to target a 10-minute block time:
int64_t actual_time = ((int64_t) (t - prevblock.prevblock_time));
int64_t desired_time = 600000000000ll;
int64_t earlyness = desired_time - actual_time;
uint64_t next_log_difficulty = prevblock.log_difficulty + earlyness * 32;
log_difficulty = (log_difficulty+next_log_difficulty)/2;
if (log_difficulty < MIN_LOG_DIFFICULTY) {
log_difficulty = MIN_LOG_DIFFICULTY;
}
I'm trying to implement an HTTP-like protocol that allows the communication of miners. I think if each node can have a port (say 6333) linked to an HTTP server and there are two endpoints "blocks" and "block*****", each node could just query each of the nodes that it's connected to with "blocks", and if the node's local copy is behind, query each "block*****", adding it to its local chain, until it is up-to-date.
EDIT: When there's transaction support there could just be a "txpool" endpoint that gives the entire current state of the unconfirmed transactions, but given the current state of Lifecoin, ...