khannie @ khannie @lemmy.world

Posts

24

Comments

1,214

Joined

2 yr. ago

Oh damn. That's a beauty. Right from the mouth of the judge.

She could go one step further and try to convince a jury that he is in fact a rapist based on the evidence in the previous case. Different jury, maybe a different outcome. It's a roll of the dice I don't think he'd be willing to take.

edit: Fuckin' hilarious though that they're raging with the logic of "HE'S ONLY A SEXUAL ABUSER!!!" hahahahaha.

Reading the article then doing the oul' internet search, "the jury did not find Trump liable for rape and instead found him liable for a lesser degree of sexual abuse". (Wikipedia link).

AOC would surely fight this in court instead of rolling over like ABC did. Not sure that would be something Trump would like, especially if she wins.

What you're missing is that after Brexit the EU is desperate to appear to citizens that they're listening and this would be such an easy win that yeah, I really expected them to not only listen but actually get their fingers out of their collective arseholes and do something about it.

Blah blah funding. Sure, start by targeting games that sell over X units or Y euros in revenue.

If the article is correct then it's a massive missed opportunity.

I like to nibble the occasional onion but this one definitely didn't feel like an onion unfortunately.

SBU > FSB 🌻🌻

Incredible summary. 10/10.

High five from the far side of the Atlantic at 1:36am and not entirely sober ✋

Right.... Well that's some insight. Thank you . I heard a rumour that it was down to it being popular during a war where cocoa was in short supply but that makes sense too.

There is. That's fair, and some of it was decent and that's not to say that all American chocolate is bad because that would be stupid of course, as you say. And I'm sure there's top notch American chocolate. Of course there is.

But, the dominant chocolate, the one that foreigners associate with the US, was shite IMO. That's all.

And tbh I do like an oul' mackers. I wouldn't call McDonald's the Hershey's of burgers.

This is all subjective and I'm not being a cunt. I just was expecting sparkles in my mouth and I got.... Hershey's.

Try chocolate that wasn't made in America...

I'm actually very fond of the US but the chocolate is absolute filth, sorry lads. I was so excited to try Hershey's and holy moly was it an earth shattering disappointment.

Consistent with their more ecumenical views

I.... Can't help myself....

My french friend told me that the dairy farmers once protested by dumping a massive amount of milk on the streets of Paris one time. Apparently the smell was..... Well you can imagine.

The French know how to protest.

They're gonna be working hard to justify that budget. Things are going to get a whole lot worse for our American friends. :(

You're not going to believe this but someone else commented above that it might be the HDMI cable or monitor and unbelievably they were correct. Ping immediately restored once I unplugged it then went bad again when I replugged.

I've rotated the deck 90 degrees and it's a lot better.

Holy. Fucking. Shit.

This was it.

Here's my ping output. You can see where I unplugged and replugged the HDMI cable. Absolutely not in my wildest dreams would I have thought of this. Thank you so much.

    
(1)(deck@steamdeck ~)$ ping google.ie
PING google.ie (74.125.193.94) 56(84) bytes of data.
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=1 ttl=108 time=818 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=2 ttl=108 time=674 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=3 ttl=108 time=308 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=4 ttl=108 time=289 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=5 ttl=108 time=404 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=6 ttl=108 time=25.7 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=7 ttl=108 time=17.2 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=8 ttl=108 time=19.6 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=9 ttl=108 time=18.6 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=10 ttl=108 time=19.4 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=11 ttl=108 time=17.0 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=12 ttl=108 time=16.0 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=13 ttl=108 time=17.0 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=14 ttl=108 time=17.5 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=15 ttl=108 time=25.2 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=16 ttl=108 time=17.1 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=17 ttl=108 time=15.2 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=18 ttl=108 time=19.7 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=19 ttl=108 time=14.0 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=20 ttl=108 time=21.2 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=21 ttl=108 time=20.3 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=22 ttl=108 time=18.8 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=23 ttl=108 time=13.9 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=24 ttl=108 time=18.1 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=25 ttl=108 time=12.9 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=26 ttl=108 time=17.9 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=27 ttl=108 time=16.1 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=28 ttl=108 time=19.1 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=29 ttl=108 time=15.1 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=30 ttl=108 time=16.2 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=31 ttl=108 time=16.4 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=32 ttl=108 time=18.1 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=33 ttl=108 time=21.7 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=34 ttl=108 time=23.2 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=35 ttl=108 time=411 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=36 ttl=108 time=287 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=37 ttl=108 time=412 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=38 ttl=108 time=2445 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=39 ttl=108 time=1679 ms
64 bytes from ig-in-f94.1e100.net (74.125.193.94): icmp_seq=40 ttl=108 time=666 ms
^C
--- google.ie ping statistics ---
41 packets transmitted, 40 received, 2.43902% packet loss, time 40064ms
rtt min/avg/max/mdev = 12.890/223.052/2445.465/478.256 ms, pipe 3


  

Thanks. I can't see it in the KDE settings but will give that a whirl.

Everyone looking at the date counting down going "before what exactly?"

It's WiFi, 3rd party dock (but deck WiFi), ISP router which is unaffected on other devices, OS is right up to date.

I did reboot the ISP router just before posting and the issue still persisted until I rebooted the deck at which point it was gone.

edit: It's gone to shit again. I got a network analyzer on my phone and ping is clean as a whistle on it while the deck is averaging 400ms.

My wife had a favourite song when she was pregnant and it was very useful for calming after the birth. It was quite a chill tune.