Maybe A Human

I like things and tell stories 18+

[silverwolftales]

The F*Ck You Buffet : Compiled by Tastefullyterrible and contributors : Free Download, Borrow, and Streaming : Internet Archive

Secret Family Recipes Of Kids Betrayed By Their Homophobic Parents And A Few Recipes From Good And Kind People Because Balance Is Key

Spreading this around in hopes others remember and see it.

[clacy2812]

Lemme touch your face - Part 1/3

[clacy2812]

Lemme touch your face - Part 1/3

[mx-post-stuffs]

redraw

[mx-post-stuffs]

previous one

[themurderscene-deactivated20140]

and if you turn to ur left you’ll see the emos

[rnyselfie]

is that my chemical romance?

[penceyprepster-deactivated20160]

OH MY GOD not every group of emos is my chemical romance stfu tumblr

[chxmical-rxmance]

but it actually is my chemical romance

[losered]

this is the funniest fuckibg thing I’ve ever seen

[gay-emo-quotes]

I’ve…. seen this everywhere except on Tumblr itself. It’s the blessed post.

[teaboot]

Took Ollie to the vet today. And I'm not gonna say who. But ONE of us had a panic attack immediately after the checkup and wouldn't get out of the sink

[teaboot]

it was a difficult morning for everybody

[painted-bees]

this week has been way too exciting [negative]

I had just gotten back from my dog's neurologist appointment, which was...4 hrs long and stressful😭 Planned on eating a nice lunch and then getting some work done while there was still time in the day.

Only to watch a myna with a fat grub in it's beak land by my back door and then deliberately drop said grub and stare at it for a moment before flying off with a little "bwee" sounding coo.

And then I watched the grub move.

And then the horror dawned on me that it was not a grub.

it was this fucking thing:

I had a very ugly reaction that I will not describe in detail but fuck me 😭 I did not need this rn.

because I knew. I KNEW no rehabber here would take a myna hatchling. And I was right. Was basically told "congrats, it's urs" or "let nature take its course". It's such a strong, spirited little guy, if he's gonna die, he's gonna die warm with a full belly. Got a heatlamp and the appropriate food.

Let me be frank, I have no hope for this guy.

I have hand reared chicks before, but never this young. I hated doing it back then and I never wanna do it again. but this guy...He is like..1-5 days old.

SO, my life for the next week is gonna be waking up at 5:30am to feed this guy every 30 minutes until midnight. All day, every day. Assuming (biiig assumption) he doesn't just die overnight.

But he IS eating and pooping very well so far...so maybe he's gonna force me to live like this for a while after all 🫩 I give it a 50/50 chance, very generously. There's still a matter of diseases n' shit. He looks and acts healthy but who fuckin' knows what's going on under the hood.

It will be what it will be and all I can do is my best.

[painted-bees]

So, I have 2 plausible theories abt this

usually, when a parent kicks a chick out, it's because the chick is obviously very unwell and tending to it further is a waste of resources.

This chick, however, is very strong and determined AND had apparently been fed prior to abandonment. So--not unwell and not a waste of resources.

my first plausible theory is that these are first time parents who are very stressed by the monsoons and LOUD construction taking place across the street. Filicide can occur under such conditions.

My more plausible theory, however, is that the myna I saw was a home-invading kidnapper--not the actual parent of this particular chick. Mynas will kill rival nests, and evict chicks in order to claim the nesting site for themselves. And I think that's what happened here 😩

[painted-bees]

survived the night :V

Ate a fuckton of breakfast.

comfy.

[painted-bees]

lil dude has officially been with us for 24 whole hours...which might be most of his life, at this point!

So it's time to

get weighed, idiot!

9 gram.

Grub is currently 1 AAA battery large.

[painted-bees]

folks are already vested in Grub and I'm so nervous abt this being a sad ending. Please don't hold your breath for this little guy, the odds stacked against him are monumental.

When I weigh him tomorrow, I wil be able to get a clearer picture about whether or not he is on a trajectory of healthy development or if his growth is stalling and he is failing to thrive.

He can look good and strong, but if he can't absorb the requiered nutrient load and grow, then that could very well be the end for him.

I've been watching him around the clock and his behaviors seem good so far as my eyes can tell me...but more importantly, pls look at his tiny feetie claws

you can also see the eggtooth still clearly present at the tip of his beak here.

[cyberbunniisoda]

finally posting…. TwT

[bishopony]

twilight sends an urgent letter to the hippogriffs to not allow rainbow dash into the waters of mount aris indefinitely

[ponyisle]

The test. How Twilight ended up with Valen. Twilight was just a filly herself when she took him in. Yet another responsibility placed on such little hooves.

SURPRISE COMIC!! I have quite a bit more explaining to do about what led up to the rainboom but here’s this for now! More Twi stuff because I simply cannot help myself. Also an excuse to draw little fat baby dragon!!

[ms-demeanor]

Okay so my actual assigned-by-my-boss potentially revenue generating job for today was supposed to be updating a simple quote and sending it to the client.

Reader, it was not simple.

[ms-demeanor]

The rest of this post needs a dramatis personae:

UPS - Uninterruptable Power Source

SR(1-6) - Server Rooms 1-6

LSF - Another server room but with a different name

PSA - Software that includes client management and hardware management tools, plus ticket tracking and history

RMM - Software that includes remote management tools

Documentation Platform (DP) - software that hosts documentation about client passwords and other information

IP address - location of a device on a network

Serial Number - Unique hardware ID, in this case it must be noted that the manufacturer serial number includes the device production date.

There are seven UPSs, SR1-UPS, SR2-UPS, SR3-UPS, SR4-UPS, SR5-UPS, SR6-UPS, and LSF-UPS. The names should, in theory, correspond to the Server Rooms they are placed in and the documentation in the PSA, RMM, and Documentation platform should match.

[ms-demeanor]

We need to quote replacement batteries for any devices that are reaching about three years of age.

We don't have a documented inventory of UPSs for this client (bad). SR6-UPS, SR2-UPS, and LSF-UPS are not visible in our RMM or on the network, but have records on the PSA and the DP.

We have been attempting to define a "source of truth" for our equipment (this has been a very big part of my job recently due to lifecycle management) and the way this is SUPPOSED to work is that the RMM gathers information from a device, which syncs with the PSA to create a Configuration Item (CI), which syncs with the DP to create a record. The PSA is supposed to be the source of truth, because it can be updated from muliple RMMs but we can manually create CIs if we have to.

The PSA can *only* be updated via the RMM if something called Simple Network Management Protocol (SNMP) is enabled on the devices. It has, historically, not been standard for us to enable SNMP on most devices.

Because we weren't able to see everything about these devices via the RMM, I sent a tech to the site to find all of these a few months ago.

[ms-demeanor]

Immediate, instantaneous problem: the first UPS is showing an assigned name that doesn't match any of the other devices, and is displaying two serial numbers. One serial number indicates that the device was manufactured in 2017 and the other indicates that it was manufactured in 2022.

This is NOT the device I'd sent the tech to document - the device I'd sent the tech to document was not connected to the network.

[ms-demeanor]

The device that has two serial numbers is supposed to be LSF-UPS. Instead the device shows "NND-1" as its description.

The device not connected to the network is SR6-UPS, it appears to be functional and plugged in but does not have SNMP enabled. It is also nine years old at a minimum, and (according to the tickets in our PSA) had the battery replaced in 2020. This is, as far as I know, the only actual device that is in the network that was manufactured in 2017.

The next device is SR2-UPS, which is not showing as connected to the network in our RMM, but is visible from other management devices.

The tech takes photos of:

The serial number

The product number

The MAC address

The IP Address

He does not photograph each of these identifiers for each machine. It's sort of a grab bag of what he documented for each one.

[ms-demeanor]

The tech documents spotty information on SR1-6 and LSF-UPS.

I find this information unsatisfactory. I go to the manufacturer management portal and export the list of devices we've got registered on the portal. That list includes:

SR1-SR5 UPS.

It does not include LSF-UPS

It DOES include Stand-55 UPS. Which I do not have documented by the tech.

Neat. It also says that SR2 and Stand-55 have lost connection, but provides IP addresses for all devices and also has location descriptions for most devices.

I decide I need more info. I go to the RMM.

[ms-demeanor]

The RMM has no serial numbers. It has only one MAC address. It has IP addresses that don't match the IPs from the photos or from the vendor.

It is showing two devices offline, they are not the same two devices that the vendor showed as offline. Some of the devices that show as last connected a year ago in the RMM show online from the vendor.

My ears start ringing.

The RMM shows one device created in 2015. The vendor serial number from that device indicates that it was manufactured in 2022.

I require documentation. I go to the documentation platform.

[ms-demeanor]

I have 8 UPSs (SR1-6, LSF, and Stand-55).

The documentation platform has twelve configuration items labeled as UPSs.

Each item has a linked server room and a unique identifier that is synced from our PSA.

The document for LSF has a note that it was edited in 2018. The serial number for LSF indicates that it was manufactured in 2022. The ticket I have for installing it is from 2023.

[ms-demeanor]

The document for another device has no name, in place of the name is an IP address that doesn't match any of the other IPs that I've collected thus far.

[ms-demeanor]

The documentation platform has three ID documents for S1-UPS, each of them has a different unique ID (which is supposed to correspond to the unique ID from our PSA). One of the unique IDs includes the vendor MAC address of the device with the same name as part of the unique ID. All three documents have different create dates, on of which is from 2017. The vendor serial number indicates this UPS was manufactured in 2023. The document from six years before the hardware was manufactured is the only one that lists a physical location.

I need to check the documentation platform against the PSA, so I have to search the unique IDs in the PSA.

[ms-demeanor]

Surprise! It's bad!

[ms-demeanor]

Okay so apparently the reason that the UPS had two serials in the photos that had two different create dates is because apparently from 2015 until 2023 we've been using hand-me-down NIC cards in new hardware (even when the cards are past support age).

But also: for some reason SR2-UPS and the UPS that has just an IP address for a name are the same device and the of the 6 IPs associated with these two records only one matches the IP that's the document name.

[ms-demeanor]

The documentation platform has a network diagram that I can search by IP address to see what switches the UPSs are connect to.

SR2-UPS/IP Address Name - since the name is SR2 that should be in Server Room 2 and on the Server Room 2 Switch.

But no, that would make sense. It's on the Server Room 1-2 Switch.

[ms-demeanor]

Documenting 8 UPSs.

[ms-demeanor]

Also sometimes Server Room 6 is known as SR6, and sometimes it's known as NPP6, and sometimes it's known as SR NPP, and sometimes it's known as the Loft.

So I'm specifically trying to find solid documentation on a piece of hardware that has a minimum of 4 different names and is cobbled together from hand me down hardware using CIs that are only distinguishable by 40-character IDs because we replace hardware with hardware that we name in exactly the same way and nobody prior to me seems to have understood what the fuck a serial number is.

Anyway that's 14 records for 8 devices.

[ms-demeanor]

I spent seven hours on this and it's for a quote that will generate less than $300 of profit. And I haven't even unfucked the documentation yet, I've just documented HOW it is fucked.

[whydidisavethistomyphone]

[kawaiihonyaku]

虹って渡れるのかな…💭🌈

I wonder if you can cross a rainbow...

[kawaiihonyaku]

だっこする？

Will you pick me up?

[geopsych]

Sunrise at the lake, July a few years ago

[hypokeimena]

i need to show you guys the absurdly saucy pear my parents just casually had out in the fruit bowl like it was normal

[hypokeimena]

im not a talented photographer but these come close to capturing the overall effect (i.e., the raunch factor)

[feefal]

Dino cube :)

[leatherleaves]

My 2 year old son is obsessed with your Dino cube. When I showed him he audibly gasped and took my phone from me so he could zoom in and look at different parts of Dino cube. He looked at Dino cube’s face and turned to me and said “happy!!!” and I said yes, Dinosaur is happy!

He spent 5 minutes just admiring every part of Dino cube, he would’ve spent longer if I’d let him lol. Picture saved so he can look more later.

[feefal]

Genuinely the cutest thing I’ve read :’) Your sons “happy!!” comment is the single most greatest art critique I’ve received