[tor-relays] Relay JPsi2 not getting into consensus anymore

[Random Tor Node Operator]

On 10/12/20 12:55 PM, William Kane wrote:
>> The provider said it was due to Spectre mitigations and the only way for me
> to fix this would be to switch to a newer (more expensive) plan...
> 
> What?
> 
> Your provider lied to you / scammed you, Spectre/Meltdown etc.
> mitigations have nothing to do with applications freezing or having to
> get a faster downstream/upstream speed.. at worst there's a 5-10%
> performance hit if you don't have the newest CPU microcode installed
> and an OS that makes use of the new insturctions (use the latest linux
> kernel and intel-ucode if you can).

It is possible that the provider wasn't fully honest in their
statements. I have never experienced any instabilities due to CPU bug
mitigations in any other machine, bare metal or VM.

But that isn't the issue.

The situation of my relay hasn't changed. It still isn't in the consensus.
If it is caused by something on my side, I'd like to fix it sooner
rather than later.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20201013/19faa1ba/attachment-0001.sig>