WhyJiffie @ WhyJiffie @sh.itjust.works

Posts

3

Comments

1,324

Joined

2 yr. ago

it couldn't be too popular as a windows only project. I assume it was too lite known, like I never even heard about it here or other places

bluetooth is short range isn't it? so while this is a problem, it is not the exact same thing. network based location is not a replacement for GPS.

Google already uses this with WiFi to help "bootstrap" GPS localization. It is much faster to get a GPS fix if you already know roughly where you are (a few seconds vs a couple minutes), so they use nearby WiFi/Bluetooth devices to determine that.

I think you mean A-GPS, which is not related to wifi and bluetooth, other thqn being able to use wifi to access a server for downloading current constellation data. phones that have google mobile services installed, have an additional fused location source (besides a network based and a gps based location source) that tries to fuse the 2 sources while the gps signal is not precise enough. but as I know fused location computation happens locally

well probably they wouldn't want it anymore

that really depends on the location. not everyone lives in big cities. is there a way today to give access to bluetooth without giving access to GPS?

I don't know what is so broken, but this image does not load in voyager, and neither when opened in browser for the lemmy.zip instance

I think it's debatable whether storing in volatile memory is persisting, but ok. And by debatable I mean depends on what is happening exactly.

A court order forcing them to no longer garbage, collect or delete data used for processing is a problem.

what, are they going to do memory dumps before every free() call?

I think not all clients support it. is it a feature on the default lemmy website?

so they never should have persisted that data to begin with, right? and if they didn't persist it, they wouldn't need to retain it

I've seen people do this on Lemmy, one person even had a stalker that would go server to server to reply angrily to their posts because he felt "wronged" somehow.

those need to be reported and banned, their replies mass deleted.

Plus, nobody is reading this stuff after a month anyway,

Because we don't have a proper (or any) system for subscribing to threads. but if I have saved a link for myself for future reference, it'll be gone!

I'm just saying, don't be surprised if people start running instances that disobey deletions

one could argue that installing packages is a dangerous permission

this can be useful, but hopefully it never becomes a default, it was enough of a pain when Windows was thinking that updates are more important than keeping the hibernated programs

even the outside?

for the inside I don't think it's a problem, it's hygienic

of course the eventual enforcement is left to the service provider (google) as it often is how it works. when you can't define something with 100% precision, you leave some room for interpretation. they can then decide what to do on a case by case basis.

totally clear. and exactly the subject is the broadest: harmful to anyone or anything

it seems they will, just not too soon

Oh you will. I know the name for a few months now and I still read it slurpnik

if they haven't defined it, then legally it is meant in the broadest sense, isn't it?

Drives only consume power on reads and writes, if your NAS spins them down as it should (and apparently QNAP doesn't, which I didn't know).

not really. not all drives spin down by themselves, by default. and even if they do, it'll happen relatively long after reads and writes, a the while it'll consume power.

The problem seems to be that even with a perfectly clean slate, no services running, the system set up in their own RAID0 SSD pool, the HDD's, even with 0 bytes of data on them, are being pinged for access at least once a minute.

if it's for drive health stats, and the device runs linux, hd-idle could help. it only counts actual block device (so, storage) access as activity

edit: https://github.com/adelolmo/hd-idle

And don't think that SSD drives would do better - spinning disk drives generally have far better idle power than SSD does, and usually much better write power consumption.

I wonder if they can be "spinned down" like hard drives. their startup time would be much faster, so it's shutdown could even be on a tighter schedule. I mean probably they dont have an internal idle timer, but who cares if you can just have something like hd-idle that shuts it down according to a better schedule.