204 karma · joined October 15, 2016
This hits too close to home. I'm sending you my therapist's bill for this month.
I've tried several of the "budget" NextCloud hosts. I'm not going to name names, but all of them were very disappointing. File syncing frequently broke in hard to diagnose ways. And from a perspective of overall service, I would get 502s, 503s, or 504s far more often that I should have. This was with multiple budget providers. I didn't try any of the more expensive providers, because I couldn't afford it, so maybe this is a "get what you pay for" situation... But in theory, the size servers I was paying for should have been able to handle our traffic volume.
Anyway, after a couple of years of trying to make hosted NextCloud work for us, I gave up and bought Dropbox's paid service and haven't had any issues with it.
We use Cryptomator on top of Dropbox to ensure data privacy, by the way. Back when we were using NextCloud, we had been using their end to end encryption plugin until we discovered a silent failure mode in which it was uploading documents in plaintext to the "encrypted" folder. I believe nowadays the recommendation even for NextCloud is to use Cryptomator on top, rather than their built-in encryption.
Look, I'd love to contribute to the kernel, but the amount of time I have to play around with these things is now measured in minutes per day. So no, sorry, I don't have time to rebuild my kernel from mainline, and then bisect, and then cherry pick patches, and then test out proposed updates, and then help shepherd it through my distribution's patching mechanism.
So I just gave up on Bluetooth on Linux and plugged in Logitech's proprietary Bolt dongle, and re-paired my devices with it, and haven't had trouble since. I'd prefer to use standard protocols, but this isn't the first time a kernel update broke my Bluetooth setup, so I think I'll stick with what just works.
- Your ISP is [ISPs are, to your 2nd point] actively hostile to running "servers" from your connection, so you must either pay a ridiculous premium for that privilege, or jump through hoops to evade their intentional breakage.
- Your other cousin does something illegal (sells drugs, posts revenge porn, threatens a public official) using your host and now the police are knocking down your door in the middle of the night and dragging you in for questioning. Even if you avoid charges, your neighbors eye you suspiciously from then on.
- The raw idea seems easy.
- The initial implementation seems like it should be of moderate difficulty, but is actually very challenging to get even close to right.
- The long term maintenance is a nightmare, but don't worry, you won't survive long enough to worry about that.
- The infrastructure and policy implications of getting and keeping it connected to everyone else are intractable. (See https://news.ycombinator.com/item?id=38531969 for some tip-of-the-iceberg examples.)
And yeah, none of that even touches on marketing.
I said no such thing, and I'd thank you not to put words in my mouth. As I explained in a different subthread:
> before you declare war on the ones that don't wanna change
I never "declared war" on anyone. I guess it's a lot easier having never used Facebook or Facebook products. I had a bad feeling about them from the very beginning and I've only ever felt more right in that feeling.
What would usually happen was, I'd meet someone new at some event, or maybe I'd be talking to a relative at a family gathering, and they'd say something like, "What's your Facebook? I'd like to add you to GroupX," and I'd reply that I didn't use Facebook. Then they'd follow up with, "You should join, it's <blah blah blah>," to which I'd politely explain why I won't ever join Facebook. And then one of two things would happen. Either they'd understand, and we'd exchange phone numbers or email addresses, or their eyes would glaze over and they'd find some excuse to walk away.
For the latter group, obviously we didn't interact online. For the former group, I'd text or email, and maybe they'd respond, and we'd have what I consider to be a normal relationship, or maybe they'd rarely or never respond, and we'd have no relationship. But in either case, I wasn't haranguing people not to use Facebook; I just wasn't using it. If not using Facebook meant I didn't have a relationship with someone, I was okay with that.
For most of the non-techie people in my life, I just communicate via common open protocols like SMS and email, things everyone can use easily. I do encourage people to try Matrix or Signal, but I certainly don't require those to communicate with me.
I'd love to work at a competant and impactful organization on something meaningful. The problem is, I genuinely believe that the probability of such an organization existing, and of them hiring, and of my having the right skill set, and of my learning about, applying to, and passing the interview, is essentially 0. Now, I struggle daily to avoid the cynicism you described so well.
> SHR was a light OpenEmbedded-based distro
I might have been thinking of a different distribution. There was one that brought in all of the GTK, Qtopia, and Enlightenment libraries, so you could run pretty much anything that could compile on the Freerunner, but it was quite slow and consumed most of my SD card (which at the time was probably only something like 1GB).
I guess if you were a hard-core hardware and systems hacker, the OpenMoko was an acceptable platform. For anyone else, it was a terrible product and the company that made it was obviously doomed to fail.
Maybe if it had come out at least 2 years earlier, it might have had some hope of carving out a sustainable niche, but by the time it did come out, the expectations set by iPhone and Android made it impossible to find a product-market fit, even among open source lovers like me. Maemo, while if memory serves not fully open sourced, was far closer to something sustainable, but then Nokia voluntarily imploded :-(
I wish Nokia had continued developing the Maemo OS.
* The leadership was terrible. They had no clue what it took to make a mass market product. They just assumed that they would sell hardware and a community would provide a working operating system and apps magically.
* The hardware was buggy. There was one issue that if you let the battery drain fully, you could not get the phone to recharge it and had to use an external charger. Another issue was that the GPS receiver was accidentally surrounded by metal, so barely functioned. There were all kinds of problems with the radios in the early days. Oh, and that touchscreen -- I guess it was typical of pre-capacative touchscreens, but it was hard to use without a stylus and impossible to hit widgets near the edge of the screen.
* The hardware was massively underpowered (compared to competitors) by the time the Freerunner actually shipped. Weak CPU, little RAM, 2G cellular radio in an era when 3G had become standard, so like 5kbps max data transfer.
*Because of the failure of Openmoko leadership, the community fragmented a hundred ways. This meant that there were a dozen or more "distributions" of an OS for the phone, and none could do more than one or two of the things a typical user wanted in a phone at that time. Then there was finally a big bloated distribution (SHR if memory serves) that packed in enough libraries to make a more or less "usable" device, but doing so maxed out the phone's meager storage and RAM, making it nearly impossible to do anything "smart" with it.
* Once again, in absence of strong UX leadership, the community resorted to dumping X11 apps without modification on the tiny screen. Think impossible to read fonts and dialog boxes that ran off the screen with no scroll capability. The vast majority of devs seemed to only use it by hooking it up to a computer via USB networking and SSHing into it.
As a technical user, I could live with this. Kinda. Sorta. Using it was an exercise in masochism. I was embarassed ... no ... humiliated when a nontechnical person compared their iPhone with the OpenMoko that I had talked up so much (before receiving it).
I had planned to destroy the phone in some fantastic fashion (e.g., melting it with a laser) as soon as I got a real phone. But by the time I could afford an Android, I was so done with it that I just dropped it in the trash (after wiping it, of course).
We have no idea how or when he got infected. As far as he knows, he never had a bullseye rash, although apparently that doesn't always happen. Now I slather myself in DEET whenever I go into a an even semi-woodsy environment.
As a side note, I ended up re-enabling system fonts because disabling them broke a large percentage of web sites' CSS.
On my initial run, I got an overall entropy of 17.63. My two biggest identifiers were screen resolution (1000x595x24 which was approx 1/22000 browsers) and webgl hash (approx 1/3800 browsers). I fixed screen resolution to 1000x600x24 (approx 1/85 browsers) and disabled webgl hashing (approx 1/6 browsers) and the overall entropy did not change one iota, despite also closing browser, flushing cache and cookies, etc. I gave it another run with a deliberately weird resolution (1420x701 which was something like 1/105000 browsers) and once again, the overall entropy was exactly 17.63. So based on my experiment, it seems that screen resolution and webgl hash have no effect whatsoever on [Panopticlick's] overall entropy score.
I've closed the above bug report as it's not really a bug.