87 Followers
88 Following
666 Posts
Coder/Dev in Chicago, weeknight side project code tinkerer, weekend boater and day drinker. Late night tooter.
Maybe i'm a little late on on this... like i love that the middle is big but now it's just bad now.... :(
For the last couple weeks I've been primarily on my new account on Mastodon.technology. Please follow me there instead. There are just too many performance issues with this instance.
I really just want to leave this instance since the performance has gotten so bad, but should we try to encourage the admin to pass the reins on to someone else? It's clear he doesn't have the time or desire to maintain an instance of this size. The instance is now the size of what mastodon.social was when I initially joined this instance. There are too many users here to see it just disappear from atrophy. Thoughts?
btw, just want to say fuck WCF services and my co-worker for using them, even after 2010-2012. I've tried to purge as much of that shit as I could. I'm so glad he left the company last year cause I'm purging the rest ASAP. Shit like WCF made people hate the C# ecosystem. Fuck that noise.
@TheAdmin each request is taking 5-10 seconds for me on .cloud right now. You may want to check server performance. Also, it may be time to limit new signups on this instance if not done so already.
I know local weather posts are lame, but, fuck, I'm so ready for spring in Chicago. 50s this week.

Of #Apple, #QRCodes, and sanitizing input:
https://infosec.rm-it.de/2018/03/24/ios-camera-qr-code-url-parser-bug/

"I’ve learned recently that the iOS 11 camera app will now automatically scan QR codes and interpret them.

Naturally the first thing I want to try is to construct a QR code which will show an unsuspicious hostname in the notification but then open another URL in Safari.

And this is exactly what I found after a few minutes."

#InfoSec

iOS camera QR code URL parser bug | infosec.rm-it.de

infosec.rm-it.de
Just had to call a friend out on their 'slippery slope' argument. We agreed on quite a but that argument is such BS. Luckily, my husband had my back too.

With recent revelations that Visual Studio Code (1.19.0 to 1.19.2) was listening on 9333/tcp exposing a debugging interface with flaws, it's worth learning an editor like ed(1) that doesn't even have network connectivity, let alone listen furtively on exposed ports.

If you want to read from the network, follow the Unix Way: external tools used explicitly

r !nc -Nl 0.0.0.0 31415

The remote machine can then do "echo hello | nc -N ${ED_MACHINE_IP} 31415"

https://medium.com/0xcc/visual-studio-code-silently-fixed-a-remote-code-execution-vulnerability-8189e85b486b

Visual Studio Code silently fixed a remote code execution vulnerability

This blog was written few weeks ago, since VSCode has been upgraded for a while, I made this public.

Yeah, if we could keep bots of off Mastodon that would be greeeeaaaat, ok? We saw how that all turned out. The only way I can see that happening is providing admins with tools to detect bot behavior, which is no easy task.