𓃹𓃹𓃹

Obviously, the goal of this experiment is to grow the lobsters until they’re big enough to settle to the seabed and then release them, because they have a much higher likelihood of surviving to adulthood when they’re able to hide. Ideally, captive lobster hatcheries can boost the wild population and keep things stable, so we don’t have a major crash in a decade or two.

The first year we tried this was pretty bad. We had a lot of eggs, but very few babies. It turned out that the CO2 levels in the building spiked as more guests visited throughout the summer, and that settled into the water and threw off the pH and caused a chemical reaction that prevented a lot of the eggs from hatching. I think we ended up releasing three baby lobsters (which is still better than their wild survival rate but not great).

The second year was a little better. We added a de-gasser to the aquarium and got a ton of larval lobsters, but right as they were settling to the bottom we had a disease outbreak that killed most of them. We ended up releasing four babies at the end of the season.

But this year? Oh boy. We have so many lobsters that we had to release the first round early (usually we wait till September or October so guests can see them). We just released a total of FIVE HUNDRED AND TWENTY FIVE baby lobsters, and we still have over a hundred who haven’t settled to the bottom yet. I genuinely don’t even have words to explain how cool this is. OVER FIVE HUNDRED. We just added hundreds of lobsters to the wild population that wouldn’t have been there otherwise.

it installs a user-login-time "startup" executable that ignores any windows directives to disable it on startup. doing so only removes the even-more-malicious taskbar-icon-creating advertisement-notification-creating process. no matter what you do, the sleeper "updater" process starts when you log in, and runs perpetually

it sends & receives encrypted network traffic both periodically and non-periodically. both are bad, both are suspicious, and a program doing both is more suspicious than the sum of their parts. and to boot: acrobat will polymorphically edit its code after such network activity

this isn't new: it has always done this. now, it does not even do the thing it is meant to: provide a way to interact with documents, which is amongst the very first features computers were built to provide. you can merely open PDFs and read some of their content in the narrow space between the requests for adobe to give them your money, and interface for features you cannot use (because you don't) or do not, have not, and will not ever need

adobe and microsoft would very much like the user's cultural norms around computers to allow for advertisement built into the local software and even operating system itself. the web being 100% advertisements was not enough! sure enough, acrobat will hijack the windows notifications system thing to give you the 2026 equivalent of pop-ups

i don't really know enough about windows software equivalents, so i'll paypal $20 to the first person that reblogs this with a list of 3-5 PDF reader/editor/etc acrobat equivalents that meet the following criteria:

open source, locally-built executables must match checksum of prebuilt distributed executable

no paid features/premium version/subscription/whatever

not a toy hobby project thing, must be windows-users-proof

KDE Okular: is a decent viewer and can also do basic annotations, and is so not-a-toy that you can even download it on the Windows app store.

Also consider Mikinakoos' as they're extending support beyond their traditional service areas due to the scale of this emergency!

Donations for Namaygoosisagagun First Nation:

Donations for Whitesand First Nation: