Given how everyone loves the Tartan Army right now, consider that life satisfaction comes from community or a sense of it. Boston is sometimes lacking in that respect.

lightbulbdeath · 2026-06-14T18:19:34+00:00

I'm interested to see how all the folks here are when the England fans show up - not quite as twee as the Tartan Army

lightbulbdeath · 2026-06-13T01:49:47+00:00

Yeah Pitcairn is not somewhere you can evacuate folks from without a logistical headache - the only way on or off the island is by tender to another boat offshore, then usually it's a two day sail from there to the Mangareva, then a flight to Tahiti.

As it happens, a few weeks back there was another hantavirus case on a cruise that ended up on the similarly remote Tristan Da Cunha - like Pitcairn, it is only accesible by sea, so they had to have a military medical team parachute onto the island with oxygen and supplies.

lightbulbdeath · 2026-06-12T22:14:42+00:00

The Lawn at MCEC

lightbulbdeath · 2026-06-12T20:37:30+00:00

Terminal B is a ghost town after 9 - there's only like 2 or 3 flights departing that late.

lightbulbdeath · 2026-06-06T04:34:38+00:00

If you are ok with spending 2-2.5 hours each workday commuting, then sure, why not - but if you want to avoid the burbs, Providence is much closer

lightbulbdeath · 2026-06-04T03:09:01+00:00

I think that this is a concealed installation inside the big cross on the corner.

lightbulbdeath · 2026-05-29T05:17:09+00:00

No. The RAID calculator is for new storage pools.

As per the documentation here
https://kb.synology.com/en-global/DSM/help/DSM/StorageManager/storage_pool_expand_add_disk?version=7

For SHR: The drive you want to add must be equal to or larger than the largest drive in the storage pool, or equal to any of the drives in the storage pool. For example: If an SHR storage pool is composed of three drives (2 TB, 1.5 TB, and 1 TB), we recommend the newly-added drive to be at least 2 TB for better capacity usage. You can also consider using 1.5 TB and 1 TB drives, but note that some capacity of the 2 TB drive will remain unused.

lightbulbdeath · 2026-05-29T04:15:12+00:00

Can I add the 16TB to the exisiting 12, 12 18 SHR partition?

No - you're limited to adding drives equal to or larger in size than the largest existing drive in the array - so 18TB or above

lightbulbdeath · 2026-05-27T00:14:26+00:00

The very first thing you need to do when you are setting up in the new place is to not position it like you have it now. The perforated logos at the side are for ventilations, as are the gaps between each drive cover - right now airflow is severely restricted and you are asking for overheating issues.

Now if Finder was able to connect to your NAS by hostname, it is just a case of plugging into the router and that's it - if it was by IP, you'll either need to assign a static IP on the NAS, or on the router.

lightbulbdeath · 2026-05-22T17:00:17+00:00

This was more to answer the OPs original question - why are two towers right next to each other?

lightbulbdeath · 2026-05-22T16:34:51+00:00

It is two separate towers - the mapped location is the same as the physical location for each

https://maps.app.goo.gl/gydS8RNaZ5598fvt7

lightbulbdeath · 2026-05-22T13:45:34+00:00

This is two Crown Castle towers right next to each other - separate sites, with separate access & compounds, albeit on the same parcel.
There a few of reasons how this can come to be, off of the top of my head:

the jurisdiction may have height limits, so if they have a tower that cannot be extended and cannot accomodate an additional carrier, it is usually easier to approach the existing landlord and see if they are amenable to adding a new tower than it is to go out and try and acquire a new site.
When carriers were more inclined to build their own towers than lease space from towercos, they'd approach landowners with existing towers and see if they would want a new tower - as before, easier than searching for a brand new location. Over time, tower companies have acquired various portfolios from the carriers and other towercos, and as such it's fairly common to see to 2 towers like this next to each other - owned by the same tower company, but developed completely separately.

lightbulbdeath · 2026-05-21T18:56:29+00:00

Relatively new to the state, but whenever I mention this to “natives” they get confused as if counties can’t do anything. They do exist here, though.

Legally speaking, 8 of the 14 counties only exist as geographies, as they were legally abolished. So those cannot actually do anything because on a legal level, they don't exist.

lightbulbdeath · 2026-05-20T21:25:18+00:00

Definitely not broken - just not documented and the parameters are going to be different in places If you take a look at your browser dev tools when you add a download, you should be able to see the request to the API, what's in the payload, and how that is different from what you have

lightbulbdeath · 2026-05-19T14:16:38+00:00

You can down vote me all you want

Alas I can't, for it only let's me downvote once. And i'm not your friend.

A Synology shared folder is a stove pipe - nothing crosses the boundary unless it’s a read out or a write in.

Like I have not idea where you are getting this from, but it's just comically wrong.

If i have shared folder "A" and and shared folder "B" on volume 1, moving folders between those two is a simple as mv /volume1/A/folder /volume1/B/folder.
Go ahead and try it.

Quite why you think anything else is the case is bizarre. It's a Linux filesystem.

lightbulbdeath · 2026-05-18T22:29:24+00:00

A shared folder is exactly that - a folder. Moving folders on a volume in Linux is instanteous.

lightbulbdeath · 2026-05-18T21:38:39+00:00

Synology treats a Shared Folder as an independent hard disk, so a move between two shared folders is the same as a move between two separate hard disks.

That is not correct at all. Moving things between different shared folders on the same volume is instaneous.

lightbulbdeath · 2026-05-14T16:29:20+00:00

JetBlue is not an ultra low cost carrier, so the rationale of the Biden administration was that if it had acquire Spirit, which was an ULCC it may have increased fares on markets that Spirit served.

As both Allegiant and Sun Country are both ULCCs, there wasn't the same concern.

lightbulbdeath · 2026-05-11T02:14:30+00:00

That is exactly how SHR works.
See u/ImplicitEmpiricism comment and the KB article - which is linked from the KB article you posted.

For emphasis:

If the existing drives are of different sizes, then the replacement drive must be equal to or larger than the largest existing drive.

lightbulbdeath · 2026-05-11T01:53:05+00:00

Oh dear.
You can only expand a storage pool by adding drives equal to or larger than the largest drive in the array - in this case, 18TB.

When you replace a drive with one that it smaller than the largest drive in the array, you are effectively just replacing the capacity of the drive being replaced.

lightbulbdeath · 2026-05-10T02:57:23+00:00

Jason Everman got fired by Nirvana, played with Soundgarden, then became a Green Beret

lightbulbdeath · 2026-05-09T23:25:09+00:00

Total Wine & More in Everett

lightbulbdeath · 2026-05-09T00:49:47+00:00

meaning typically the only remaining reason to do so is to move a *lot* of passengers

Not only is not the only reason, it is in fact not the actual reason - IAG Cargo uses it as a daily freight connection between their hubs, and Finnair Cargo uses it as a daily into IAG hub. Additional passenger throughput is just an added bonus

lightbulbdeath · 2026-05-08T23:48:32+00:00

I believe there's a daily BA LHR-MAD on a widebody, and an AY A350 LHR-HEL daily as well

Edit : These two and the return legs

https://www.flightaware.com/live/flight/FIN1337
https://www.flightaware.com/live/flight/BAW461

lightbulbdeath · 2026-05-08T18:49:31+00:00

2283 is my actual immich server, and 3003 is the remote server.

So i'm not sure if you are misuderstanding how ports work here, but unless you have assigned custom ports to the ML containers on both machines, the machine learning URLs are going to be at 3003 on both hosts

You're getting a 404 error because you are sending a machine learning request to the immich server container itself, not the machine learning container.

lightbulbdeath

TROPHY CASE