lupi

cow of tailed snake (gay)

avatar by @citriccenobite

you can say "chimoora" instead of "cow of tailed snake" if you want. its a good pun.​


i ramble about aerospace sometimes
I take rocket photos and you can see them @aWildLupi


I have a terminal case of bovine pungiform encephalopathy, the bovine puns are cowmpulsory


they/them/moo where "moo" stands in for "you" or where it's funny, like "how are moo today, Lupi?" or "dancing with mooself"



Bovigender (click flag for more info!)
bovigender pride flag, by @arina-artemis (click for more info)



lupi
@lupi

also i think whatever they pushed that forced the auto-refresh broke notifications?


lupi
@lupi

@kortney has already gotten a reply from staff saying that whatever change did this specifically to the notifications is being rolled back.

I've made a bug report for what happened to me, when the site failed to refresh/phone home/whatever while live updating/whatever and nuked itself, taking what i'd written in the modal post composer with it


You must log in to comment.

in reply to @lupi's post:

The "white out" only happens when they push a big change in the backend and the auto refresh can't load the new code, is my understanding. That may be wrong but I'm pretty sure that's what it is.

I'm not sure if there's a reason to have auto refresh turned on if you're on the new post page, because it's mostly a good way to lose work in that context. There's probably a reason I'm not thinking of.

it happens when you try to load an archive.org snapshot of a page too, it can't pull whatever its trying to pull from outside the archived environment and after 5 seconds the page disappears.

as for the second half, i think it might be an oversight stemming from the addition of the modal post composer (which lets you post from any page by overlaying the composer). maybe the "new post" page itself doesn't auto refresh, but when you have the modal one up, the underlying page you're on still can.