al. zone walk ?

[uggyuggy]

Hi,

I noticed it looks al. seems now walkable... (I think it was not until now)

$ wc -l zonewalk.al
32457 zonewalk.al
$ 
$ shuf -n 10 zonewalk.al | awk '{print $1}'
vzu.al.
packeta.al.
area-real-estate.al.
albakredit.al.
radioshqiptare.al.
kushot.al.
webmarket.al.
elitepalace.al.
lenteoptike.al.
beldent.al.

Do you plan to possibly add it into walks_lists/?

[monoidic]

This was automatically picked up a few hours after you opened the issue, and the file has been getting one or two updates per day since then.
It manages to pick up things like that on its own, thankfully, without my input.
Closing the issue as everything's working ~as expected.

[uggyuggy]

Hi @monoidic ,

Perfect, I can see it now..

Noted for the automatic pick up 👍
Great work

Thank you

[uggyuggy]

Hi @monoidic

Noticed the .al has not been updated over the last month.
(Commit 3a98715 on Jul 3)

It looks that the zone walking is still available on the registry side.

I'm wondering if I'm missing something ? or what is the "update" frequency you use.. ?
thx

[monoidic]

Hi @monoidic

Noticed the .al has not been updated over the last month. (Commit 3a98715 on Jul 3)

It looks that the zone walking is still available on the registry side.

I'm wondering if I'm missing something ? or what is the "update" frequency you use.. ? thx

The update frequency should be ~hourly, via Github-run workers. In reality, it seems to get throttled to effectively once every 2 hours or so?

Though every one of those attempts only walks a randomly selected collection of 255 walkable zones from the list of all that are available, due to a Github actions limit.

Aside from that, my experiment with walking rDNS zones (in-addr.arpa./ip6.arpa.) in addition to TLDs seems to be slowing down TLD zone walk frequency, since they're taking up some of those limited 255 hourly slots.

I am not sure why it's been a full month, but I'm guessing it's all those factors described above acting together.
Perhaps 1) more priority should be given to non-rDNS zones, and 2) more priority should be given to new zones + zones that have been walked less recently.
I will try to look into something for this soon.

Though, if the al. zone is of particular interest to you, then you could also perform the walks yourself rather than waiting on this repository.

[uggyuggy]

Hi,

Thank's for the details about the update cycle.

I agree with your proposals. I think too more priority should be given to non-rDNS zones (like rDNS get only 1 hourly slots per day), and zones that have been walked less recently.
In addition, may be bigger (non-rDNS) zone could have higher priority too.

I'm not interested in particular to .al zone. That's just a recent example that triggered my attention.

Thx