Platform Decay
Misplaced Lens Cap
we're not kids anymore.
Monterey Bay Aquarium
PUT YOUR BEARD IN MY MOUTH

titsay
i don't do bad sauce passes

@theartofmadeline
No title available

shark vs the universe
Alisa U Zemlji Chuda
hello vonnie
Cosmic Funnies
wallacepolsom
let's talk about Bridgerton tea, my ask is open
Keni
noise dept.

JBB: An Artblog!

No title available
trying on a metaphor

Kaledo Art

seen from Netherlands
seen from Ukraine
seen from Ukraine
seen from Ukraine
seen from United States

seen from United States

seen from United States
seen from United States

seen from United States

seen from United States
seen from United States

seen from Türkiye

seen from United States
seen from United States
seen from Malaysia

seen from France

seen from United States

seen from Japan

seen from Türkiye

seen from Netherlands
@fascinatedfinch
Platform Decay
So I was working on a set of Murderbot AUpril prompts, and one of them was "furries."
And we all know Murderbot is a feral cat of course.
But ever since I was a little girl, I have been in awe of @lackadaisycats's work... so now everyone else in PresAux is cats too:
And ART, of course, is an horrible Cheshire cat thing:
And bonus: Three, Lark, D'Artagnan, and ComaUnit!!
INTERPOLATION
(aka "how many ways can i gnaw on the concept of ART riding MB's feed")
Chapter 12!!! https://archiveofourown.org/works/67492181/chapters/174422211
We're coping with adversity quite well! That is: we are turning into a buffalo and attempting to stop the shit out of it
(this is technically from last chapter but there were SO MANY cool moments to illustrate so buffalo-ART upon ye)
Bonus: "idc if you're an ancient eldrich horror. we're not doing fuckall unless there's a written contract."
Chapter 11 is up!!!
https://archiveofourown.org/works/67492181/chapters/203398021
The crew gets new clothes! Tarik gets a goddamn smoke break! (Martyr Does Not Approve)
so did ART put together a 200-page powerpoint to convince its dads to let SecUnit on board or just send the text
alternate:
Will you stay? Down on your knees? Or will you bite the hands that feeds-- --
I've had Murderbot on the mind, so naturally when the early 2000s rock comes on... I'm having a good time.
[Image Description: A drawing of Murderbot from The Murderbot Diaries. The piece is a high contrast eye-strain with many layers. Murderbot kneels, being yanked forward by the throat with cyan barbed wire. The wire wraps around its face, partially gagging it and it bares its teeth in pain and anger. Murderbot's person form red with bright red lines and its armor is overlayed in orange with blue lines. Blood is pouring down its mouth to the bottom of the canvas. Overtop and behind Murderbot are images of animal jaws, including a: wolf, jaguar, barracuda, crocodile, gorilla, killer whale, and fox. The images are monochrome orange and obscure its eyes and parts of its armor, where a logo might be. All around Murderbot are blue hands, reaching kindly out to it, they are a gradient of light blue to cyan. Over top it all are the lyrics to a Nine Inch Nails song; Bite The Hand That Feeds, in bright white with a yellow to cyan shift under it. END ID]
we are BACK, baby!!!
An Archive of Our Own, a project of the Organization for Transformative Works
apologies for the... minor delay.
but! three pieces of art this chapter, for your patience!
Don't listen to her apologizing this hiatus was entirely the result of my absolutely incredible mental health.
Also it was worth it because Finch has gone and made some glorious artwork with the extra time!!
SHUT IT
for the record! I was also being extremely overambitious
don’t know how to paint landscapes (time to paint a landscape)
don’t know how to paint interiors (three point perspective time babey)
let’s draw everyone’s new clothes (it takes forever for me to decide on outfits)
there were literally 7 pieces I wanted to draw for this chapter
also I was traveling around and acquiring employment (ugh)
that is to say! uhhhhhh we are setting reasonable expectations now?
we are BACK, baby!!!
An Archive of Our Own, a project of the Organization for Transformative Works
apologies for the... minor delay.
but! three pieces of art this chapter, for your patience!
In my head, Murderbot is really bad at sitting normally, since it either stood at attention or curled up in cubicles for 87% of its life so far. And I question how accurate actLikeAHuman.actionfile is; ART was the main judge of human verisimilitude (and since ART is basically a weaponized Magic School Bus in space, it hangs out primarily with teenage survey interns and career academics which is going to create a fairly tilted data set of “totally normal human postures”.)
Loving Murderbot's rage meltdown at ART, even if ART clearly isn't and wasn't expecting it. Is this emotional reaction:
a) Unprocessed grief over ART's death seeking a new outlet
b) CPTSD reaction to being hauled around, called a weapon, and not given a choice
c) A reasonable reaction to ART almost killing its humans, including one of Mensah's children
d) All of the above
The look of horror on @fascinatedfinch's face as I explained to her last night that for all of my fic, several of which make extensive use of work skins, I have:
Copy-pasted text directly into the html editor on AO3 and added all my formatting tags by hand.
Built all my work skins by having the skin editor open in one tab, the fic draft in another, and repeatedly updating the css and then refreshing the fic draft to see what happened.
She didn't understand my reasoning that:
Copying from libre office into the rich text editor resulted in entirely unnecessary numbers of <span>s being dumped into my fic.
Copying into the html editor and then switching to the rich text removes all formatting, including paragraph breaks.
Therefore, copying into the html editor and manually doing everything for the basic html is the easiest option.
AO3's text editor uses <em> tags for italics, which is normally better because screen readers will read that text differently. But when I'm writing feed dialogue, the italics are only aesthetic, so I want to use <i> tags instead.
AO3 doesn't like some css. Using another editor can result in endless cursing while you try to fix what you made elsewhere. I have seen this happen to Finch. I save time by not being to build it twice.
This has nothing to do with whether or not I knew that there were tools that would let you edit css and watch the effects live or whatever. It's not like switching tabs and hitting refresh takes that long anyway.
I am very practiced in closing all my tags.
And yet all of this meant nothing to her in the face of me saying that I "rawdog the html."
for reference: i am a front end developer!!!
i am trying so so so gently to explain to my dear friend that there are tools that will help you preserve these precious mortal hours of your life. where you can make a lil playground that responds instantaneously instead of taking 30 seconds for every little edit to
change one thing in your workskin
save the workskin
go to the fic tab
refresh the fic page
see if the change worked
AND you don't have to live in fear of the Post button being 2mm away from the Preview button
(i learned these things from my very first baby Finch job when i fucking broke the production site as i was rawdogging the HTML)
i beg you fey
i beg
use a tool that has find/replace
Okay but you have to admit the colspan thing was clever and efficient on my part.
i shall admit it!! and it makes for a very cool and creative fic!!!
it also turns into a 2-character-wide classic Tumblr Drama formatting when the fic is not enjoyed on a Proper Device
*waves airily* Turning off creator's style on mobile fixes that, with the only downside being that it reveals my secret to vertical spacing.
monkey typing on keyboard produces work of thought provoking creativity
however: has not discovered tools and linters. HTML covered in dents from being hit with rock
finch you're soooo right actually. fey do better.
me, through gritted teeth: there are many ways to solve a problem using CSS and human …….. ingenuity.
The look of horror on @fascinatedfinch's face as I explained to her last night that for all of my fic, several of which make extensive use of work skins, I have:
Copy-pasted text directly into the html editor on AO3 and added all my formatting tags by hand.
Built all my work skins by having the skin editor open in one tab, the fic draft in another, and repeatedly updating the css and then refreshing the fic draft to see what happened.
She didn't understand my reasoning that:
Copying from libre office into the rich text editor resulted in entirely unnecessary numbers of <span>s being dumped into my fic.
Copying into the html editor and then switching to the rich text removes all formatting, including paragraph breaks.
Therefore, copying into the html editor and manually doing everything for the basic html is the easiest option.
AO3's text editor uses <em> tags for italics, which is normally better because screen readers will read that text differently. But when I'm writing feed dialogue, the italics are only aesthetic, so I want to use <i> tags instead.
AO3 doesn't like some css. Using another editor can result in endless cursing while you try to fix what you made elsewhere. I have seen this happen to Finch. I save time by not being to build it twice.
This has nothing to do with whether or not I knew that there were tools that would let you edit css and watch the effects live or whatever. It's not like switching tabs and hitting refresh takes that long anyway.
I am very practiced in closing all my tags.
And yet all of this meant nothing to her in the face of me saying that I "rawdog the html."
for reference: i am a front end developer!!!
i am trying so so so gently to explain to my dear friend that there are tools that will help you preserve these precious mortal hours of your life. where you can make a lil playground that responds instantaneously instead of taking 30 seconds for every little edit to
change one thing in your workskin
save the workskin
go to the fic tab
refresh the fic page
see if the change worked
AND you don't have to live in fear of the Post button being 2mm away from the Preview button
(i learned these things from my very first baby Finch job when i fucking broke the production site as i was rawdogging the HTML)
i beg you fey
i beg
use a tool that has find/replace
Okay but you have to admit the colspan thing was clever and efficient on my part.
@fascinatedfinch you're right and you should say it
@needlesandnilbogs i am shouting from the top of my wizard tower , trying to warn these citizens that the AO3 formatter will destroy their creations
the trials i went through to help create the Squab Experience.... harrowing....
also @potatoturnipbean : but amateur hour is so so so important!! you’re playing in the sandbox and learning as you go!!! you appreciate the little digging shovel so much more after digging around with your hands !!!
(and if you ever have CSS questions, I’m always happy to help!! W3 schools saved me as a baby developer lol)
The look of horror on @fascinatedfinch's face as I explained to her last night that for all of my fic, several of which make extensive use of work skins, I have:
Copy-pasted text directly into the html editor on AO3 and added all my formatting tags by hand.
Built all my work skins by having the skin editor open in one tab, the fic draft in another, and repeatedly updating the css and then refreshing the fic draft to see what happened.
She didn't understand my reasoning that:
Copying from libre office into the rich text editor resulted in entirely unnecessary numbers of <span>s being dumped into my fic.
Copying into the html editor and then switching to the rich text removes all formatting, including paragraph breaks.
Therefore, copying into the html editor and manually doing everything for the basic html is the easiest option.
AO3's text editor uses <em> tags for italics, which is normally better because screen readers will read that text differently. But when I'm writing feed dialogue, the italics are only aesthetic, so I want to use <i> tags instead.
AO3 doesn't like some css. Using another editor can result in endless cursing while you try to fix what you made elsewhere. I have seen this happen to Finch. I save time by not being to build it twice.
This has nothing to do with whether or not I knew that there were tools that would let you edit css and watch the effects live or whatever. It's not like switching tabs and hitting refresh takes that long anyway.
I am very practiced in closing all my tags.
And yet all of this meant nothing to her in the face of me saying that I "rawdog the html."
for reference: i am a front end developer!!!
i am trying so so so gently to explain to my dear friend that there are tools that will help you preserve these precious mortal hours of your life. where you can make a lil playground that responds instantaneously instead of taking 30 seconds for every little edit to
change one thing in your workskin
save the workskin
go to the fic tab
refresh the fic page
see if the change worked
AND you don't have to live in fear of the Post button being 2mm away from the Preview button
(i learned these things from my very first baby Finch job when i fucking broke the production site as i was rawdogging the HTML)
i beg you fey
i beg
use a tool that has find/replace
Okay but you have to admit the colspan thing was clever and efficient on my part.
i shall admit it!! and it makes for a very cool and creative fic!!!
it also turns into a 2-character-wide classic Tumblr Drama formatting when the fic is not enjoyed on a Proper Device
*waves airily* Turning off creator's style on mobile fixes that, with the only downside being that it reveals my secret to vertical spacing.
monkey typing on keyboard produces work of thought provoking creativity
however: has not discovered tools and linters. HTML covered in dents from being hit with rock
The look of horror on @fascinatedfinch's face as I explained to her last night that for all of my fic, several of which make extensive use of work skins, I have:
Copy-pasted text directly into the html editor on AO3 and added all my formatting tags by hand.
Built all my work skins by having the skin editor open in one tab, the fic draft in another, and repeatedly updating the css and then refreshing the fic draft to see what happened.
She didn't understand my reasoning that:
Copying from libre office into the rich text editor resulted in entirely unnecessary numbers of <span>s being dumped into my fic.
Copying into the html editor and then switching to the rich text removes all formatting, including paragraph breaks.
Therefore, copying into the html editor and manually doing everything for the basic html is the easiest option.
AO3's text editor uses <em> tags for italics, which is normally better because screen readers will read that text differently. But when I'm writing feed dialogue, the italics are only aesthetic, so I want to use <i> tags instead.
AO3 doesn't like some css. Using another editor can result in endless cursing while you try to fix what you made elsewhere. I have seen this happen to Finch. I save time by not being to build it twice.
This has nothing to do with whether or not I knew that there were tools that would let you edit css and watch the effects live or whatever. It's not like switching tabs and hitting refresh takes that long anyway.
I am very practiced in closing all my tags.
And yet all of this meant nothing to her in the face of me saying that I "rawdog the html."
for reference: i am a front end developer!!!
i am trying so so so gently to explain to my dear friend that there are tools that will help you preserve these precious mortal hours of your life. where you can make a lil playground that responds instantaneously instead of taking 30 seconds for every little edit to
change one thing in your workskin
save the workskin
go to the fic tab
refresh the fic page
see if the change worked
AND you don't have to live in fear of the Post button being 2mm away from the Preview button
(i learned these things from my very first baby Finch job when i fucking broke the production site as i was rawdogging the HTML)
i beg you fey
i beg
use a tool that has find/replace
Okay but you have to admit the colspan thing was clever and efficient on my part.
@fascinatedfinch you're right and you should say it
@needlesandnilbogs i am shouting from the top of my wizard tower , trying to warn these citizens that the AO3 formatter will destroy their creations
the trials i went through to help create the Squab Experience.... harrowing....
The look of horror on @fascinatedfinch's face as I explained to her last night that for all of my fic, several of which make extensive use of work skins, I have:
Copy-pasted text directly into the html editor on AO3 and added all my formatting tags by hand.
Built all my work skins by having the skin editor open in one tab, the fic draft in another, and repeatedly updating the css and then refreshing the fic draft to see what happened.
She didn't understand my reasoning that:
Copying from libre office into the rich text editor resulted in entirely unnecessary numbers of <span>s being dumped into my fic.
Copying into the html editor and then switching to the rich text removes all formatting, including paragraph breaks.
Therefore, copying into the html editor and manually doing everything for the basic html is the easiest option.
AO3's text editor uses <em> tags for italics, which is normally better because screen readers will read that text differently. But when I'm writing feed dialogue, the italics are only aesthetic, so I want to use <i> tags instead.
AO3 doesn't like some css. Using another editor can result in endless cursing while you try to fix what you made elsewhere. I have seen this happen to Finch. I save time by not being to build it twice.
This has nothing to do with whether or not I knew that there were tools that would let you edit css and watch the effects live or whatever. It's not like switching tabs and hitting refresh takes that long anyway.
I am very practiced in closing all my tags.
And yet all of this meant nothing to her in the face of me saying that I "rawdog the html."
for reference: i am a front end developer!!!
i am trying so so so gently to explain to my dear friend that there are tools that will help you preserve these precious mortal hours of your life. where you can make a lil playground that responds instantaneously instead of taking 30 seconds for every little edit to
change one thing in your workskin
save the workskin
go to the fic tab
refresh the fic page
see if the change worked
AND you don't have to live in fear of the Post button being 2mm away from the Preview button
(i learned these things from my very first baby Finch job when i fucking broke the production site as i was rawdogging the HTML)
i beg you fey
i beg
use a tool that has find/replace
Okay but you have to admit the colspan thing was clever and efficient on my part.
i shall admit it!! and it makes for a very cool and creative fic!!!
it also turns into a 2-character-wide classic Tumblr Drama formatting when the fic is not enjoyed on a Proper Device