

Some version of Ubuntu around the time they were doing the Ubuntu phone
Some version of Ubuntu around the time they were doing the Ubuntu phone
I stopped wearing pants almost a decade ago. Joggers & sweats have taken over lol
This is beautiful, and a perfect example post you used there. I know it’s not a release but it makes me wish I had an Android phone to test it anyway lol
The perfect Apollo 1:1 wefwef migration dream is dead then. That sucks.
DNS is what translates www.website.com into an IP address that allow clients to load content from those websites. Most people use the DNS that come with their ISP. NextDNS is an alternate “translator” with built in Firewall/Adblock options (like a Pi-Hole). I figured after the Clear Safari Data trick didn’t work for me, it was because of NextDNS blocking something that required wepwep to function. I think it was related to that CORS and wepwep proxy thing that was fixed a while ago, but I switched it back on after reinstalling wepwep and it’s all good!
For me, it was because I had NextDNS enabled but it worked fine with it on up until now. Wonder what happened. Replying from iOS.
I wouldn’t say left behind, wefwef has the best UI/UX through it’s Apollo DNA. I believe it will catch up once the App Store version releases.
Seal the doors! Mark/Meta’s obsession over user base and data control has to be put in check. They’re like a social culture vulture. Riding the next wave but the attempt ends up being stale, killing the mood for everyone that just wanted to enjoy something to themselves.
By “game-changer”, I meant in the sense of having the most functional lemmy client with the best UI in the App Store so soon after what happened to Apollo. PWAs are cool (good for small startups, less cost, faster update deployment, cross-platform thru web-browser engine), but they can’t or don’t leverage the strengths of the hardware/platform they run on to achieve that without a wrapper or native code. Spotify is a PWA, for example. I just logged into mobile Spotify and most of the core functionality is there, but the experience is better using the native app from the App Store. (I can’t even view my Library with mobile Spotify) Scrolling is buttery smooth, animations for transitions instead of sudden “pop-ins” and “pop-outs” or loading a page (like a web browser). Same with Twitter, or a majority of sites/services with an already established app. There’s a reason they all push you to use the native app instead of the web-browser version. It’s just better, and wefwef can only benefit from it. As a PWA, it’s a good solution until it’s mature enough to be native.
I just drag the homebar up a little and it’s back to normal
If that’s the case, apps may as well not exist. But apps still get made, because the world doesn’t work that way.
If this becomes a native iOS app, it would be a game-changer!
Took them long enough, they know they were wrong for that