placatedmayhem

joined 2 years ago
[–] placatedmayhem@lemmy.world 12 points 1 month ago

Friends don't let friends recognize the bodies in the water. ;)

[–] placatedmayhem@lemmy.world 17 points 1 month ago* (last edited 1 month ago) (2 children)
[–] placatedmayhem@lemmy.world 3 points 1 month ago* (last edited 1 month ago)

I wouldn't consider a consumer-grade router that doesn't have OpenWRT support. No arbitrary EOL to worry about. I was very happy with OpenWRT until I moved to OPNsense router and Ubiquiti access points. I still use it on my travel router, too.

Edit: Check if your current router is supported by OpenWRT and get more life out of it.

[–] placatedmayhem@lemmy.world 12 points 1 month ago (1 children)

Maybe now, but definitely not originally. Apple grew the Maps ecosystem originally for feature parity reasons, not privacy ones. That's at least a bit more similar to the Search situation.

Turn-by-turn was the killer feature back in iPhone 4S time frame, and Google refused to allow it iOS, shipping it only on Android. Apple had some geographic features (reverse geo lookup specifically, iirc) prior to this in-house and had started developing their own maps because of the longstanding tension with iOS and Android, but Apple rushed to get turn-by-turn directions out the door in mid-2012, which is partially what caused it to launch pretty half-baked. Google introduced a dedicated Google Maps app on the iOS App Store in late 2012 with turn-by-turn in response to losing millions of daily-active users to the launch of Apple Maps.

Here's a retrospective from 2013 by The Guardian on the whole thing with a lot more detail:

https://www.theguardian.com/technology/2013/nov/11/apple-maps-google-iphone-users

Now, Apple has run a web crawler since at least 2015:

https://www.engadget.com/2015-05-06-apple-web-crawler.html

Apple has been steadily building up its search expertise for the last decade. Notably, it acquired Topsy back in 2015, which was a search engine mostly based on Twitter data:

https://www.businessinsider.com/apple-shuts-down-topsy-the-200-million-mystery-laid-to-rest-2015-12?op=1

... then launched a few web-based Spotlight search integrations a few years later (which I can't find a good source for) which integrated common web searches for things like weather and news directly into Spotlight.

IMO, based on the above (and maybe a bit more), Apple's explanation in the article doesn't tell the full story. It doesn't want to build it, but it could. This is more is about Apple wanting to keep extracting the money from Google and not having to build another also-ran service to directly compete.

[–] placatedmayhem@lemmy.world 6 points 4 months ago

The recommendation changed from car lengths to seconds decades ago, but wasn't well communicated fwict. I learned car lengths from my dad and then seconds when I got my motorcycle endorsement.

If everyone were leaving 2 seconds of space, it also reduces stop and go traffic that is caused, or at least exacerbated, by the traffic wave phenomenon. But that's even less well socialized.

[–] placatedmayhem@lemmy.world 1 points 5 months ago

Yup! Stein (Robinson's opponent) has been polling with landslide numbers for weeks.

Meanwhile, R supermajority in the NC legislature is overriding governor Cooper's vetoes with some regularity.

[–] placatedmayhem@lemmy.world 9 points 5 months ago (3 children)

It looks like the png is getting word wrapped. Line spacing is so large that the png on the second line is getting pushed into the space of the icon below, and the icon below is given a higher Z value, so it goes over it. The different font has a different letter width and can influence the line spacing by being taller than the original font.

See if you can find an option to reduce line spacing or an option to increase icon spacing (vertical or horizontal). I would expect these to be advanced settings though. Iirc, most Linux desktops don't use ellipses on long names, like some other operating systems (macOS iirc).

[–] placatedmayhem@lemmy.world 38 points 5 months ago* (last edited 5 months ago)

Yes. I'm not sure what you think makes you bad at writing bug reports, but here are tips I give to everyone (my day job involves working with bug reports).

Nominally, a decent bug report should have:

  • the steps that got you the bug
  • whether you can reproduce the bug
  • what you expected to happen instead of the bug

Doing any of these things makes bug reports so much more actionable. You can do it. I believe in you!

Edit: Including a contact method so the software developer can have a conversation with you can also be helpful but not strictly required. Some bug reporting methods do this implicitly, like email bug reports and GitHub issues.

[–] placatedmayhem@lemmy.world 16 points 5 months ago (1 children)

It's available in the API and in some apps. I'm using Memmy for iOS right now and I get both.

[–] placatedmayhem@lemmy.world 49 points 5 months ago

It's exactly this. The policies put in place by "healthcare administrators" (MBAs and such with healthcare flavoring, not people that actually know how to care for people's health like doctors and nurses) are designed to process the most patience in the least amount of face time possible, so that each doctor and nurse can see more patients per day, meaning more office visit fees, meaning higher profit. My dad calls it the "cattle shoot" and I feel that's a pretty apt analogy. It's the same general reason that fast food restaurants and pharmacies and department stores are perpetually understaffed: fewer staff members means lower "overhead" costs.

[–] placatedmayhem@lemmy.world 21 points 6 months ago

Linking outside of their website would reduce engagement, thus ad revenue. I'd put money on this is why so many news sites rarely link out anymore.

[–] placatedmayhem@lemmy.world 44 points 6 months ago (6 children)

This is called "Embrace, Extend, Extinguish". Microsoft coined the term internally for their responses to open standards in the 90's and 00's.

https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

view more: next ›