~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@not_bob_afk
@orignal
@postman
@zzz
%acetone
%cumlord
+FreefallHeavens
+Xeha
+ardu
+bak83_
+profetikla
+qend-irc2p
+r00tobo_BNC
+uop23ip
+weko
AHON1
Arch
BubbRubb
Danny
DeltaOreo
FreeRider
Irc2PGuest24776
Irc2PGuest63604
Irc2PGuest70891
Irc2PGuest84450
Irc2PGuest86877
Irc2PGuest87993
Leopold_
Meow
Onn4l7h
Onn4|7h
T3s|4__
anontor
boonst
duck
evasiveStillness
hk
maylay
onon_1
pisslord
poriori_
shiver_
simprelay
solidx66
thetia
u5657
usr001
zer0bitz_
RN
dungeon master is coming? oh dear?!
orignal
running now
orignal
2RRY with new family signing code
orignal
and found the issue with openssl
orignal
somethimes they return -1
orignal
was able to connect to stats.i2p with 6
zzz
great. I just submitted my final ratchet PR
orignal
when are you ready to test transports?
zzz
2 months?
zzz
havent started yet...
orignal
asking you
zzz
6-8 weeks maybe
zzz
shouldn't be too hard, just a lot of stuff ahead of it on the list
orignal
fine
orignal
seems no issue with 2RRY so far
orignal
it gets honoured at all my nodes
StormyCloud
Hypothetically, if someone wanted a domain that has already been registered but has never been used, what would they need to do? zzz orignal
not_bob
I can't speak for them, but on my end if it's never active, then my hosts.txt won't have it in there.
not_bob
But, just the act of having it registerd will tie the b32 to that domain.
not_bob_afk
I know that reg.i2p does auto-expire domains that don't get used in a long time.
RN
not that long; not long enough
not_bob_afk
This topic is a point of disagreement.
StormyCloud
reg is showing its never been active so looks like someone registered it but never got around to their page/project
not_bob_afk
What's the domain?
StormyCloud
DM coming
T3s|4
StormyCloud: not sure in this case, but I'd be asking myself: it is more efficient to create a new site registration vs. attempting to re-awaken a registered but never used site?
StormyCloud
Well would think its simple enough to drop the dead site out of the current registries. Ultimately if its going to be a big hassle Ill move onto the creating a new site
RN
dropping it from current registries, if that was supported, would not remove it from end user netdb
RN
so anyone that had got it from their subscriptions would not easily get your new one
zzz
correct
RN
the expiration issue is borne of the concept of anyone or group can create and share their own subscription links privately or publicly, which was an intentional design choice
RN
so that issue asside... might be better/easier to think of a new url
RN
unless they registered *stormycloud* in which case you MIGHT make a case with the existing registrars to have it manually removed
StormyCloud
sounds good