python

I'd give laser pointers to Neanderthals. Even if they did figure out some useful application for them (maybe hunting?) they'd run out of batteries eventually.

On a touchscreen !!
Within a pan-pinch resizeable container !!
With a weirdly-shaped Grid !!

(Didn't know where else to post this, since it doesn't seem very relevant to !webdev@programming.dev, but I needed to exclaim this somewhere haha)

Hello! I'm messing around with some PWA features and getting really stuck when it comes to display modes. Basically every browser and device I test on behaves wildly differently, and I'm having a hard time distinguishing which of those behaviors are errors on my part and which are just browser funkiness.

(Link to my PWA if you want to check the manifest or see how it displays for you)

In my manifest, I try to set the display mode to fullscreen. This setting seems to only be properly and consistently applied when I test on my Lenovo Tab 11 running Chrome. Firefox on the same tablet does not respect it and starts in standalone mode, unless I also have the Chrome Version of the PWA installed. Once that is the case, Firefox is beautiful and consistent. I have no idea why the different versions installed by the different browsers would interact with each other like this.

When I install the PWA on my phone (Pixel 9 Pro running GrapheneOS), via Chrome or Vanadium, the site thinks it's running in fullscreen, but I still have a black bar at the top (it doesn't apply the theme color set in the manifest!). This wouldn't be a problem per se, but the browser also sets a safe-area-inset parameter, which, when I respect it, leads to a very fat distance from the top (the safe inset is green):

spoiler

When I install it on my phone via Firefox, the app sometimes thinks it's display-mode:browser but displays perfectly fine as fullscreen, and sometimes it thinks it's fullscreen but displays more like a standalone. It seems completely random and can change any time I close the app or navigate away from it:

spoiler

When I install the PWA on my secondary phone (Moto G100) via Chrome, it has similar issues as on my main phone (it thinks it's fullscreen but is actually standalone) but it does not apply that ridiculous safe-area-inset. That backfires sometimes as navigating back via gesture will catapult the page to take up the full height, so the header shifts into the top bar. Would have been nice to have that safe-area here...
When I install it via Firefox on the Moto G100, it looks good about half of the time! Actual fullscreen with proper safe-area that doesn't break on navigation. Sometimes it randomly starts in standalone mode, but with the proper theme color applied to the top bar. Everything breaks if I have the Chrome version installed at the same time though. Then, the firefox version will never show up as proper fullscreen, but always have almost the same display issues as the Chrome version on that same phone.

I haven't even tested the PWA on iOS yet (I'll have access to an iPhone in about 2 weeks though so I'll test it then) but I'm guessing it will have its own display challenges as well. I'm also still battling the display issues from swapping my SVGs to generate with colors from the OKLCH system (it seems to really mess with any open source browser I've tried). So maybe, I should just ignore the browser display issues for now and focus on my color display issues instead?

Also, does anyone know if I can just let the user decide on their own preferred display mode? It would probably be the best solution to just let the user set the display mode that actually works in their specific browser. But as far as I understand how manifest files work, I can't really change much once the app is already installed, and I haven't found any online documentation that would suggest that I could programatically change the display property in the manifest based on user input :( But maybe there's some workaround you know about?

I would be very happy about some pointers and feedback on how I might get this display thing halfway consistent!

We might not live in the best timeline, but we sure live in the funniest one.

(no idea if it's satire, but I appreciate the dedication to the bit, especially when he started stealing merch right after)

Link to the videos Knowyourmeme page

Sorry, might be a stupid question, I have literally no idea about bikes!

What I'm looking to do is figure out whether there are any modern-ish ebike motors on the market that I could swap my current motor with (I'm assuming I'd be swapping all the other innards to fit that motor too, so dw about battery compatibility and the like). All I know about the current Motor is that it's a 250W Panasonic motor from around 2011. I asked the mechanic at my bike shop whether I could just toss one of those Bafang conversion kits on the bike but he said the way that my pedals sit within the motor would be incompatible with that and I'd need to get an actual ebike motor, not a conversion motor.

So now I'm trying to find information on current Panasonic motors and what sort of frames they need to fit, but I'm having a hard time because I have no idea how to even call this kind of spacing on the frame. Does anyone have an idea on what to call it/describe it as? Or is is a proprietary thing that I'd need a welder to rework? (Totally an option if push comes to shove, I know a guy)

Some more pictures from as many angles as I could get into (should I be getting measurements of any of these?):

spoiler

The cobblestone roads shook up all the drinks I was carrying home on my bike 😠

As in, I remember that back in my apprentice days I knew how much I got paid per hour.
Now recently I had to look trough my documents to find out what my monthly salary even is because it's raise season and I have to give my manager a number higher than that so that he can advocate for it to the board of directors.

I still remember my yearly salary semi-accurately (like within 10%), but I bet super rich people either go by decades or don't know at all what they make in a year.

On the other side, my friends who work retail jobs have a decent estimate of what they make per week or two week span, even if they are paid monthly.

I've been exclusively on Garmin watches since my interest in fitness started, my current Watch is a Forerunner 255s that I bought around 3 years ago. Thing is, it's been slowly starting to decline in battery life (one charge maybe lasts 5-7 days) and my height sensor started to really drift around, giving me that "You climbed 10 stories!" achievement like 7 times every day.

I was going to get a new Garmin when this one completely bit the dust, but due to a weird bundle deal at the Google Store, it was 300€ cheaper to buy a Pixel 9 and a Fitbit Charge 6 than it was to just buy the phone.

I can't sell the Fitbit for at least two years, since I bought the bundle as a "work expense" without paying taxes. So my options are to either use it myself or to give it to someone who I could quickly get it back from if the Tax Agency comes to check on whether I'm not reselling.

Sooo... does anyone here use Fitbit and could share their opinion on how it holds up? I'm especially interested in hearing how long the battery lasts and whether it works well with ANT+ devices (I use a Polar HR Strap and occasionally a bike cadence sensor)

Also, how annoying is it to listen to music on it? I bought the Music variant of the Garmin just to find out that it only really works with Spotify Premium... which I'm way too cheap to get. And manually transferring MP3s to it is really annoying haha

Despite all the other compromises with the FF6, I still was ready to buy it until I noticed the USB-C 2.0. Which means no Android Desktop and significantly slower data transfer than the USB-C 3.0 in FF5. The linked Discussion thread from the Fairphone forum has some interesting additional points.

Is this a dealbreaker for you? (It is for me, I'm ordering a different phone today..)