@evelyn @yes It's a fair point.

@yes
Who determine what is #malware and what is a useful service?

Another theme that keeps popping up is ppl on Fedi using (#)GriftHub.

Also as s part of a holistic movement towards #censorshipResistance, all instances should strive to federate over Tor or I2P.

We posit that federation over #I2P should be default because Tor don't like lots of traffic (eg. they don't recommend torrenting over Tor etc).

@hugo @evelyn

@dsfgs @hugo @evelyn i2p is too slow, use lokinet, https://lokinet.io/ it was made by an i2pd contributor.

@yes
Hi Nanachi,

I2P is fast a lot of the time. This is why bitcoin and torrenting is using I2P and why we think its perfect for Fedi. Fediverse really doesn't even need to be blindingly fast anyway, but it will likely be somewhat fast.

@hugo @evelyn

yea hi,

i2p is "fast" (50kbps per connection absolute max) yes, but suffers from bottlenecks, the scaling factors in i2p are relatively dismal. they have done a great job removing one shot elgamal from the protocol but the real issue is i2p integration is more invasive vs even .onion, lokinet uses dns as its primary "api" and as long as your resolver settings are set zero modifications are required to use it. i cannot suggest people suffer the pains of setting up i2p or onion connectivity when lokinet is a thing. but that it just me.

you are right, fedi does not need to be fast , it needs to be easy. lokinet seems so much better on that front vs everyone else.

one of the most useful things lokinet brings is hybrid mode on mainline fedi, if you have a clearnet domain you can still talk to .loki without needing a .loki domain, you just need lokinet dns on your instance, on the other end for .loki only they just need to pick an exit node for outbound federation to clearnet instances with lokinet dns. all of it turnkey, no mods required in any of fedi's stack. much easier to gain network effect with that vs everything else.