I guess I should probably list the problems that I have with microTube:
Why would upload date suggest that it’s date of when it was scrubbed? It’s date of when it was uploaded to youtube. So you can sort by oldest for example.
Gotta suffer for those yuuuutooobs i guess. It’s either python or javascript, searching etc is javascript, loading video is python. The only thing you can do about it is get better cpu
no i will add that, I just have better things to do right now
Awesome! Now this brilliant app works again. Thanks for the update 
Not all videos. Some of them show the upload date of when they were fetched, like when I checked for new videos, I got like 4 videos all uploaded 3 minutes ago, and that’s just impossible.
And I almost forgot about the issue where if on the video info it says that theres 1.1M views for example, then on the main page it will say 11M views.
That’s when microtube cannot fetch the actual upload date, or mostlikely, a bug.
Dude, it’s literally not the device… MicroTube is working fine on the XA2 with Sailfish 5.1. You could say what you meant is that your app was not at fault, which would have been true. But nobody said that your app was buggy in this regard in the first place! Instead, you are stubbornly still insisting the device is at fault, going as far as contradicting yourself in the same message by writing: “jolla recently has made some improvements to streaming […] so that could fix the issue that only exists on xa2”.
Which touches on the crux of the problem: just because an issue manifests only on one device, doesn’t mean the device is at fault. We could delve in the semantics of that, but this could only lead to admitting you’ve used poor wording instead of something more to the point like: “microTube’s special requirements exposes an obscure bug in Jolla’s software stack on the XA2, latest streaming-related improvements might fix that in 5.1.” That would have shown a prior understanding of what the issue was actually related to. Which i suspect was lacking on your part prior to me testing the 5.1 release.
Again, ultimately i don’t care much who’s right or wrong. Have already written on what’s most important for me here. However, i do care when wrong assumptions are publicly made on my thinking or lately even feelings. My actually professionally-qualified answer is that projecting your own insecurities on other people is just immature, @Mister_Magister.
Because the adaptation was fixed, so it is the device aka adaptation for that specific device. end of story.
I use device as an stand in for “device’s sailfishos port” because we’re talking about sailfishos here. It is the device.
Or perhaps you mean to tell me that when some specific device does not support hardware decoding it’s also microtube’s fault? It’s same as if that hardware decoding is not working fully correctly as it was the case with xa2. There’s absolutely nothing to fix on microtube’s side because it’s adaptation’s fault.
That would be a more sensible wording. And it’s true it could be one explanation. But I’m highly skeptic the Jolla guys still work on the XA2 adaptation, 7 years after launching it. Most probably some fixes higher up the software stack had a positive impact on the XA2, like you have already exemplified above, regarding video streaming. So it was almost certainly not the device, even if you use the term to refer to the device’s adaptation.
I’ve exemplified much higher above that Pico Player, among others, always played 1080p60 without hiccups on my device. Even microTube seemed to be using hardware acceleration at all times on my XA2, although video playing was stuttering with Sailfish versions older than 5.1. One hint was that the hiccups were happening even at 480p, which should have been smooth with software decoding. When hardware acceleration for video decoding stopped working on my XA2 in the native browser, it was very noticeable, and I’ve reported it upstream. This wasn’t the case here.
So i tried fetching autogenerated subitles, problem is that the URL returns error and not subtitles so it seems it’s currently broken in yt-dlp 
if yt-dlp fixes it then i’ll add the option
Did you create an issue in their repo?
I’m not that invested in it