https://peertube.co.uk/videos/watch/55eece8c-2d6c-4da3-8c8c-...
This prototype version is definitely not ready for mass market due to (1) known overheating issue (so far I've observed it get quite warm sometimes, but not uncomfortably hot), (2) a bunch little software things to work on. But it's really exciting to be able to `ls` and `cd` and `ssh` on a phone, and know that the software updates are coming.
Purism's accomplishment already is pretty incredible on both a hardware and software level. For me, well worth the price. Congrats to them even if there is a ways to go yet.
Can't you do that on any other Android phone with terminal software installed?
Modern Android has been locking down access to everything that isn't an NDK public API.
Can you boot to a shell without starting GNOME?
I'm so fed up with software that tries to anticipate what I want. Computers running Linux do what you ask in spite of what you want, but phones running modern phone operating systems do what they think you want in spite of what you need. And that is deeply frustrating to power users.
I guess now I just need to decide when to jump into this.
It's strange that SailfishOS has not caught more marketshare on the hacker/tech enthusiast community, because it's (almost) everything people wants about Purism : you lose a bit in the free software and open hardware side, but you win in terms of price (used phone + 50$ license), availability and usability (Right now, it's the only alternative to Android and iOS I can safely recommend).
If only Jolla devs had kept their promises of open-sourcing more of their code.
https://developer.android.com/ndk/guides/stable_apis
Given the changes started with Android 7 to block access to everything else?
In fact, https://wiki.termux.com/wiki/Differences_from_Linux
I think that's a big part of the answer to why it hasn't caught among techies. When I tried using it (shortly after release), there were numerous issues in their default apps that nobody could fix because they are proprietary and Jolla didn't seem to have the resources to handle all the bugs.
I'd wager that if it had been open source, the early adopters would have put some time in to fix a lot of the bugs.
In retrospect I'm pretty pissed at them for not being honest and upholding their promises. In my book they're basically con artists that just tried to get the Linux community's money by saying "open source" without actually meaning it.
It's quicker than any of the YouTube downloader apps I've tried!
How it works: in ~/bin there's a termux-url-opener script that handles what you share:
"#!/bin/bash
case "$1" in
*youtu*)
echo "$1 is a YouTube URL,
downloading"
sh ~/shortcuts/dl_yt.sh $1
..."I love it and am still finding new uses for Termux. I've got neovim and all my dotfiles loaded, so in a pinch I can ssh into my phone to do some work.
I later switched to Ubuntu Touch because, despite Canonical picking up the project, the community had continued maintaining it. They could do that because it was freely licensed; nobody could do that for Sailfish.
The best part is that I don't really need to trust Purism, I can choose to trust the community instead to whistleblow if Purism breaks the community's trust. Their target demographic is exactly the type that will be watching over their shoulder to make sure nothing fishy is going on.
> sudo systemctl disable phosh.service
Or something like that. I'm sure it would be pretty easy with a bit of fiddling. However, you're right that you'd probably need a keyboard plugged in because the default TTY probably doesn't have a soft keyboard.
Google is like a feudal lord. In exchange for owning you, they'll protect you from everyone weaker than they are. Google doesn't want to break into your office computer as long as they can shovel ads down your throat. And their reputation for security is much higher than a small startup regardless of the startup's competence and intentions. See e.g. Project Zero or Chrome vulnerabilities vs Firefox.
I suspect the issue is that PeerTube is getting a NAT IP instead of properly determining its own external IP, which is causing problems streaming when it tries to get back to the origin. I'm pretty sure it's a simple enough fix, I just need to take a look at it in the light of day.
Not all security mind you, Android runs on ancient kernel and it won't be changing for a long time even though Google announced plans for moving to mainline linux.
youtube-dl -f bestaudio -x --no-progress -o "~/storage/music/YouTube/%(title)s.%(ext)s" "$1"
This generally gives me .opus files, which play OK but my player can't change the tags.