LedgeDrop

@LedgeDrop@lemm.ee

This profile is from a federated server and may be incomplete. Browse more on the original instance.

LedgeDrop,

Thanks for the write-up. I think Santa will be bringing me a Firestick Max for Xmas… and I’ve already got a real-Debrid subscription (which I highly recommend). I look forward in trying to plug them together.

I feel like /c/memes has taught us a valuable lesson today: Would it make sense to develop a feature to block a comm from our feed for a selectable unit of time (1 hour, 1 day, etc.)?

Even if we’re subscribed to them? Could a temp block exist in conjunction with a subscription? I love c/memes but holy shit no matter which sort I select by they’ve managed to overwhelm my feed.

LedgeDrop,

I like the idea of improving the quality of “what’s hot”.

At the moment, the current implementation is pretty weak. Even in this thread, as I’m reading it: Your post is top… even though it’s 25 minutes old and has only 3 upvotes, compared to the second thread which is an hour old and has 39 upvotes.

I can see how Lemmy would benefit by modularizing the “hot” algorithm. This would allow each Lemmy server to install/test their own (or shared) “hotness” algorithm. Eventually, I think, everyone would converge but in the meanwhile it would allow for a rapid exploration of different possibilities.

LedgeDrop,

You’ve got a good point regarding Photoshop. Gimp exists on Linux, but I find it immensely powerful but hard to wield.

Gaming with the Steam Desk has gotten better for Linux with the introduction of Proton and I imagine this’ll only improve.

You can see if your favorite game is supported with Proton here.

LedgeDrop,

The end user’s ip is hidden in the onion network. The server will get the ip address of the “last node” your client routed it’s request through (and that node only has the ip address of the previous node, etc).

However, the clients ip can be leaked if a server creates some Javascript which makes an Ajax call (basically, an additional http request). A malicious Ajax call will not go through the onion network and thus expose the clients real ip. Hence, it’s recommended to disable Javascript and other features while using tor.

LedgeDrop,

I did a bit more homework and you’re right.

“Back in the day” running Javascript increased your attack area. But now-a-days I guess it’s consider “safe”.

I did find this old (7 years ago) posting which talked about concerns. Today, I guess the rule of thumb is to avoid (or limit) browser plugins.

Thank you clarify that.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #