Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Tor's trust model has always been broken (Score 3, Insightful) 50

This is a primary reason why I2P (Invisible Internet Project) exists. Its much less centralized than Tor, mixes other peoples' traffic with yours by default, and over the years has typically used stronger encryption than Tor. Its just more private and secure overall.

The people who make the TAILS distro recognize Tor's shortcomings which is why they include I2P along with Tor. I2P isn't built to outproxy to the regular web (although it can), but you do get the ability to do fully decentralized/anonymized messaging and torrents, for instance, along with hidden websites. On top of being more private than Tor, its a protocol that's meant for general purpose use.

https://geti2p.net/en/

Comment Re:F/OSS reality (Score 1) 167

Desktop pretends to be (or maybe they actually believe that's what they are creating) a product for end users but is a product for admins and developers who are familiar and comfortable with the UNIX-like environment to use on their personal computers.

This is total BS. Lots of people who aren't computer experts use Linux desktops every day. My wife is one of them.

The obligatory Slashdot-Linux-enthusiast defense of "Desktop Linux for my relative" never ceases to make me chuckle. I can always spot the authentic ones, because they contain the "we have the Web so who needs a native UI or native apps" meme.

Comment Re:F/OSS reality (Score 1) 167

I can always spot the authentic ones, because they contain the "we have the Web so who needs a native UI or native apps" meme.

Did you ever consider that people advance this idea because it's true? There's plenty of people that JUST want email and the web. They don't care about native apps and never will. They use their computers to communicate with other people, and couldn't care one whit about doing their taxes on their computer, or editing video.

Its demonstrably UNtrue, otherwise Apple and Microsoft would not still be viable companies. "Plenty of people" apparently does not define the whole consumer electronics market.

That you think Chrome OS belongs in the Desktop Linux category is instructive... But Google doesn't even identify Chrome OS as Linux. They could switch to a different, closed kernel and hardly anyone using Chromebooks would notice or care. That's because a Chromebook is a type of mainframe terminal or client, not a personal computer (it may be converted to a PC, but that's not its design).

If you don't think this is a common windows experience, you're not paying attention.

The tragedy is that you can't even give a Desktop Linux distro away for free despite how awful that Windows experience has been.

Comment Re:F/OSS reality (Score 1) 167

The reasons why GP is far from an excellent reply:

1. Anecdotes are not data. Doubly so if its someone who lives with you.

2. Native apps still matter because they attract a wide-ranging ecosystem of talented people who move between native apps and the Web, and...

3. ...That range of people between grandma and kernel developers form networks of support and advocacy. If the Power Users don't like your pile of bytes called an OS, the more creative ones won't start writing interesting apps for their non-techie friends and colleagues, and they won't recommend the OS either.

4. People depend on the 'look and feel' of software environments. Its what enables tech support staff to deliver *usable* instructions in a way that doesn't feel threatening to users, and also to get reliable answers from those same users. Having a well-defined GUI is important, but Linux is very slippery in this area.

There are many more reasons why GP represents nerdy myopia and wishful thinking. Perhaps the most important one is that Apple and Microsoft laid down, by example, a de-facto definition of what Desktop Personal Computer is. The FOSS community actively sabotages itself whenever it tentatively tries to reverse engineer the *concept* of the desktop PC; I think most of those numbskulls would define it as some kind of aberration that needs to be stomped out. Where "platform" is supposed to evoke (feature) stability and recognizable surroundings, the Desktop Linux crowd instead create this.

Perhaps I should start using stronger words than "numbskull" for these true believers.

Comment Re:F/OSS reality (Score -1, Troll) 167

The reasons why GP is far from an excellent reply:

1. Anecdotes are not data. Doubly so if its someone who lives with you.

2. Native apps still matter because they attract a wide-ranging ecosystem of talented people who move between native apps and the Web, and...

3. ...That range of people between grandma and kernel developers form networks of support and advocacy. If the Power Users don't like your pile of bytes called an OS, the more creative ones won't start writing interesting apps for their non-techie friends and colleagues, and they won't recommend the OS either.

4. People depend on the 'look and feel' of software environments. Its what enables tech support staff to deliver *usable* instructions in a way that doesn't feel threatening to users, and also to get reliable answers from those same users. Having a well-defined GUI is important, but Linux is very slippery in this area.

There are many more reasons why GP represents nerdy myopia and wishful thinking. Perhaps the most important one is that Apple and Microsoft laid down, by example, a de-facto definition of what Desktop Personal Computer is. The FOSS community actively sabotages itself whenever it tentatively tries to reverse engineer the *concept* of the desktop PC; I think most of those numbskulls would define it as some kind of aberration that needs to be stomped out. Where "platform" is supposed to evoke (feature) stability and recognizable surroundings, the Desktop Linux crowd instead create this.

Comment Re:F/OSS reality (Score -1) 167

Desktop pretends to be (or maybe they actually believe that's what they are creating) a product for end users but is a product for admins and developers who are familiar and comfortable with the UNIX-like environment to use on their personal computers.

This is total BS. Lots of people who aren't computer experts use Linux desktops every day. My wife is one of them.

The obligatory Slashdot-Linux-enthusiast defense of "Desktop Linux for my relative" never ceases to make me chuckle. I can always spot the authentic ones, because they contain the "we have the Web so who needs a native UI or native apps" meme.

Comment Re:See it before (Score 4, Interesting) 276

Anyone who looks back in my posting history will see that I have long, LONG advocated for tackling the UI and packaging paradigms on FOSS desktops because they choke-off interest from the type of creative person who develops apps. (Even worse, they scare away people who would like to experiment and become budding app developers, so those people cut their teeth on OSX or Windows almost as a rule.)

PC tools are supposed to link the user with the power and features of the underlying hardware, making them at least discoverable in the GUI; In other words, there must be lots of vertical integration. Also... the GUI must have a 'gist' or feel consistent because this is a sign of feature-stability in the OS.

What FOSS has is a bunch of developers who tinker with the OS itself (I include the GUI in this, as it rightfully belongs in the category of OS) and assume that anyone who understands how a system works internally can trivially design GUI features... a big, big flaw in what is not so much an articulated belief as an unhealthy attitude. This is part of the subconscious of the FOSS world, and it results in maladies like not being able to describe fixes and workarounds (or just general usage instructions) as GUI snapshots and walkthroughs (almost always, the user will be directed to the CLI); It means even seasoned tech support personnel will struggle to interpret DEs and other UI features they are not very familiar with. Just getting to the point where your cousin or boss can try out your creations is hell.

App developers should have the power to create exceptions for UI features in their *apps* (I said apps, not OS), because that embodies the two things app developers subconsciously look for: power and feature-stability. The default behavior is always the OS way (i.e. ONE way) out of respect for all users in general; If the default behavior/appearance is ten possible ways, then the app developer feels like they are managing chaos instead of power.

My 'remedy' for the FOSS OS problem would be for a distro like Ubuntu to shed its identity as a "Linux distro" because the Linux moniker just confuses people at this point; and to take full control over the UI design so that it conforms more to a single vision (something that is apparently already under way). Pretty much all of the OS except the kernel should be original to the project or forked and, as Google did for a while with Android, Canonical should threaten to fork the kernel if that is necessary to improve the UX.

I'll also point out that Ubuntu has gotten some meta-features that were typically missing from a Linux distro, like a full-blown SDK and extensive whole-system hardware compatibility tests and searchable database. What would remain to be done beyond this is to standardize on a GUI IDE (with capabilities like Xcode) and extend the hardware program to include a certification process (with licensed emblem) that system and peripheral manufacturers can use in a straightforward way.

Also, packaging is a whole other cup of worms, though I personally think emulating OSX app folders would be a good foundation for easily-redistributed apps. This means that an OS repository would have to stop at some well-defined point instead of trying to mash all the apps and OS together along with the kitchen sink.

Comment Re:OpenBSD proves the claim to be wrong. (Score 1) 58

You forgot AppArmor, which is one of the most widely-used on Linux. Of course, I'd much rather have Qubes' isolation mechanisms so that my banking, work and leisure activities (and even my NICs) don't even share the same virtual machine -- My data sets are kept separate and the interfaces between those domains are simple and very strong.

Comment Re:on designed for "security" (Score 1) 58

When I am designing for "SECURITY" I want to simplify the critical protocols so that they can be described by a state machine and then implement them in silicon.

It would be interesting to see a Xen hypervisor implemented in silicon, as that is what Amazon EC2 and Qubes OS base their security on. Qubes doesn't even use kernel-based permissions for its single-user desktop model; It gives you the means to control dom0 and everything else resides in VMs.

Comment Re:Still a useless exemption (Score 1) 74

'Denial' isn't just a river in Egypt.

You're missing the point.

Quadcopters are dangerous

Sure, just like countless other objects. But if the FAA was worried about safety, they'd be expecting the recreational users of them to also be subject to the regulations they're putting on commercial operators using exactly the same 3-pound plastic quadcopter in exactly the same way. A guy checking out his own roof gutters with a consumer-grade quad, and a roofing contractor using exactly the same device in exactly the same way present exactly the same safety risks ... but the FAA only considers one of those two people to be subject to a $10,000 fine. How do you reconcile that?

Easy. For both the homeowner checking his gutters as well as a airplane pilot flying overhead, self-preservation is a big factor.

OTOH, third parties flying vehicles around other people is an inherently callous (and cowardly) act.

Slashdot Top Deals

"Gravitation cannot be held responsible for people falling in love." -- Albert Einstein

Working...