sha666sum

> Personally, I think LXDE/Lubuntu is obsolete.

I suppose this is precisely why the project is changing direction. LXDE/LXQT are pretty cool desktop environments and I'd hate to see their development come to a halt even if I'm personally not a user.

There's a lot of pseudoscience out there like flat earthism, homeopathy, dowsing and what not. The belief that "the establishment" is ignorant and narrow-minded and could be proven wrong by a determined individual willing to challenge those beliefs is what enables these beliefs in the first place.

Skepticism and curiosity are healthy, driving forces of science that can be taken too far to lose touch with reality.

I'm no journalist, but I guess that being first to report is more important than minor errors in the article.

I think dmenu is a good example of this. It's a common launcher application that's (at least) known to all i3 users. Here's a succinct explanation from the man page:

"dmenu is a dynamic menu for X, which reads a list of newline-separated items from stdin. When the user selects an item and presses Return, their choice is printed to stdout and dmenu terminates. Entering text will narrow the items to those matching the tokens in the input.

dmenu_run is a script used by dwm(1) which lists programs in the user's $PATH and runs the result in their $SHELL."

In practice you press Super + D, type a few letters to match the name of your program (such as "fox" for "firefox"), and press enter. It's so fast that any delay is near imperceptible even on older hardware. It also accepts command line arguments if you don't care to read the stdout from the process. This is a stupidly simple program that works with no configuration unless you want to change the font size.

In other words, in a few years everyone will need to replace their perfectly good computers because of software bloat.

> This guy didn't experience what happens in most mental breakdowns.

Your case is really not what I would call "most mental breakdowns" and it's unfair to belittle someone else's issues because they don't match up to yours. Mental issues are an everyday reality for millions of people, and by their very nature might mean the world to those suffering from it while seeming insignificant to everyone else.

You don't need to emphasize the severity your own experience, feeling shit is not a competition.

I ran into a CloudFlare DDoS protection screen and had to enable JS.

The irony is real.

My biggest gripe with SourceTree (and Atlassian products in general) is the poor use of screen space. Too bad this new visual look seems to do nothing to fix it.

In PowerShell, ls is an alias for Get-ChildItem.

Personally I started out with Arch on an old 64bit Atom netbook. I got a nice hobby out of it, and liked it so much I put it on all my computers. If you have a knack for googling and enjoy reading high quality wiki pages that document far beyond the scope of the operating system, you'll probably enjoy it. It requires patience and some time investment, but it's no rocket science.

That Dropbox retains data far longer than what can be considered reasonable. It's in the headline, of course, but I think that quote highlights the severity of it quite well.

>I installed dropbox earlier tonight and I allowed it to do a full sync with my local folder. When I checked it out as it was close to finishing I found 2 extra folders in there.

>They are so old I initially didn't even recognize them. Took me a couple of minutes to realize they're a couple of folders with project files from about 6-7 years ago, so extremely old.

Whoops?

So that I don't make unfounded claims I had to do a bit of research on the Android app permission model. Source: https://developers.google.com/android/guides/permissions

> Google Play services automatically obtains all permissions it needs to support its APIs--your app won't normally need to request permissions to use them. However, your app should still check and request runtime permissions as necessary and appropriately handle errors in cases where a user has denied Google Play services a permission required for an API your app uses.

I'd say this constitutes a loophole in the Android app permission model and Google as well as other app developers have a mutual interest in using it so that their apps get as many permissions as possible. It has practical benefits too, though: querying Google Play services for your location info, rather than independently looking it up, saves battery life. Google certainly has financial interest in it - their position in the middle gives them analytics data and keeps developers dependent on Google API's. I don't think there are many F-Droid apps that are dependent on Google Play services.

It's likely also easier for the developer to use Google's API rather than provide their own implementation, which is of course what Google wants. It just comes at the expense of the user.

I suppose the solution is to tighten the app security model, at least on an opt-in level, as I can't imagine the average user being interested in being queried for even more permissions. I think apps should require permission to interact with other apps (such as Google Play services), and most of all they should require permission to access the internet. I can't imagine Google championing this cause, though.

I misread your post in haste, sorry.

Slightly tangential, but yesterday my Gmail app kindly informed me that I need to give Google Play Services the following permissions in order for it to function:

- Body Sensors

- Calendar

- Camera

- Contacts

- Location

- Microphone

- Phone

- SMS

- Storage

This promptly led me to discover K-9 Mail. Not entirely incidentally, Google's Calendar was so helpful as to suggest that I install Google's fitness tracker to integrate with the Calendar. I politely declined the offer, and installed Etar.

Sandboxie is nonfree and after a trial period only allows sandboxing one app at once. Firejail just had a local privilege escalation exploit, but I'm still using it (although more cautiously than before). Mbox appears unmaintained, and sandbox-exec isn't even for a platform I use.

I'm quite glad that Firefox implements sandboxing of its own.

The screenshot on the github page shows running _yaourt_ as _root_. I can't see how doing it on Windows makes it less horrifying than on Arch.