I figured it was something like this, but it was far less obvious than the `gnome-software-plugin-flatpak` package that kind of set everything up for me.
Is there documentation anywhere I can reference?
1,583 karma · joined July 29, 2013
Is there documentation anywhere I can reference?
I think it's one thing to recognize that Purism is providing patches, but that doesn't translate to a device people can and want to purchase.
Nonetheless, I do appreciate the community forming around this. For a long time in 2020 it felt like encryption was going to be a "when we get to it" task, so it's good to see more things popping up.
Disclaimer: FWIW the closest I ever got to Arch proper was Manjaro, so I definitely didn't do an exhaustive search of every distro.
I'm not a web developer by trade, so this is good advice and something I never looked into. Thanks for the heads up, I'll have to block Javascript and see if I can get it working. I might be able to remove the prettify stuff entirely.
I think the hardware is a limiting factor, but part of what makes these devices unique (as other commenters have pointed out) is that they can run with minimal proprietary blobs. I don't believe either phone is at "no blobs" yet, since even Purism had to have blobs for the Baseband and Wifi (I think, or maybe it was just Wifi?). Nevertheless, Ubuntu Touch does work on Android devices today, and I think even PostmarketOS has some adoption on OnePlus 6/6T.
Overall though, I'd say that power isn't really the big thing. I think existing software has shown that you really don't need a lot of compute to be able to run apps smoothly on these phones (Morph browser, many GTK apps on the Librem 5). Battery life remains a concern with these devices, but that seems to improve bit by bit over time (at least, the Pinephone does. Not sure what is up with my Librem).
I think getting a partnership would be doubly tricky though, because a lot of the market just doesn't want these phones to begin with, and struggling companies are unlikely to attempt to explore mobile Linux unless they know it'll turn their ship around. Maybe if they get banned from using Android somehow (much like Huawei was), but even then I can't say I'm sure that Linux is appealing for companies in that scenario.
With regards to thermals, my writing may have been a bit unclear. The thermal issue was definitely only during my one trip, when it was in the car with me and had been charging + running for a couple hours of driving. There was sunlight but it wasn't in direct sunlight. I suspect charging + running (music) + ambient heat was part of the problem, but I've never had a phone be that hot even on a long drive like that. I've been fairly careful otherwise to not place it in direct sunlight, mostly because I'm afraid the heat will damage the battery in some way.
As for the battery, I'll have to do some digging there, although I can't get to that today. Those are great tips to look into though, thanks for posting them. I'll note that I haven't tested the latest kernel, so if any patches have gone into the Librem 5 regarding power in the last three weeks, I probably wasn't able to quantify that!
:g/<regex>/<command>
is the general form for [g]rabbing lines that match a regex and applying a command over them. You can also chain the command:
:g/<regex1>/g/<regex2>/<command>
I'll admit this isn't exactly something you intuit as easily as a drop-down menu, but (neo)vim does have tools for all these things out of the box.
Notifications in the system are still pretty hard to work with, and email notifications are no replacement. Comments on pages are unwieldy and mess with cursor focus in annoying ways. I've definitely submitted this feedback to support before and I can understand that not everything can be worked on at once. However, I still have faith that the team will work the kinks out eventually.
EDIT: To be less negative, I should also note that Notion still has probably _the_ best LaTeX / mathematics support out of any documenting system I've ever used. I vastly appreciate this, as it is often easiest to share complex mathematics via a shared Notion doc since I work remotely.
It's hard to sympathize with Purism here. Supply chain has gotten quite messed up thanks to the pandemic, but there's little excuse to treat your customers this way. It goes beyond negligence and into contempt, if you ask me. The least they could do is put that at the front and center of their update, and offer folks who may want refunds to get out early.
The kicker is that if you order the $2000 variant (because who doesn't love paying more for a low-end phone than they do a couple months rent) their production is still at the same capacity.
If you convert everything to continuation passing style, then every function call, tail call, recursion, etc. is just as expensive (and expressive) as a GOTO. This is, incidentally, the main "trick" or lightbulb moment in the classic Cheney on the MTA paper by Henry Baker [1].
Now if we're talking specifically in C, then absolutely! But while this intuition holds for C, it's not always true and doesn't have to be always true.
[1] https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.54...
It's not a short read, but is very easy to follow. I highly suggest subscribing!
[1] First day: https://www.bloomberg.com/opinion/articles/2021-01-25/the-ga...
[2] Second day: https://www.bloomberg.com/opinion/articles/2021-01-26/will-w...
[3] Today: https://www.bloomberg.com/opinion/articles/2021-01-27/reddit...
With that out of the way, the best book I read regarding conflict and resolution has been "Conscious Business" by Fred Kofman. While his strategies relate largely to the business world, they are applicable in a very general sense. I bring this up because these strategies will help you in framing and explaining why this matters to you.
The main takeaway from the book is that you need to approach these problems from a place of infinite empathy. Remember, your final goal is not to "win the conversation" or have the last word, it's to come to an agreement of shared values and collectively (that means, you and your parents) build a strategy in combating the underlying problem.
To build that strategy, I recommend taking a page out of the Less Wrong sequences, and _Hold Off On Proposing Solutions_ [1]. Somewhat ironic given what I am currently doing, so I suppose I have already failed. Anyways, on this note, recall I said that the goal was an "agreement of shared values." Start here. Begin by listing your values and frame these in the context of the conversation.
As for the exact solution, it may very well be a matter of how you form beliefs vs. how your parents form beliefs. Being able to describe your epistemology and how it differs from their own is a valuable tool. However, it can often be difficult to carry a heavy conversation for long enough to get to the root of this. I point back at Fred Kofman, and having a well of infinite empathy. You have to be willing to commit a lot of time.
And to that last point (committing a lot of time), there are some stories out there of people being converted both to and from dis/misinformation. I've been thinking about this quite a bit over the last couple years. Fortunately, there are people who are better at this than I am. Jane Lytvynenko [2] is a wonderful disinformation reporter, and she puts out a lot of resources for how to spot fake news, how to look at evidence critically, how to critically examine online content, etc. She doesn't quite get to using Bayes' theorem, but dismissing fake news and contrived stories doesn't often rise to the level of needing Bayesian reasoning (although it does help!).
With that said, I'm sorry that you're encountering this with your parents. While few have commented, I think more than a fair share of people are running into this issue more and more. The most important part is the empathy, and remembering your goal. After that, the best you can hope for is enough time and energy to help drive the point.
[1] https://www.lesswrong.com/posts/uHYYA32CKgKT3FagE/hold-off-o... [2] https://twitter.com/JaneLytv
In the article you demonstrate how quad-trees are used for indexing spatial data, but does Cockroach DB do this in 3D as well (i.e. octree)?
I was fairly interested in PG Pointcloud [1] back when I was in grad school, but storing arbitrary 3D information seemed to present unique challenges in this space (especially with regards to indexing). Would the approach used here extend to 3D? I don't know if I see a clear reason it wouldn't, but I was wondering if there's anything in Cockroach that might make that extension difficult. I recognize you're using the S2 library here as well, which doesn't seem to have all the 3D primitives, but I'd be interested to hear your thoughts!
Shame though, because among all the Pine devices I have (Pinebook Pro, Pinephone) I've gotten very used to booting from the SD card to swap things out.
Have you written / do you have any links to documentation for how to use fastboot?
It seems fine as a statement piece if you're a big company willing to put your wallet on the line, it means a lot less if you're Purism and you need to stay focused in order to do it. And I will argue again: you could probably do this for vastly cheaper than $1999 even in the States. If anything it hurts this more, since people will look at this as an example and say, "Well, I'm not paying $2000 for something like that, guess USA manufacturing is dead since they can't produce good hardware at reasonable prices."
I don't see any lack of contribution to the mainline kernel or upstream code from either community. The main divergence between the two is the price point and how the communities are run. As for fragmentation, well, if you want a choice in distro, then fragmentation does kind of happen as a result of that.
But overall a lot of the momentum is in the same direction. The biggest sticking point I see happened years ago, when Purism opted to make Phosh + PureOS and make it GNOME based instead of rallying more effort to the UBPorts project. That said, it's free software, so this happens all the time.
(Don't get me wrong though, I really love what Ubuntu Touch has become, and the UBPorts community too!)
Eventually once the software is more refined, there are definitely some features worth adopting for. The kill-switches are a decent feature, and I would love to have something like that on every phone (especially the cam & mic one, since I don't tend to put tape over my phone cameras!).
For the Pinephone, the hope is that one day you'll be able to buy one (or some successor) and be able to load whatever distro you want on it. It's vastly easier to work with than installing a custom bootloader, and then flashing a new version of Android. So as far as that goes, there's a lot to be desired.
I'd also add that just because you don't want to buy Chinese products != Buy USA made products. There are a vast number of other countries that would jump at the notion of becoming your supply chain, and don't necessarily have all the ethical grievances of supporting China.
I actually think my main objection though had nothing to do with "buying Chinese goods" vs. "not buying Chinese goods." Mainly: why would you buy a $2k smartphone that is grossly overpriced and isn't really providing much more than the base model? As the above comment here says, it should really be closer to "few screws inserted in USA" than "Made in USA."
Focus less on presentation, more on content. Write shorter things and ship often. Everyone gets to 20,000 words ~50x within their first million [1].
Just write.
[1] https://twitter.com/patio11/status/1317627674810929152?s=20
We are also at a cross-roads with regards to having a housing crisis. There are many places now (Bay Area, Boulder) where housing is skyrocketing not because the value is naturally increasing, but is instead being artificially inflated due to a shortage in homes. One "radical" solution to this: build more homes.
However, given the amount of labour and time needed to do so, we may not be able to avoid the housing crisis. One way the market is responding is moving to pre-fab construction, and trying to reduce time / costs that way. The article does seem to claim that the projects cost about the same, even if pre-fab is faster in terms of time. This _does_ identify a problem with pre-fab, namely, how come they can't fulfill this promise of being cheaper & faster. Seems strange that you save time but still cost the same when what you're proposing is taking away a significant chunk of higher-skilled labour from the equation.
Some of this is regulatory capture (wasted time / money trying to convince cities of the process), some of this is nascent technology sucking (see top parent comment, sometimes pre-fab doesn't get it right), and some of this seems to just be a lack of experience on behalf of the companies trying to "disrupt" construction.
> should never update a user interface without allowing the previous one to be used as the default
> should always be backwards compatible with previous plug-ins or other third party add ons
Even as a longtime user of Firefox, who lost access to a number of XUL addons once-upon-a-time, I have to disagree.
Some software upgrades cannot be "incremental or bug-fixes only." Sometimes you get handed a pile of hot garbage, and your best chance is to just refactor it. Certainly, you're not aiming to remove features or break workflows, but there exists a world in which some percentage N of users who are affected negatively by a change are not worth the effort of maintaining something. I think this viewpoint ignores that often as software gets more use and grows, our understanding of the problem-space and relevant abstraction grows as well. Black & white statements about what is or isn't allowed by developers in their products regarding updates completely ignores this aspect of development. Granted, if you can choose when to upgrade and to what version to upgrade this is less of an issue. Modern app stores do not function for the user in this respect.
As for the interface being updated: it happens. Sometimes it is worse, but then many times people only complain about things being "worse" because of assimilation bias. There's some fantastic reading about not necessarily catering to power users: https://pdfs.semanticscholar.org/c011/4ca106ff22cf53aaed57d9.... I don't think I would 100% agree with that full article, but a lot of the central premises hold up.
As for killing compatibility with plug-ins or third party add-ons, I am upset by this as anyone but sometimes it needs to happen. Sometimes a breaking bug is abused by a third party for bad reasons as much as they can be for good reasons (e.g. banning add-ons that use exploits to mine bitcoin or data from users, even if the add-on was offering up a useful feature as well).
Now, relating to Firefox's recent Android update that breaks a lot of things, and even their behaviour for deprecating XUL in the past (I'm not referring to how long they gave people to upgrade, which was fair, but rather that some XUL features were never duplicated in webextensions thereby rendering some extensions impossible to reproduce), I would argue that yeah, maybe there is some sense of truth or some imperative that we need heed in the article. However, I think most of this would be mitigated by being able to pin versions, ask for a specific version from a specific date, or rollback. So maybe it's a wash.
To brush off the actions of the police in the US as "not even close to brutal" and "showing remarkable restraint" is beyond callous and demonstrates some pretty bad faith and a lack of empathy on your part. I will remind you that this started over the murder of a man accused of using a fake $20 bill, and __human lives are more important than property__.
That said after locking myself into Spacemacs to use org-mode and org-capture, I always wish there was a way to make org a bit more independent of Emacs, or at least a bit more collaborative. We use Asana at work for tasks / issues / todos and syncing that between my TODO.org and back again can be tiresome when trying to preserve information and context. I'm definitely better at maintaining my org files, but Asana preserves context in a more clean way because people can collaborate and add information to tickets, whereas they can't do that with org files.