Show newer

Forget protecting the furniture, this is the biggest reason I have to keep her claws from getting pointy!

Sound up for happy kitty purrs.

#cats

@wallhackio did you catch who the youtube channel i posted it from was

the IRS has decided I owe them $600 from 2023 taxes for some fucking reason

donate.unascribed.com

re: What Sad Dragon TF is from 

@coriander i can’t believe they made a game in which trapping zelda in her designated role literally caused the apocalypse, and then in the sequel to that game, they make her give up Her Entire Being fur the plot to work

Furry convention, but you only allowed to dress up as Tux or Xenia or Konqi or the GIMP dog or another free software mascot

@vaporeon_ honestly, technically speaking, it’s purrobably better than a bluetooth headphone, which also needs to embed a DAC (digital to analog converter) and amplifier alongside electronics fur bluetooth reception and decoding. i would imagine usb electronics are less heavyweight

@vaporeon_ a normally created git repository is a directory with a .git subdirectory, the ultimate source of truth about the repository and its history. the actual files that you are working on are part of the “working directory”

actually pushing to a remote only changes the contents of the .git subdirectory; the parent directory (that is, the “working directory”) is not changed to reflect any updates. strictly speaking this is fine, but consider a situation where

  1. somebody clones the repository,
  2. they add a new file and commit it, and
  3. they push the new commit back to upstream.

since the behavior of the the push opurration will not update the working directory upstream at all, this will create a very unintuitive situation where the history is being stored correctly, but the working directory is not updated. if you can git status in the remote, it would say the new file has been deleted! (although the change is recorded in .git, the working directory no longer has the file, so this is the conclusion git will come to about the current (unstaged) state of the working directory)

creating “--bare” repository makes the created directory just the .git subdirectory; no working directory is created at all. because git only needs the .git directory to handle server operations, this is fine

*climbs into a random folder on your computer*
is cozy in here :3
*tail sticks out*

archaeological dig unearths never before seen evidence that the ancient greeks knew about gay dragons

#furry #furryArt #dragon #dragonArt

Show older
📟🐱 GlitchCat

A small, community‐oriented Mastodon‐compatible Fediverse (GlitchSoc) instance managed as a joint venture between the cat and KIBI families.