Hey everyone! There's an L in vulnerable. #kthxbai

#VagueTooting

Helpful suggestion:

Instead of:

  • Posting error messages from #GitHub
  • Complaining about github being down

try:

  • Not supporting #FashTech
  • Moving to a different service
  • Not supporting fashtech
  • Self-hosting
  • Not supporting fashtech

#kthxbai

@fakemetrotrains ...but don't you dare to even think about correcting anybody's spelling online. #kthxbai

@pixx

Could you have them add

| clear | > /dev/text |

to http://wiki.9front.org/unix2plan9 ?

#kthxbai. XD

unix2plan9

for any #NASA folks still monitoring the #NASAsocial hashtag, please please PLEASE:

– make it SOP to put up a super simple straightforward one-page mission timeline that has every significant mission event with a built-in TZ converter so folks playing along at home can set their local time zone & get accurate updated timings 🙏

– make it as low-tech as you can – mostly text, minimal “fancy” crap (JS, WebGL, user-tracking frameworks 🤮, etc.)

– link to it prominently at / near the top of the mission homepage, maybe with a handy “Next up: $MissionEventName” label as well

– publish an iCal feed that folks can either subscribe to or download^

– update the timings as they slip or advance as best you can (and have a single source of truth that’s used to update both the mission timings page & the iCal feed, obvs.)

– yes, I’m def open to a fully-remote position on your #SciComms team so long as I can mostly work UTC+10ish-friendly hours 😜

#kthxbai
 
 
 
^ and then also maintain a canonical page with all your mission iCal feeds in one place – something like nasa[.]gov/SpaceNerds/MissionData/feeds/iCal/ would be appropriate 😜

Dearest winter: my spirit is already broken; this snow isn’t necessary. #kthxbai

Please take note, #CLI / #TUI devs.

Some of us still like 80x25, and would like our tools to be usable at that resolution.

#kthxbai

P.S. 80x24, what was I thinking??? 😂🤦‍♂️

@jbz

Plllllllease reply to yourself in a thread so we can get the context #kthxbai 😆

Dear #distro maintainers,

When you publish iso images and hashes, please don't just name your hash like this:

groovy-vibe-linux-1.1-amd64.iso groovy-vibe-linux-1.1-aarch64.iso groovy-vibe-linux-1.1-riscv.iso sha256sums.txt

Instead do this:

groovy-vibe-linux-1.1-amd64.iso groovy-vibe-linux-1.1-aarch64.iso groovy-vibe-linux-1.1-riscv.iso groovy-vibe-linux-sha256sums.txt

That way, when we download the sums, we know which distro they go to!!

#KTHXBAI

P.S., if anyone actually wants to use the name "Groovy Vibe Linux," it's all yours, as long as it's not just another Arch/Ubuntu derivative with a cool theme. Seriously, put in a little more effort. XD