One particular spite house in Boston: https://en.wikipedia.org/wiki/Skinny_House_(Boston)#History

According to local legend, the structure was built as a “spite house” shortly after the Civil War:

… two brothers inherited land from their deceased father. While one brother was away serving in the military, the other built a large home, leaving the soldier only a shred of property that he felt certain was too tiny to build on. When the soldier returned, he found his inheritance depleted and built the narrow house to spite his brother by blocking the sunlight and ruining his view.

Another source states:

Not much is known about the city’s narrowest house. Legend has it that … its unnamed builder erected it to shut off air and light from the home of a hostile neighbor (also nameless) with whom he had a dispute. … Believed to have been built after 1874

Sadly never came up.

I generally dislike editorialized headlines (when used as post titles) but this is the exception. Nicely played.

Not sure about Android, but on iOS, when one scans a QR code it shows the web address on the screen that the user then taps on. For the average user, I doubt that they are going to question what the URL is before following through to the website.

Android does the same. The problem is most of those QR codes are encoded short links which tells you nothing about where they’re taking you.

https://short.link/au1034gha could take you to a PDF on the restaurant’s Wordpress site or it could take you to malware or somewhere else you really don’t want to go.

In that case, I blame the people generating the codes for using URL shorteners. My org uses them in flyers for the public, and I always have to chastise them and re-create the QR codes because they run the URL to our website through bit [dot] ly. 😡

I used to work with a guy who was a dead ringer for Bill Bailey both in appearance and personality.

Weird. Other than how it used to choke when there were conflicts (and all uploads stopped until that was fixed) I haven’t had any issues like that. Guess I’m just lucky.

I’ve had pretty good experience with Nextcloud’s instant upload. The only time I’ve had it shit the bed was ages ago when it would occasionally get stuck on a conflict, but that hasn’t happened in a long time. Pretty much all of my image folders (camera/DCIM, Screenshots, Downloads) get synced. The only annoying thing was when apps would suddenly change where they download to and I’d have to reconfigure yet another sync folder, but I can’t really fault NC for that.

Mine is set to upload and keep a local copy and only do a one way sync (phone to NC). Not sure if that causes less issues than a 2 way sync or deleting the local copy after upload?

Hard to say. I’m not sure of the delivery radius that’s allowed here and whether rural food deserts would even be eligible or not. I was just mentioning that ordering (non-perishable) groceries online and having them shipped does have a legit and unfortunate use case.

Back when I lived 45 miles minutes from the closest grocery store, I’d order my non-perishables online and they’d usually come via UPS or FedEx.

This isn’t really the demographic they’re catering to but Food Deserts are a sad reality for many in the US. Being able to order staple food and have them delivered (even if it’s not same day) is often less painful than driving 30-50 miles to the closest grocery store.

They Might Be Giants - Istanbul (Not Constantinople)

https://lemmy.ca/post/46655208

Just defederated from usagi [dot] reisen just in case federation starts working on that end.

Probably different batches. Recall info said it was due to an issue with a single supplier. Not even all of the listed models are affected, just certain serial numbers for each model.

I mean…I tend to take potential lithium fires seriously, especially when they’re in my everyday carry. Companies don’t issue recalls and mass-replace units on a whim.

HAHAHA. 🤦‍♂️ I’ve called them “Ankler” for freaking years and am just today learning it’s “Anker”.

It’s “Downtown Abbey” all over again lol.

No, they’re on the form. Was just providing experience of what the process is like in case people expect it to be super painful.

Yep. I’ll note that in the post. Thanks.

Process was pretty easy. Basically you have to:

1. Fill out the recall form (linked in post).
2. Provide info for the unit:
   • Model number
   • Serial number
3. It will check to see if that exact unit is part of the recall. If it is, you’ll also need to provide:
   • Where it was purchased
   • The order number associated with the purchase
4. Let them know if you want a replacement unit shipped to you or a non-expiring gift card for Anker.com
   • I selected “replacement unit” and had to provide my shipping address. Not sure if gift card needs that or not, but would assume so.
5. You have to submit two photos of the unit:
   • Write the current date and the word RECALL on a piece of paper.
   • Upload a photo of the back with the serial number visible with the paper in the shot
   • Upload another photo of the front with the paper in the shot. Also, you have to write RECALL on the device itself in Sharpie (not sure if they’ll be able to see it in mine since the case is black and you can’t see the marker at all)
6. It said the turnaround time is approx. 5 days.
7. It advises to send the unit for recycling after you submit the form, but I’m holding onto mine for now because I’m not sure if they’re gonna complain about the Sharpie not being visible in the second photo.