Agreed, I happened to just make this mockup chronicling my journey through screen sizes. I loved the HTC One m7, the pixel 2 despite being a bit larger was still comfortable because it still has a “chin” at the bottom. I thought going to the pixel 5 would be fine and I chose it because it’s within ~1mm of the same body dimensions, but I forgot to account for the screen going all the way to the top/bottom - trying to press the back button at the bottom of the screen with 1 hand is so much more of a stretch and it sometimes makes my hand sore. Given that I’ve had the P5 for a while and my hand still hasn’t adjusted I just can’t go to a bigger phone, especially since the P5’s increased height over the 2 lower screen bottom compared to the P2 makes it want to flip backwards out of my hand when I’m trying to reach down to the back button. At a minimum I need my next phone to be same or smaller than the P5.

(Comparison: https://i.imgur.com/gAc306o.png )

That said, I get that FP wants to make a repairable phone that appeals to the masses, and it might hurt that mission to cater to a specific crowd instead of competing with the veritable hand-tablets that other companies are producing. I just hope that they grow large enough to be able to make a “Luddite” version though with a non-cramp-inducing size and a headphone jack. I don’t care either way about headphone jacks but I feel like there’s a lot of overlap between the crowds that want smaller phones and people who want headphone jacks.

I was curious and tried that on my Samsung TV from 2016, it loads a grey background and does nothing

The color of the bubble is only important because it helps iPhone users know who not to add to group chats, since the presence of a non-imessage user in an iMessage group chat downgrades the entire chat to grainy photos, no reactions/ read receipts, voice memos, typing indicators, etc. I don’t blame them at all, many of them don’t use any third party messaging apps because iMessage is built in and gives them everything that other chat apps have, with the benefit that they don’t have to convince anybody to install it because all their iPhone owning friends have it preinstalled.

Essentially yes, the Chromecast ultra is basically a more powerful Chromecast 2 that supports 4K (maybe other differences too but idk). I’ve stuck with the ultra because the next upgrade is one of the Chromecast “with Google TV”, which while is nice that you can install / side load apps like SmartTubeNext it also means you get a dedicated remote (I hate having more remotes) and it also has a launcher, which I think is more likely to get ads added to it (not sure if it already does by default or not) compared to the older CC2 / CCUltra which just has a “backdrop” photo slideshow and no launcher UI.

That’s where all the good pirated content comes from

You can’t cast to Chromecast (non-googleTV if that matters) from Firefox mobile, also pull to refresh doesn’t work in browser, and they dont support push notifications for uploads. Revanced works great so I see no reason to switch, and it’s based off of the official YouTube APK so you’re only logging into Google play services, and you get the same native app experience you’re used to with all the addons you’d get from browser extensions built in (adblock, shorts block, sponsorblock, return dislike, background play, etc.)

I don’t think there’s anything that YT in Firefox mobile can do that revanced can’t, but revanced gives you cast support (through the official cast shim that supports CEC for pause, play, stop using the TV remote unlike doing screen mirroring of your phone where you can’t use your phone for anything else while mirroring) and other niceties like notifications and one tap to newpipe player / download video file through newpipe. It’s only a benefit to use revanced over the mobile web.

Doesn’t jellyfin still lack auto detecting hardware acceleration settings? Setting up quicksync transcode in Plex meant just mapping /dev/dri and checking use hw acceleration + use hw accelerated encoding and it just works. In jellyfin, according to the documentation (I mean just look at the size of that page… I’ve spent hours poring over every section trying to get my setup to work), you have to pass in the render group id in addition to passing /dev/dri, run a command inside the container to check capabilities, then it just says to “enable qsv and uncheck unsupported codecs” without any guidance on how to match the output of the command with the codec list. I kept getting playback errors so I resorted to using the Linux server docker container and referencing the Wikipedia page for quicksync to enable the codecs my CPU should be able to handle with quicksync.

They sorely need to make it just work out of the box with a single enable check box and have the rest of the settings auto detected and hidden under advanced. At least it should add (not present) or grey out every hardware acceleration device not detected like amd/nvidia on my nuc that’s just Intel, and the codecs should just auto set based on your hardware and show a warning if you enable something outside of the detected capabilities. I still can’t get opencl tone mapping to work despite having the opencl linuxserver mod so I’ve just resorted to VPP, my jellyfin users can just deal with it if it doesn’t look quite right.

If they seamlessly integrate iMessage features with rcs then I would call it solved

ie if iPhone users can react to messages, include rcs users in group chats with iMessage users and all share HQ photos, send voice memos, and whatever else without missing any of the features because the other person is rcs or because one rcs person in a group chat causes the entire group chat to be downgraded, then the only remaining difference is the color of the bubble so the only people hating on green bubbles will be those who do it solely because of the color and not because of any loss of functionality, which I think would be so few people that it would be a non issue

It’s not just about the color of the bubble. If you go on an outing with a group of iPhone users, there’s a high chance they’ll create a group chat with and without you, because the group chat with you won’t let them send HQ photos. Even if they aren’t trying to be exclusionary, someone will inevitably forget to send messages to both group chats. iMessage incentivizes situations like this which socially punishes Android users.