18358414

I have an android device that I have basically said "this never connects to google", and I've installed everything by APK thus far.  I ran into some issues when I came across Floatplane and a few other packages which just don't seem to provide a direct APK download through official sources.  Xournal++ offers the APK directly on their gitlab site for example (as do most of the other open source goodies I wanted to install). 
 
With floatplane specifically, I feel like this is an oversight because some of its users (myself included) want to use it to get away from Google... and yet to install it you need a Google account because you can't access the play store without an account. 
 
So is there some restriction in the developer agreement that stops people from just providing the APK directly?  What about people who use amazon tablets and need an apk to install their applications?
 
And yes, I'm aware of APK mirrors.  I'd rather install something provided by the developers because there's at least some trust there. 
 
edit: I'm talking more about established projects, not small-timers who make one app for android and that's it (Xournal++ is the smallest dev group I've installed from).
 
edit2: I don't have time for this; I've asked that this post be deleted as I've no intention to respond to any of you.

This has been discussed to death. 
 
 
 
 
 
1. There is no reason to believe Anthony would even want to do this, compared to his current role at LMG
2. There is no evidence to believe that a Linux channel would get enough viewership to be profitable for LMG
3. There is never anything cited that the many existing Linux-devoted YT channels are failing to bring to the table to create a "need" for LMG to enter this space

"The only winning move is not to play."

Don't know what error message Linus specifically got, 'nor do I know what packages he had installed when he tried running 'apt get' so I can't say whether there was an autocompletion (eg: pkgfile) tool trying to "help", but you can install apt on arch via the AUR: https://aur.archlinux.org/packages/apt
 
But it doesn't even have to search aur; here's what pkgfile's 'command-not-found.bash' hook returns when you just type 'apt':
 
apt may be found in the following packages: extra/jdk7-openjdk 7.u261_2.6.22-1 /usr/lib/jvm/java-7-openjdk/bin/apt If I didn't already know that this wasn't the debian package manager, I might reasonably assume that installing this "dependency" would provide 'apt'. 

It looks like Ubuntu is trying to find a network time server but isn't getting anything.  You could try disabling ntp with
sudo timedatectl set-ntp 0 or
sudo systemctl stop systemd-timesyncd but it might be necessary to restart the ubuntu install process and when you get to the "select a timezone" screen make sure the 'ntp' checkbox is not checked. 

Could you open up a terminal and type 'sudo timedatectl status' and post the output of that command here?

Potato is only real food.

Potato is only real food.

My parents have a robot vacuum cleaner which runs an embedded Linux kernel.  So yes, Linux does literally suck. 
 
As a desktop operating system, it's a perfectly usable environment provided you take the time to learn it.  People today do not know how to use a computer.  They know how to use Windows, or the know how to use MacOS, or they know how to use whatever else they use on a daily basis.  I see people who assume they're experts just because they know the ins and outs of Windows, and then they blame Linux when they are unable to figure out how to change network settings.  I have an old book about "mastering Windows 3.1"; if I learned that and only that I'd probably be raging at Microsoft for making everything so different and confusing for Windows 10.  An analogy might be: "if you know how to play the guitar, that doesn't mean you know how to play all stringed instruments".  Any operating system requires you to learn how the individual operating system does things.  And yes, there are some things that you simply cannot do.  This is true for all OS platforms. 
 
Gaming adds another layer of complexity.  Going back to the musical analogy, if you try to play the piano accompaniment of Kreisler's "Liebesleid" on the guitar, you'll have a hard time (because the way the two instruments operate are very different).  If you take a music sheet ("game") that's written for the piano ("Windows") and try to make it sound the same on a pipe organ ("Linux"), there's going to be a few challenges (especially if it requires all 88 keys).  It's entirely possible that you could make it work, but whether you can do so with ease depends on the specific game and how well it can adapt to the different underlying system. 
 
Gaming is certainly not impossible on Linux.  If you play games that were developed with native Linux support then it works great.  If you ask a game written for Windows to run on a different base system with different system calls, then you have challenges.  At that point you're not gaming, you're attempting to facilitate a computer program in a nonstandard way.  The biggest problem faced with Linux is that it is a truly open platform, meaning that depending on the author of your particular distro the "right way" to do something can be completely different from the "right way" to do something on another distro.  While Windows and MacOS (IMO) both have a crap way of doing things, they've standardized their crap and can therefore offer consistent advice across their respective ecosystems.  This is why I recommend people to take their time rather than "taking the plunge".  With Linux, you need to be flexible to some extent.  Dual boot if you have to, or run Linux in a VM and tell yourself "I'll only go back to Windows if I'm absolutely stuck". 
 
Huh... this reply of mine started off making some sense, but I appear to have gotten distracted half way through LOL.

My parents have a robot vacuum cleaner which runs an embedded Linux kernel.  So yes, Linux does literally suck. 
 
As a desktop operating system, it's a perfectly usable environment provided you take the time to learn it.  People today do not know how to use a computer.  They know how to use Windows, or the know how to use MacOS, or they know how to use whatever else they use on a daily basis.  I see people who assume they're experts just because they know the ins and outs of Windows, and then they blame Linux when they are unable to figure out how to change network settings.  I have an old book about "mastering Windows 3.1"; if I learned that and only that I'd probably be raging at Microsoft for making everything so different and confusing for Windows 10.  An analogy might be: "if you know how to play the guitar, that doesn't mean you know how to play all stringed instruments".  Any operating system requires you to learn how the individual operating system does things.  And yes, there are some things that you simply cannot do.  This is true for all OS platforms. 
 
Gaming adds another layer of complexity.  Going back to the musical analogy, if you try to play the piano accompaniment of Kreisler's "Liebesleid" on the guitar, you'll have a hard time (because the way the two instruments operate are very different).  If you take a music sheet ("game") that's written for the piano ("Windows") and try to make it sound the same on a pipe organ ("Linux"), there's going to be a few challenges (especially if it requires all 88 keys).  It's entirely possible that you could make it work, but whether you can do so with ease depends on the specific game and how well it can adapt to the different underlying system. 
 
Gaming is certainly not impossible on Linux.  If you play games that were developed with native Linux support then it works great.  If you ask a game written for Windows to run on a different base system with different system calls, then you have challenges.  At that point you're not gaming, you're attempting to facilitate a computer program in a nonstandard way.  The biggest problem faced with Linux is that it is a truly open platform, meaning that depending on the author of your particular distro the "right way" to do something can be completely different from the "right way" to do something on another distro.  While Windows and MacOS (IMO) both have a crap way of doing things, they've standardized their crap and can therefore offer consistent advice across their respective ecosystems.  This is why I recommend people to take their time rather than "taking the plunge".  With Linux, you need to be flexible to some extent.  Dual boot if you have to, or run Linux in a VM and tell yourself "I'll only go back to Windows if I'm absolutely stuck". 
 
Huh... this reply of mine started off making some sense, but I appear to have gotten distracted half way through LOL.

I suppose if we normalize the concept of video games requiring kernel-level access then more users will feel comfortable allowing software to access kernel-level resources; then all the work Microsoft put in to making Windows secure goes bye-bye because users have gotten used to blasting away any userspace protections. 
 
Imagine a non-techsavvy user who sees on an OFFICIAL website that "anti-cheat software requires kernel level access"; then they see free random game on the internet and this game asks for kernel-level access.  User has been conditioned to accept that term because they're used to seeing it with official software.  User now has kernel-level bitcoin miner and keylogger. 

I suppose if we normalize the concept of video games requiring kernel-level access then more users will feel comfortable allowing software to access kernel-level resources; then all the work Microsoft put in to making Windows secure goes bye-bye because users have gotten used to blasting away any userspace protections. 
 
Imagine a non-techsavvy user who sees on an OFFICIAL website that "anti-cheat software requires kernel level access"; then they see free random game on the internet and this game asks for kernel-level access.  User has been conditioned to accept that term because they're used to seeing it with official software.  User now has kernel-level bitcoin miner and keylogger. 

"This could be the year of the Linux desktop!"
 
I did the switch from Windows to Linux in 2007.  Recently I did the switch back to see what the experience was like, and it was AWEFUL. Windows is just terrible in so many ways (and yet, since they've standardized crappiness, it's easy to get support as everyone has the same mud on their boots).  So a category for "Windows to <not windows>" doesn't make much sense in my mind, because it's more a factor of "<some OS> to <some other OS>" that's the heart of the issue (it could just as well be "Windows to BSD" or "Windows to MacOS" or "Windows to TempleOS (the only way to go)").  I feel like the whole issue isn't "which is better", but more "how do I learn to use something different".  As an example, my cousin has NO IDEA how to use a keyboard and mouse, because he's only ever used a touchscreen interface; I could say he daily drives Linux (android), but the switch from "mobile Linux to desktop Linux" for him would be just as hard as "mobile Linux to desktop Windows". 

100wpm with 99% accuracy according to 'monkeytype'... but that's completely irrelevant because if I know what I'm trying to type I generally get 150wpm (for example, if I'm typing a coherent sentence rather than a randomly generated string). 

I hate the modern context of the word "phone".  "Oh, I'll look that up on my phone", or "I have [insert game name] on my phone".  A phone is a device used to TALK to people.  It is a sound-transmitting device, hence the word "phone" (like xylophone, or microphone; it deals with SOUND).  If it's a hand-held computer, call it what it is.  How often are these things used for calling, anyway?  If it's less than 50% of the user interaction time, then IT'S NOT A PHONE.
 
It's a hand-held computer with a phone built in.  You're not using the phone part if you're not calling someone (maybe you're using a wireless modem for data transmission, but that's a different thing).

I hate the modern context of the word "phone".  "Oh, I'll look that up on my phone", or "I have [insert game name] on my phone".  A phone is a device used to TALK to people.  It is a sound-transmitting device, hence the word "phone" (like xylophone, or microphone; it deals with SOUND).  If it's a hand-held computer, call it what it is.  How often are these things used for calling, anyway?  If it's less than 50% of the user interaction time, then IT'S NOT A PHONE.
 
It's a hand-held computer with a phone built in.  You're not using the phone part if you're not calling someone (maybe you're using a wireless modem for data transmission, but that's a different thing).

It was cancelled in Canada due to covid.

An IP address isn't a person, so it's likely that they're just saying the region associated with the IP address doesn't match.  I've had my IP change 20 times in an hour due to an unstable DSL connection.  The last time I got locked out I managed to get around it by using a VPN to make my IP address relatively constant. 
 
Another thing I noticed is that google might not actually find the login attempt suspicious, they might just not like the fact that they are lacking certain information about you.  An example of this is a cell phone number, which really doesn't verify that you are who you say you are in the first place.
 
I once (and yes, this has happened to me on multiple occasions with gmail) managed to get my email back by pairing my email to a co-worker's android phone to confirm "my" identity.  It may also help if you've specified a recovery email address.  If your gmail account is more than 14 years old, you may also have some "emergency login codes" kicking around. 
 
edit: another quirk is that if you fail login so many times, gmail will tell you to "log in again later" which basically means don't try to touch your account for 1 week and then when you try again they won't care if it's really you anymore.  Not sure if it works, but people seem to recommend it.

Unpopular #1: I should be able to receive a cheque from online freelance/gig job websites for my services rather than having to sign up for PayPal or payoneer or whatever other payment system that wants to screw me over.
 
Unpopular #2: I should be allowed to purchase items online by mailing in cash directly.  My credit card never changes, no matter how much I complain, so it's completely insecure to use the same number over-and-over for websites that really don't care about you if it gets stolen. 
 
Unpopular C: And why do I need a cell phone to "verify my identity" on my gmail account?  Since when does email require a cell phone?  And how does a cell phone verify that it's even me in the first place when I can buy a burner on the street corner?  I thought that NOT needing analogue hardware was the big reason for using email in the first place.
 
Unpopular (iv): Analogue is spelled with a "ue", colour has a 'u' in it, 'z' is pronounced 'zed', and I like tofu on pizza.
 
Everything I hate about online economies is described by the adage of the man who goes to the local pub to frequently play a blatantly rigged game of poker.  I know the system is rigged against me, but danged if it isn't the only game in town. 

In high school I completed the curriculum for computer science about 3 months ahead of schedule.  So me and the guy next to me just messed around with the CD-ROM drive on the computer.  We crammed like $20 in spare change into that thing before it gave up the ghost. 

In high school I completed the curriculum for computer science about 3 months ahead of schedule.  So me and the guy next to me just messed around with the CD-ROM drive on the computer.  We crammed like $20 in spare change into that thing before it gave up the ghost. 

Don't know if y'all like hard drives, but I plugged this thing in yesterday in search of some old documents and the thing still works perfectly.  Booted Windows 3.1 in dosbox. 

Don't know if y'all like hard drives, but I plugged this thing in yesterday in search of some old documents and the thing still works perfectly.  Booted Windows 3.1 in dosbox. 

When I was putting my current build together, I cut my thumb and spilled a lot of **R** on the case.  It was upsetting, because that was the case I spent my hard-earned **G** on.  When I went to start the computer for the first time, I held my breath waiting for that first POST and ended up turning **B** because I forgot the power to the GPU. 
 
That's my story of R, G, and B. 

When I was putting my current build together, I cut my thumb and spilled a lot of **R** on the case.  It was upsetting, because that was the case I spent my hard-earned **G** on.  When I went to start the computer for the first time, I held my breath waiting for that first POST and ended up turning **B** because I forgot the power to the GPU. 
 
That's my story of R, G, and B.