plantteacher

@plantteacher@mander.xyz

• ⁨Comment⁩ on ⁨Long load times again⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  So, the server that hosts the front-end via Tor will see the exit node connecting to it

  The onion eliminates the use of exit nodes. But I know what you mean.

  I appreciate the explanation. It sounds like replicating the backend and DB on the Tor node would help. Not sure how complex it would be to have the DBs synchronise during idle moments.

  Perhaps a bit radical, but I wonder if it would be interesting to do a nightly DB export to JSON or CSV files. Scrapers would prefer that, and it would be less intrusive on the website. Though I don’t know how tricky it would be to exclude non-public data from the dataset.

• ⁨Comment⁩ on ⁨Should I create a psychology community, or take over moderation of psy?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  psy is on /this/ instance. Note my question was directed to the mander admins, who would only have the power to make me a mod on the node under their control.

• Should I create a psychology community, or take over moderation of psy?
  Submitted ⁨⁨2⁩ ⁨weeks⁩ ago⁩ to ⁨mander@mander.xyz⁩ | ⁨2⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨Long load times again⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  I’ve not tried the onion instance since reporting the data loss issue, but in principle a the onion host could be a good candidate for read-only access.

  Would it perhaps make sense to redirect the greedy subnet to the onion instance? I wonder if it’s even possible. The privacyinternational website used to auto-detect requests from Tor exit nodes and automatically redirect to their onion site. They are obviously not using Tor to visit your site, but they could have Tor installed. You would effectively be sending the msg “hey, plz do your scraping on the onion node.” That is assuming your problem is not scraping generally but just that they are hogging bandwidth that competes with most users. The Tor network has some built-in anti-DDoS logic now, supposedly, so they would naturally get bottlenecked IIUC.

  I guess the next question is whether the onion site has a separate allocation of bandwidth. But even if it doesn’t, Tor has a natural bottleneck b/c traffic can only move as fast as the slowest of the 3 hops the circuit goes through.

• ⁨Comment⁩ on ⁨posts blackholed on the onion instance⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  One problem with all Lemmy instances running later version than 0.19.3 is the front-ends are broken with Ungoogled Chromium. Lemmy instances running 0.19.5 essentially force me to use Tor Browser (firefox). This is unrelated to the onion problem but one of my other workarounds is to use a non-stock front-end with ungoogled chromium. So for example slrpnk.net has alexandrite.slrpnk.net, which is an alternative FE. The landing page of slrpnk.net lists a few other alternative front ends as well.

  I don’t know if there is a way for users to run alexandrite and then specify another backend of choice. But if not, it could be useful to make other front-ends available on the onion.

• ⁨Comment⁩ on ⁨posts blackholed on the onion instance⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  As a test, I enabled js on the onion site and tried again to post from the onion connection. Again my message was simply blackholed. So noscript’s default disabling of JS is not the issue.

• posts blackholed on the onion instance
  Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ to ⁨mander@mander.xyz⁩ | ⁨3⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨What You Don’t Know About Sperm⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  When the hard-working little swimmers encounter the thicker vaginal mucus, their path is slowed. So the sperm often join together at their heads, which gives them greater swimming speed (up to 50 percent faster) than if they were to carry on individually.

  I wonder why that is. If a group of people were to join together and run, the speed of the group would be capped by the slowest runner. And aerodynamics would be worse.