Audrius Butkevicius
Audrius Butkevicius
I suggest that these should be generated from proto, in case they ever need to go on the wire.
Tbh, I think its fair game to move all events into proto/lib/events and wherever they are initialized use them from the generated package. There is zero reason why other packages...
I think it's fine to move whatever the packages embed internally to a proto package.
> > I think it's fine to move whatever the packages embed internally to a proto package. > > Do you mean that any code using these previously internal types...
The stuff you pass to .translate are technically keys, so we can just make the keys resolve to d/m/h in the english translation.
However, this would be a first and potentially confusing.
In general, this seems to me like this is fairly error prone (ie, some permissions issue will make this hang forever etc). Personally, I am not sure if this should...
In general, the tool is aimed at individuals, that are unlikely to ever need to run their own discovery servers. If you do choose to run it, then there are...
There already exists a way, it's just not what addresses get announced, but which addresses get tried when connecting. Use that.
Are we planning to do something about this? To me it seems all the required facilities (i.e. configuring device addresses) are already there, so I don't think there is anything...