7heo

Because everyone knows google publicly shows all the metrics they use for ranking, verbatim... Were it my channel, I'd bleep it or voice over it in post and re-upload just to be sure.

Dear LMG team and dear James, at 00:33 in the video, I am sure you meant to say "La pièce de résistance", but the way you pronounced it, it said "La pisse de résistance", which translates as "the main piss" instead of "the main part". I am reporting it as it might have some effect on the algorithmic ranking, if google's machine learning speech to text algorithm is advanced enough to handle multiple languages in one sentence. Not sure if this will have an incidence but I thought you should know. Thanks for the great content!

Who said it's his home address? That would be a good way of getting back at someone.

@LAwLz, if you keep up with your passive-aggressive and also insulting behavior, I will simply ignore you. Strawman/gaslighting (I initially assumed it was unintentional, but in the light of the rest of your post, I'm not so sure). Those users were never the ones targeted by this thread. Clearly Floatplane thinks otherwise, since they invested development time into fixing a bug triggered by an "edge case" use of their app. Those users were never the ones targeted by this thread. Security vs convenience. From a security point of view, automatic updates are madness. Even from a usability point of view. How will you ever know an update caused a crash if you don't know of the updates? Automagic behaviors are harmful, no matter how many people are gaslit/brainwashed into liking them. No. Especially considering that LTT does a thorough job, and will surely never miss mentioning that fact in the video. Maybe here is the problem with the current thread. I don't think enough people participating to this thread have the context. The context is the WAN Show from December the 17th. You should watch it if you want to understand why this thread exists. Ad hominem. I will refrain from insulting you, but know it is only to comply with the forum's etiquette, the intent is fully there. Since I'm just a "hobbyist", I won't even take the time to answer your invalid objections. Thanks but no thanks. What personal benefit do you stand to gain by defending Google? How do you know Floatplane have not been using the "tools Google provide them with"? Especially if you did not have the context... You look more and more like an extreme Google fanboy... You related unrelated statements. It's on you, not on me. Please stop. Out of rational points, are you? Well, maybe stop trying to "be right", then. This does not forcibly close. It does not perform a `kill -6`, `kill -9` or `kill -15` call on the processes. Then give us an issue tracker, I'll gladly go there instead. I have absolutely no interest or will to discuss this with you. I only answer here so that if the Floatplane team ever reads this, they do not only get a heavily one-sided (and questionable) point of view from people who somehow are "against this" (everyone has an opinion, and we must all share it with the world, yay!). No, but at this point, I'm not even going to try understanding where you got that idea. That was before you were all insulting and arrogant. Then please do. Thanks.

I mean, it goes against the "do not reinvent the wheel" principle, but sure; it's not that hard. It will however cost much more to implement than the few hundred bucks of developer/engineer time required to serve an f-droid repo. It will also need more time. And it can be done poorly, too, if the developers aren't careful. All in all, it is a good long term solution, and it is definitely easier for the user than using any F-Droid repo. But the Floatplane team will have to make sure it is done properly, and maintain it.

That's about all you wanted to hear. Literally only one user on a forum is writing unsubstantiated claims based on their own personal opinion, and that is enough for you to make up your mind? My personal opinion (and I would guess, @kumicota's as well) is that F-Droid is very usable. it does what it says on the tin (gives you an app catalog, installs apps, and notifies you of updates at the configured frequency), I never witnessed it crashing a single time, it gives access to plenty of alternatives for AOSP smartphones, and the only feature I wish I could have is reviews. But I value not having to create an account more than the possibility to review apps. How about you give it a try, without going in with a bias, assuming the experience is going to suck?

That was not from Linus. It was the thread I linked, that I started, half a year ago. Check my first post in the current thread for the link. Not true. You said more than that. You said "Asking the average user to install F-Droid is asking a lot". For one, I don't think LTT viewers (and at large, the Floatplane user base) are "average" in that context. They are very likely on the technically savvy end. Then, even if they were, F-Droid is not aimed at that "average user", but at the people who still wish to have access to the Floatplane platform, and are willing to put a little more effort into it, for the sake of having it work now. Now if you still genuinely wonder why we understood that you implied our idea was for F-Droid to be the only app store distributing the Floatplane app, this is it. Your assumption that "average" users will have to do it. Your implication that only "automatic updates" matter. There is literally no way for "average" users to ever hear of this problem in the first place, unless the Floatplane app completely moves to F-Droid (which, again, to be perfectly clear, isn't what we discussed). And the people who are concerned by this problem would likely shiver to the idea of automatic, un-reviewed updates. We are missing the main point here: people who trigger the current bug are people who receive app notifications while the app is forcibly closed. So the use case triggering the bug is not the one of your average user. That use case is literally the use case of someone for who installing F-Droid is nothing more than "Alright, hold my beer, gimme 2 minutes". This matters. There is a benefit. See below. The work you speak of is trivial to automatize. It would take a skilled engineer about 1h to do, maybe a couple with testing and proper git history. Heck, I already made an XML index file, it literally took me a dozen minutes. Ok, I did not know of that "feature" of Android 12. I can not see anything ever going wrong with that... I also don't see how this is relevant, as people will install updates as they always did, automatic or not. With the F-Droid store, yes. With the Aurora store, assuming the Floatplane team contacted the Aurora developers to get their repo address included in the default list, nope. It then only requires the user to tick a checkbox. That is all. It is a huge benefit for Floatplane in the light of the current situation. It gives an alternative distribution channel, in case, you know, the alternative video platform encounters further resistance from Google in the future. It is also a benefit for some of the LTT users. Technical users who use de-googleified smartphones (FWIW) now have to jump through hoops in order to use the Floatplane app, and that problem has a very easy solution. Again, I am genuinely shocked (not my first time discussing this topic) at the amount of resistance from people who have absolutely NOTHING to do with the problem at hand. Can you not let a few people with an idea and a potential solution to a current problem propose that solution to Floatplane? Or are you that afraid of using F-Droid ever that the sheer idea of someone else using it disturbs you? To make it completely clear: we are not talking about the LTT audience here. We are talking about the Floatplane audience, and even, to be perfectly precise, the subset of the Floatplane audience who happens to forcibly close the Floatplane app when they do not use it. It implies either the use of dedicated software, or the knowledge about processes life cycle. This isn't your average LTT viewer, by a long shot. Yes, we can agree on that. And that subset of people is very likely the exact same subset that has been encountering the crashes. Or, to be precise, the people encountering the crashes are a subset of that "handful of people". I hope you understand better why we are trying to get the attention of the Floatplane staff, by now. * * * All in all, I see a lot of noise from people who give their opinion to no end (really, what's your point here? Aimlessly debating anything online? Ensuring you drown that potential helpful request - to some - in so much noise the Floatplane team never ever hears of it?), but I still have to see a participation from a Floatplane staffer, let alone from Luke (I know, right now, it's Christmas, and everyone is with their families; but I also posted a very similar topic half a year ago, and the Floatplane team is very likely unaware of it even now). If you are against the idea, unless you are Floatplane staff, you aren't helping. The whole idea of this thread is to propose a solution to Floatplane since there is no other way to reach them; not to discuss with literally everyone on this forum who disagrees. Thanks.

Plus, the Aurora Droid app you mentioned is definitely more user friendly than the stock F-Droid. So much so that if the Floatplane team contacts the Aurora devs, they very likely be able to make the set-up process a "checkbox" only, after installing the Aurora Droid app store.

While running? No. Laptop hard-drives have protections so that the heads don't scratch the plates when movement is detected and the drive is in use, but with SSDs, that has become a lesser problem. Just don't run when your HDD is in use, unless it is a life/death situation. Buy a big external SSD and you'll be fine.

Nobody ever talked about a complete, definitive replacement. It is only about providing an alternative, as in "not putting all your eggs in the same basket" (especially when that basket is held by someone who has/could very well have a vested interest in seeing you fail). I don't see the point of your answer; you are not providing a solution, only non-constructive criticism, and your post borders on being a strawman (again, no one ever talked about a replacement). Also, do you care to elaborate on that "Android 12 only F-Droid automatic updates" bit? I use solely F-Droid, with android 9, and I get updates every day. Edit: While you're at it, can you please tell us how using F-Droid is "asking a lot" in comparison to the APK download and side-loading solution Linus proposed? I'm genuinely curious.

Yeah, I guessed as much What puzzles me is OP's claim that the card is impossible to remove, while they "removed all the screws". Also that and it not being connected to the motherboard ever, in any way... Since the photos are close-ups, it's hard to tell...

Printers using LPT only use one parallel port, this card has two (one male, one female). I'm guessing it is a controller card for a driving simulation seat/controls.

What if you remove the second screw? Does it move? How is it connected to the motherboard? Via the USB header(? or is the the HD Audio header?) on the left of the first photo? We can't really see where that cable goes.

Not exactly no. That WAN Show episode is linked directly at the top of the topic I linked in my post above (in the first line of the first post of that linked topic), and in it, they just assumed downloading a bare APK from a "trusted APK site" (sic) and sideloading it was strictly equivalent to using F-Droid; and then proceeded to ask someone who could not respond why they "wouldn't just get it on the Google Play store" or would not "just sideload" it. At no moment in this very brief answer (literally just one minute long) they addressed the question, aside from Linus's confession that publishing the app on F-Droid never occurred to him. Transcript is as follows (the timestamped link to the video is at the top of my other topic, as I already said): Now, using F-Droid via the official F-Droid repositories would be properly impossible in the current state (with the closed source app), and this has also been discussed in my other topic. But the current topic is about using a custom, LMG/Floatplane/LTT administered repository that users could very simply (and safely) add to their F-Droid sources. Then we would get all the benefits of using a package manager (what "app stores" really are) without the drawbacks of everyone having to abide by Google's (potentially problematic - as illustrated by the situation described by Luke in the December 17 WAN Show) rules. To be fair, in the light of the current situation, I would have already made an F-Droid repo earlier this week myself, if I had the apk file. But it's only available to the Floatplane team and Google, at the moment, so no-one can get it.

I'm glad I found this post, I was writing what was essentially a duplicate. Below is the first post of the thread I would have created. I personally think the current "setback" Floatplane suffers isn't fully random. I think Google was completely unaware of what Floatplane is prior to the application bug, and that the bug, causing a sudden change in performance (be it technical performance or review performance), got the attention of Google, one way or another. Now, I don't think this goes very high up the chain of command, but it is my opinion that the extra dozen of hoops Luke had to jump through are related to the nature of Floatplane, and the potential competition. I know, that is an opinion, and I have absolutely nothing to back it up; but there is nothing to disprove it either. Now, to the point: Luke said on the WAN show that he does not want side-loading of the app, as it would disable it from being auto-updated by the Play store. While bare side-loading would indeed cause that, there is another solution: the f-droid store. I know, I know, I (among other people) already suggested that, and it has been discussed (erroneously, see below) and rejected (also erroneously). Now, there are two new facts that change the outcome: Even if I'm wrong in the preamble, depending on a corporation you plan to compete against is just a bad idea. It's just a matter of time before you represent a tangible threat (if you do not already, in their eyes; startups have been known to suddenly "explode" in popularity before), and before it is in their best interest to find legal or technical grounds to make the life of the Floatplane team a misery, or maybe even a living hell. I totally forgot to mention (because I seldom use that feature) the possibility @kumicota mentioned in their post: f-droid allows people (anyone really) to publish repositories, along with a fingerprint. You can publish that fingerprint on a different channel (or better, read out in a video), to ensure legitimacy. I believe those two facts make it rationally a rather high priority for Floatplane to release their app over a Floatplane/LTT/LMG controlled "f-droid" repository (technically an http/https (preferably) URL that just serves the APK(s)). It is a very minimal amount of work (you already have the APK, you already have servers, you already have HTTP daemons running - the only work here is to make a new CNAME record, reconfigure the HTTPd the CNAME is pointed at to serve that subdomain, and copy the APK under its root path, along with the metadata XML index and an HTML index file. That HTML index file could contain a QR Code to scan the repository URL, its fingerprint, and possibly the URL of the video containing the read-out version of that fingerprint). Edit: I attached an index.xml file in case the floatplane team wants to re-use it. It needs 8 fields to be edited, all marked with `XXX`. You might also want to change the version numbers, as I pulled them from the Play store, so they probably reflect the version of the buggy APK. HTH. index.xml