The Official Status Thread
-
Todo f7462340, (RaceProUK:uncategorized) !todo resolve 2bbf88e0
-
Status: Fucked up that command…
-
!todo resolve 2bbf88e0
-
Todo 2bbf88e0, (RaceProUK:KeepThePeace) Rescale all reaction images to no larger than 300×300px
-
Status: As promised, all my Amy pictures are now constrained to a 300px square box.
Some of them were a bit big…
-
You just gonna leave f7462340 unresolved?
-
No; that was created by accident, and I resolved it in the @todo testing thread ;)
-
I personally prefer .
Is that a personal thing or some cultural reference I don't get? Replacement for a rotten tomato?
-
Feel like I'm walking into a whoosh with this...
-
Feel like I'm walking into a whoosh with this...
Honestly, I think we both might be in for one...
-
you are just an asshole.
Most likely because you're an asshole ...
-
And there I was using "asshole" as a compliment.
I've been Doing It Wrong™ all along!
-
-
I mean within context of this forum.
"Asshole" is a bit too tame for Croats anyway. "Fucking bastard" (loose translation) works better.
-
I mean within context of this forum.
Carry on then. We are a wretched hive of scum and villainy.
-
-
Well, since I don't intend to register there, and knowing the amounts of Jeff's love for any browser that he doesn't personally use, you can, if you wish, report that
Version information Version: 27.0.1689.76 - New version 28.0.1750.40 is available Update stream: Stable System: Ubuntu 14.04.1 LTS (x86_64; X-Cinnamon)
Works perfectly.
There, Opera on Linux. I'm sure the amount of fucks he will likely give will be impossible to contain.
Also, I should really stop ignoring my update manager it seems.
-
Status: played a Portal 2 Co-op community test chamber with a friend from England. Looked to my right. Water. In the basement. Again.
-
Firefox 36.0.1 on Windows 8.1.
No issues.
-
Chrome version 41.0.2272.89 m, page is fine but slows to a crawl when the gif is in visible area.
-
-
Opera upgraded. Still works perfectly.
Well. Other than a fact that it's a Chrome clone these days. But they keep telling me that's a feature.
-
Chrome version 41.0.2272.89 m, page is fine but slows to a crawl when the gif is in visible area.
I've encountered problems several times around here. The tab goes to 100% CPU (according to Chrome's process manager thing). Other tabs and the rest of my machine are fine, but that tab is useless for quite a while. I've zeroboxed several of them.
-
Chrome on ChromeOS. No issues.
Version 40.0.2214.115
Platform 6457.107.0 (Official Build) stable-channel daisy
Firmware Google_Snow.2695.117.0
-
Status: played a Portal 2 Co-op community test chamber with a friend from England. Looked to my right. Water. In the basement. Again.
Son, it's well-past time you move out.
-
If I had moved out, my parents' basement would have been flooded for weeks before they found out about it.
-
Yeah but you could wank off like 12-13 hours a day with no interruptions. THINK ABOUT IT.
-
But I'd have to purchase/prepare my own food.
-
But I'd have to purchase/prepare my own food.
Hopefully washing your hands beforehand.
-
It also works in Vivaldi!
...
What?
-
Chrome on ChromeOS. No issues.
Version 40.0.2214.115
Hmm...OK, I actually went there. Chrome 41.0.2272.89 (64-bit) (Linux), BTW. This one presented no real problem for me. It was using about 13% CPU and 94% GPU. I don't recall the GPU working so hard before, but then we were also dealing with stuff bigger than 30MB, so not sure how much that matters. This machine has 24GB RAM, so memory isn't a problem here.
Seems like they've made some improvements since before.
-
Try letting it sit - It gets slow after a while for me.
-
-
I used to be more young than I am now.
-
Try letting it sit - It gets slow after a while for me.
It's still loading, so I think it's buffering or whatever equivalent. But the browser tab itself is doing fine. I can scroll and look at user cards or whatever.
-
Huh. Maybe it's a Windows thing?
-
Status:
http://try.discourse.org/t/warning-this-topic-contains-an-enormous-31mb-animated-gif/326
I don't want to create a throwaway account on try.d (again), but I had no issues, other than a little scroll lag (what do you expect, there's a 31MB GIF on the page‽).
Chrome 41.0.2272.76 m on Win 7 x64
-
Is that a personal thing or some cultural reference I don't get? Replacement for a rotten tomato?
i think it may possibly have been a certain vixen that started that here....
i think she.... oh sorry... i think it was me when i started getting angry at my woosh badges tried to use the:anger: eliji and discorse helpfully autocorrected to
and i rolled with it.
-
Water. In the basement. Again.
..... at least you didn't wake up to 4 inches of water.... like i did last summer....
-
-
-_-
you would go there.
-
Status: plumber ate dinner with us.
-
Status: surprised that my title edit for this topic has later this long....
-
-
From context it appears I was going for "emoji" and failing.
Add had been noted before, I don't flag speller on my own posts. That's too easy.
-
FYI:
Which is basically insane
-
Agree.
Would you get the same effect if you put the "new post" popup at the top of the screen? At least, then it won't have to shuffle it around in order to retrofit a keyboard where you placed the popup...
-
Status: Started
meld
in a terminal, got annoyed by the debugging output$ meld . ** (meld:20524): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-ndBY5F7jbH: Connexion refusée (meld:20524): dconf-WARNING **: failed to commit changes to dconf: L'exécution du processus fils « dbus-launch » a échoué (Aucun fichier ou dossier de ce type) (meld:20524): dconf-WARNING **: failed to commit changes to dconf: L'exécution du processus fils « dbus-launch » a échoué (Aucun fichier ou dossier de ce type)
(Usual Frenglish gibberish of course...) so I tried to restart it with stderr redirected to
/dev/null
:$ meld . 2>/dev/null Trappe pour point d'arrêt et de trace $
...
SIGTRAP
? Seriously?Fortunately, it worked when I restarted it. Looks like it’s going to be one of those days...
-
The company I work for has invested a lot of money in a huge setup of server space that can be used to spin up almost any number of virtual machines at any time - subject to not actually exceeding the capacity, of course.
Which is fine.
However, a series of edicts have been passed down from on high, including that all new applications must be in the cloud.
The VM setup has been renamed 'the cloud'. Problem solved.
-
The VM setup has been renamed 'the cloud'. Problem solved.
Brillant!
Filed under: A like was not enough