Last with a headphone jack on the flagship while still allowing bootloader unlocking too. This is why I picked one up last year.

Folks literally have no conept anymore that you can just slap HTML on a page. & with the advent of needing TLS, it starts to become more technical than a lot of folks want to bother learning & maintain versus the days of raw FTP uploads.

Not in my ideal spot but tolerating Android via LineageOS for microG on a Sony Xperia 5 III as their ROMs make microG painless & hardware-wise I get a fast-enough CPU, OLED, a headphone jack, & microSD.

80 char line maximum? I read that as minimum. My bad.

Letting Cloudflare centralize the internet isn’t always the solution. I’m sick of hCAPTCHAs just for living in a non-Western country.

Microsoft GitHub injects Copilot ads in their source views. It’s another Microsoft service worth abandoning.

1. A flight ticket out of the US (it’s been 7 or 8 years since… not sure if I will ever return until there is an important funeral)
2. Wired IEMs with a Harmon target
3. Tea kettle with variable temperatures to make green tea properly without burning it

Things are about to get worse for onboarding those from other platforms. There’s been this massive push the last year to get every window manager to switch to Wayland & drop X11 support… meanwhile Wayland doesn’t support color profiles or color management (just sRGB). How are you going to convince someone with an awesome screen to drop down to sRGB? How will you convince someone with a poor screen that has been color calibrated to make it usable to go back to off colors? How do you expect content creators to migrate & still create content if they can’t have access to all the color tools they use in their workflow to come to Linux when Wayland won’t support them? A lot of Linux folk act like this doesn’t matter, but to a lot of people, a computer is a magic box that they interact with via a screen + keyboard + mouse, & if non-niche peripherals aren’t supported (which DCI-P3 is becoming the norm & saving a screen from a landfill can often be fixed to ‘good enough’ thru calibration), users will think it’s trash & unfinished.

Dino, Gajim turn on OMEMO by default & even the TUI Profanity prominently displays [unencrypted] in red at the top by default nudging you to pick OMEMO, OTR, or PGP for end-to-end encryption. The protocol is generic on purpose & meant to be extended with encryption which in the case of private chat applications, is now defacto. Much in the same way, TLS isn’t required since there are application that don’t require it, but defacto, all guides for setting up a XMPP server for chatting applications will suggest TLS where some servers have options like s2s TLS required or it won’t talk to the other server.

Seems weird that there’s a big, red no even when all the defaults point in the direction yes for human-to-human chat. Much in the same way some values are wrong like apps & servers being open source when there very much are proprietary XMPP servers out there like WhatsApp & Zoom. There’s also a reason Tails OS comes with Dino (or Pidgin) & every dark web guide explains how to connect to XMPP thru Tor + OMEMO/OTR, because it can be secure & anonymous enough for criminals & whistleblowers while being lightweight & decentralized.

Is this the real reason polka was invented?

A email provider shouldn’t require a closed, premium-only, lock-in-required sidecar program just to use IMAP/SMTP. I don’t think the release these bridge apps on BSDs or smaller OSs & you’re forced to use their apps on Android & iOS (no support for KaiOS or other smaller mobile OSs). This should be a giant red flag—kinda like waiving around a Swiss flag as more secure when they will sell you out just as fast as others.

These free-tier-loss-leading strategies are expensive too. If you bump up to premium it’s like $5/mo, but less marketing-heavy options where everyone pays get you all the features–like what I’m using @ 1€/mo.

I think I’m against this. Not because it’s the wrong thing to do, but it’s just going to swing marketers & such to obscure their tracking URLs to something like /my-slug/hashed-uid-for-tracking-without-query-param/post & it maybe unsafe or impossible to replace that part of the URL is some cases (think how not all credit cards numbers work, it has a built-in algorithm). The corpos can do this already now but query params are easier & less fiddly. Despite the large number of add-ons that could combat this already (including a uBlock Origin filter list), there wasn’t enough incentive to start another ad/tracking arms race… but you introduce it as a default feature in a major (🤞) browser, & now the corpos take notice instead of being able to wave it off as something a minority of users are doing.

…And I say this as the guy that reminds $WORK chat poster to remove their tracking URLs for the privacy of the group