Areldyb

joined 2 years ago
[–] Areldyb@beehaw.org 10 points 1 day ago

Not sure whether it matters, but Guy 3 and Guy 1 are the same Guy, who also sent death threats to the author years ago. Dude needs some serious help.

[–] Areldyb@beehaw.org 4 points 3 months ago (1 children)

The article talks a little about it. It's more of an unwind+rewind cycle:

The pull from this force then rotates the ground-based drum at a high speed.

This rotation then generates electricity that can be stored in a battery system for deployment wherever and whenever it is needed.

After 45 seconds, the kites are levelled up so that the pull from the wind is momentarily minimised.

This enables the tether to be wound back in, using only a fraction of the electricity generated when it was being spun out.

The result is a net gain in renewable power at the simple cost of flying a kite.

Then the cycle is repeated, again and again, potentially for hours on end.

It makes sense to me. I hope it catches on!

[–] Areldyb@beehaw.org 3 points 4 months ago

a glance at their artist image and bio should be enough to persuade even the least skeptical observer.

At least we know the article was written by a human.

[–] Areldyb@beehaw.org 4 points 7 months ago

It once was. Sounds like it could be again!

[–] Areldyb@beehaw.org 5 points 10 months ago* (last edited 10 months ago)

https://en.wikipedia.org/wiki/Imperial_boomerang

Edit: to be clear, OP's article does not at any point claim that these are American government-operated drones, so this isn't really a good example of the imperial boomerang effect. I just wanted to point people to established reading on the topic you brought up.

[–] Areldyb@beehaw.org 2 points 1 year ago

I mostly rely on built-in "scheduled send" features these days, but in the past (and possibly future, can't remember!) I've used Time Cave and been happy with it.

[–] Areldyb@beehaw.org 1 points 1 year ago

Pinball Deluxe Reloaded has been an excellent time-waster on my phone for a while now. It's available on PC too.

[–] Areldyb@beehaw.org 27 points 1 year ago (1 children)

If your router isn't even a Linksys router, then it's most likely a false positive result and can be safely ignored. If you want to be extra sure, you could attempt to actually exploit the vulnerability with routersploit and see whether you get anywhere.

In general, the fix for a vulnerability in an end-user network device is some combination of "update the firmware" and "disable the vulnerable feature".

[–] Areldyb@beehaw.org 3 points 1 year ago (1 children)

... ... are you secretly a mosquito

[–] Areldyb@beehaw.org 14 points 2 years ago (5 children)

Hey, um, you're all over this thread and you seem like you've really got an axe to grind here. What's your story?

[–] Areldyb@beehaw.org 1 points 2 years ago

Promising, but not ready for primetime. I spent the last two days using it as my phone's default search after you mentioned it, and... well, I went back to Google, at least for now.

[–] Areldyb@beehaw.org 140 points 2 years ago (8 children)

My second proposal — and this is a wild one — is that promotional notifications should just not be allowed. Or you can opt in to them if you desperately want to hear from the Starbucks app every single day, but you should have to go out of your way to do that and should not be the default behavior when you choose “allow notifications.” Just an idea!

The author calls out the Starbucks app here, but doesn't mention how blatantly dark-patterned its notifications really are. Android allows apps to set up multiple notification channels, so you can selectively prioritize (or, more often, mute or block) notifications based on their content. Starbucks uses this feature... to create a single channel called "Promotions & order status". You wanted to know when your order's ready? Fuck you and your concentration, get double stars today!

I appreciate the notification controls Android gives me, and I use them aggressively. If an app pushes a notification that doesn't actually require my attention, I block that channel, and if it does it again, I block notifications for the whole app. I agree with the author, though: I shouldn't need to do that.

view more: next ›