Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment Re:Why Peloton? Why here? (Score 1) 53

Slashdot is news for nerds and stuff that matters.
Personally I do not believe that Peleton is really news nor that it matters.

But weirdly, it is seen as a Tech company and the stock was lumped in with other Tech companies, presumably to have those stock lines that we want to move up, move up further than it would normally do.

There's been a lot of claims of Peleton being the "Apple of Fitness" etc. and they do offer a decent UI from what I hear.

So it's not the worst story ever on Slashdot...

Comment Re:Released too close to the SE (Score 1) 73

Amen!

I really do not like the big phones. I was very happy with my SE but it was getting a bit long in the tooth. So when they announced the SE2 which was much larger than I liked, I hestitated a bit but then bit the bullet. Ordered the 256GB version in April.
It's still larger than I want, but didn't had much choice.
And in October they release the phone I would have wanted.

Yeah, sorry. Not buying the 12, I already got a phone earlier the same year.
Maybe the 13...

Comment Re:Game set match (Score 1) 152

It is not real.

It's a non-peer reviewed research paper posted on a semi-reputable resarch database...

And even assuming that everything in the paper is true and pans out, there's a lot of work needed to turn a research paper into a product. Just ask any cancer researcher. Go ahead, I'll wait for my regrowable teeths which have been proven to work about 5 years ago. In research. :-)

I suspect the Tesla shorts are not going to worry too much. They probably assume the company is going bankrupt before the research might come to fruition.
Knowing research timeframes, I fear they might be correct.

Comment Re: and unlike Android (Score 1) 56

If I had mo points, I would mod your post a troll. Not a particularly good one though.

Android has myriads of security issues. https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.cvedetails.com%2Fvul... is a non-exhaustive list.

Android has generally three sources of security issues:

1. Issues in underlying Open Source code.
2. Issues in Google created code.
3. Issues in code contributed by the device manufacturer.

None of these three entities has ever written quality code. The underlying code seems to be the best quality. The others are unable to write any good code. For a while you could get a new vulnerability in the media server code every month...

So even if we assume that Google can write good code and Apple cannot, the number of Android security issues is probably on par with the Apple issues...

Comment Re:IF THEY REALLY CARE!!! (Score 1) 301

Vehicle fires do happen. Vehicle fires due to car crashes are very rare though. Fatal car fires are even rarer. Only 1% of fires lead to a fatality.
Data is from and probably _very_ US specific.

According to that, 171,500 fires occur a year with an average of 345 deaths. This encompasses all kinds of fires (e.g. arson, trucks with load catching fire etc. included). Doing the math there gives you a chance of 0.2% of dying in a car fire... That's a pretty good number, I'd take it.

The thing is, in an accident it is not the gas tank that is a problem. The gas tank is usually in the back of the car and unaffected by most collisions. The car has been designed to prevent the tank from leaking. If you're in a Diesel powered car, the fuel effectively cannot ignite. I can extinguish a cigarette by dropping it into a bucket of Diesel oil. If you're in a gasoline powered car, you need a very specific fuel to air mix to become dangerous enough to explode. I believe if I remember correctly that number was 7% gas and 93% air.
That basically does not happen.
Even if your car is leaking fuel the fuel needs to ignite first.

All these things can happen, but chances are surprisingly small. To put it into relation to regular crashes: https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fsafer-america.com%2Fcar-... claims there are roughly 35.000 fatal crashes in the US. 345 deaths happen as a result of vehicle fires. That is 0.9% of all deaths. You are literally 99.9% more likely to die from other causes than a fire.

At that point I'd suggest to not sweat it too much. The number of people being burned alive in their car is very small.

A bit of an anecdote from Mercedes, as I'm a bit familiar with them for family reasons: In 1982 Mercedes started production of the W201 car, also known as Baby Benz or "the 190". That car had a steel spare fuel can (possibly available for an extra fee) that was round and would fit into the spare tire in the trunk.
They did that because the company found out that the reason for most car fires is not actually the gas tank but the spare fuel in a shoddy canister in the trunk that got crushed in a crash.

And that was 1982.

Comment Re:I think Google does as much as it needs to do (Score 3, Interesting) 109

I wouldn't bet on the Google experience if I were you.

Anecdotal evidence, feel free to take it with a grain of salt:

I got my entry into the Android ecosystem with a Google tablet in 2012, the Nexus 7 1st gen device. Perfect for playing Ingress, which was what I used it for. The device however was shoddily built. The micro USB charging port broke twice in two years. The device was underpowered from day one on with the Tegra3 chip seemingly being an energy hog giving limited battery time. And one could tell that the Android tablet experience was bolted on. I was rather disappointed to find that Google stopped supporting the device after one major OS upgrade. Android 4.1 to 5.1 and that's it.

Fast forward a few years to 2017. There was an Android app I wanted to run. The Nexus 7 was a bit long in the tooth and because the USB socket was broken again, power consumption was higher than charging power, I decided to get a current model Pixel C tablet. Device was rather expensive at something like 580 EUR but whatever. It was the flagship Android tablet, right?
Half a year later Google announced that they are done with tablets. The Pixel C is declared end of life and no more software upgrades are forthcoming.

Contrast that with the Apple tablets and it's a difference like night and day. Apple's iOS looks way better integrated. Snappier reaction, quicker drawings, faster bootup. Battery seems to last longer on the iPads. But the main difference is the cavalier attitude Google takes to customer support compared to the Apple experience: Google tablet broken, mail it somewhere, get it back repaired 6 weeks later or so. Apple tablet broken, drop by the Apple store, walk out with a new device. Other people have reported repair times of a few days if the device was not swapped immediately. Software updates are the same. With an iPad you get something like 4 to 5 years software and security upgrades.

The Google experience would be excusable if their devices were dirt cheap. But they are not. I replaced the Pixel C bough for 580 EUR with a 2018 9.7" iPad for 350 EUR which has a much better user experience. Add the fact that you can actually get outdoor cases and similar accessories for the iPad series which prevents broken tablets when dropped the Apple device is a much better investment.
The Google tablet only has shitty leather covers which are useless.

All that has lead me to conclude that I am never ever going to buy a Google device again. Probably not even an Android device. But I guarantee if I buy another Android device it will not be from Google. I've been burned twice by non-perfect devices with short lifetimes/support-times. Never again.

Comment Re:Cisco = Backdoors with a router (Score 1) 280

I'd agree that it's a bit concerning to see that Cisco announces newly found hardcoded credential every month.

On the other hand the reason they are announcing these constantly is that they are actually auditing their devices and their firmware and find these. So that is a good thing as they seem to care about security nowadays and do training etc. to teach their developers _not_ to hardcode shit anymore.

At that point, I am more likely to trust Cisco than the other random vendor who never has any backdoors they fixed...

Comment Re:OMG, WHY!? (Score 1) 120

What reason does this even have to exist, except as a hobby project that is not meant to see the light of day?

I really cannot think of one.

It all started making sense to me when I realized that Felix is one of the Slack Desktop client developers. https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Ftwitter.com%2Ffelixriese... says he is also an electron committer/contributor.

This should probably never have seen the light of day but if you consider what a disaster the Slack client is... I am not sure Windows 95 is necessarily much worse...

Comment Re:Yet another reason not to touch IoT (Score 1) 151

As the other posters in this thread said: X10 is pretty much dead for other reasons as well. I have never really used X10 much but I've always found it super infuriating to have this noticeable delay between pressing the button and the light actually turning on. It's short enough that it is not causing problems but it is long enough to tell that something is going on.
The reason for this is just the slow transmission speed of (IIRC) 20bps. That is terribly slow compared to more modern systems such as Z-Wave.

I never really liked Z-Wave and other protocols though. The technology is fine, but the politics are terrible. It's like every single vendor has decided that they want to own the system and nobody else is allowed to play. Typical example is Philips Hue trying to lock out other vendors such as Osram on their Hub. That was rolled back but it still leaves a bad taste in my mouth.

Since then I've been looking at giving KNX-RF a go which is a professional (read expensive) smart-home standard originally developed in Europe. https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2F... has the details but the nice thing is that it exists for twin wires, wireless and IP. They had a powerline transmission mode but I think that is dead. What I like the most though is that they seem to have managed the cross-vendor functionality very well. Every switch will work with every actuator and the protocol is fully bi-directional.

The only annoying thing I found so far is that there's an entry fee of about thousand buck to buy the programming software...

Slashdot Top Deals

Yet magic and hierarchy arise from the same source, and this source has a null pointer.

Working...