Posts
1035
Following
0
Followers
18
l33th4xx0r in training
plays games, I think
Mastodon API tech support

XMPP: glitch@trashserver.net

Other accounts:
@Glitch@kawen.space
@necromancer@niu.moe

Necromancer akkohi2 mylittlevoid

Computer: "Warning: High GPU temperature"
Also computer: *Renders Diablo 3 in 4K for a 1080p monitor*
1
0
0
@RafiX
That sucks :/
Ok, what about game number 28?
1
0
0
@RafiX
A Hat in Time?
1
0
0

Necromancer akkohi2 mylittlevoid

I spent two hours in Diablo 3 again. Productivity!
0
2
3
@lucy @snacks Cool, thanks!
0
0
0
@waifu It looks like they are divided into groups. Group C is probably everything API related
0
0
1
@waifu I only use tags because of the shiny colors. No other reason. They are only helpful when only a few tags are used and the project is reasonably large, but this is just overkill
0
0
1

Necromancer akkohi2 mylittlevoid

Hey @lucy @snacks. Could you please add the onion link for netzsphaere to the instance panel? Those domains are not particularly memorable blobowo
0
0
1
@hunter I even had an own instance blobcatcoffee
0
0
0
@absturztaube
Wouldn't a whitelist make more sense with their rules enforced like that and a blocklist of that length?
@lucy
0
1
3
@absturztaube
What a weird instance...
@lucy
0
0
1
@absturztaube
They probably searched for their instance, found the post and blocked everyone reblogging/interacting that post
@lucy
0
0
1
@absturztaube
Original post; Lucy's post
@lucy
1
0
0
@absturztaube
Did you reblog the OP?
@lucy
1
0
0
@lucy @foxhkron @igeljaeger that's what you call an overreaction, god damn
0
0
0
Now I need to write an own extractor using serde_qs. Yay. Fun.
0
0
0

Necromancer akkohi2 mylittlevoid

>Failed during Query extractor deserialization. Request path: "/api/v1/accounts/relationships"
Oh, please no. I had the same problem with Rocket :<
1
0
0
@foxhkron Ok, that's weird. I can't think of any situations where this should happen
0
0
0
@foxhkron
Wait, I'm too stupid to read.
How do you synchronize the data between the threads?
0
0
0
@foxhkron
The mutable reference could move the data to a different part in the memory and immutable references don't update (as far as I know). That would produce a dangling pointer
0
0
0
Show older