Conversation

Notices

1. Embed this notice
   pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:31:40 JST pistolero :thispersondoesnotexist:
   An AP server tier-list for the shittiness in handling the Accept header:
   
   S-tier: PeerTube
   A-tier: Misskey, Pleroma
   B-tier:
   ...
   D-tier: Against all odds, *Mastodon* actually does something more or less what you're supposed to do. (Go figure.)
   
   Mastodon probably does it correctly because Rails has facilities that automatically do this because collectively, bullshit feature-factory startups have decided to outsource things like "Read a few paragraphs to understand this plain-text protocol that took off precisely because it's so easy to understand and work with" to framework authors. Don't fall for it, just read the RFC, it's easy, I swear: https://datatracker.ietf.org/doc/html/rfc2616 . (Honk is absent from the list because Honk has yet to cause any problems.)
   
   I'll usually put something on while I eat, watch a little TV and chill, you know? So over the course of a few days, I re-watched this speech Woz gave in 1984 about the early history of Apple and I've seen it before, but the thing that stood out this time was his account of how he designed the floppy drive controller. He sat down, he studied the Shugart specs, he applied what he knew about those and parity bits and he came up with a design that required five chips, at a time when most of them used 10-50; he joked that he didn't know enough to make one that took 50 chips. (Eventually they did custom silicon and moved all five chips onto one chip: https://en.wikipedia.org/wiki/Integrated_Woz_Machine . It would have been prohibitively difficult to integrate a 50-chip design.) This is several miles from the "I slapped the codebase with dependencies it until it worked" style of development most people do: if your codebase acts like you've been getting drunk and battering it, usually it's because you have. (I love you all but please have some goddamn pride as engineers and study the things you have to implement.)
   
   And that concludes a post I am likely to regret because it will upset someone that I don't want to upset and will also come back to bite me when someone has to debug their code and it turns out that the source is a fuckup I have made with Revolver. The former may not occur, but the latter definitely will, with as much certainty as the spelling mistake you will make when criticizing someone else's spelling mistakes (though a spelling mistake in a post someone makes does not tend to result in having to debug your code and then make your code jump through hoops because the bug is in another codebase).
   
   Thank you for reading my blog post.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:31:14 JST pistolero :thispersondoesnotexist:

     in reply to

     • rinpatch
     • NEETzsche
     @rin @NEETzsche
     
     > can't guess who is a browser by ua
     
     Firemen have to connect lengths of hose together, and they are trained to have one hold the hose and turn his head away, while the other does the connecting. This is because if they're both looking, they'll both move the hose around, and it will take longer to connect than if one holds still, and even if you're trying to hold still, you'll involuntarily move to "help". (Also it saves additional time because if they make eye contact when connecting their hoses, they always stop to say "nohomo".) So if a UA asks for the thing that exists at a given URL, you should give it that thing instead of trying to guess what it actually wants; if the client tries to guess and the server also tries to guess, that the client and the server are at odds.
     
     Anyway, UA-based content transformation was discovered to be a bad idea in the 90s, it is still a bad idea for the same reason it was back then.
     
     > everyone who opens the link in the browser should get a 406?
     
     See, the problem starts when you're trying to detect whether the UA is a browser or not and deciding what to display based on a bad guess (any guess is bad), but most browsers will include "*/*" in the Accept: header anyway. You go down the priority list, match it against what you can send back, and show them the best match for that (though the UA can't rely on that). If it's a redirect, you can't vary that based on the Accept header; a 200 has to be a 200, a 301 means that resource is elsewhere. The entire idea is that this is a resource, it's at this URL, and the server will pass back a representation of that resource. (It's also supposed to be a 405 with an Allow header if they try to use a method not supported by that resource, so "GET /inbox" shouldn't just pass back index.html and "POST /objects/whatever" shouldn't 404.)
   • Embed this notice
     rinpatch (rin@patch.cx)'s status on Monday, 25-Jul-2022 19:31:27 JST rinpatch

     in reply to

     • NEETzsche
     @p @NEETzsche so since we can't redirect everyone without an accept header and can't guess who is a browser by ua, everyone who opens the link in the browser should get a 406? or am I missing something?
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:31:29 JST pistolero :thispersondoesnotexist:

     in reply to

     • rinpatch
     • NEETzsche
     @rin @NEETzsche
     
     > If no Accept header field is present, then it is assumed that the client accepts all media types
     
     The field *is* present, but in this case that should be treated like "Accept: */*". This means that the JSON should be spat back out: that's the only representation offered by the server. Attempting to guess if a UA's a browser and redirecting depending on the guess, that's worse than doing nothing.
     
     What Pleroma should do is represent the resource or toss a 406. "Redirect or load the webapp" isn't either of those, that should not happen.
   • Embed this notice
     rinpatch (rin@patch.cx)'s status on Monday, 25-Jul-2022 19:31:31 JST rinpatch

     in reply to

     • NEETzsche
     @p @NEETzsche I did read the RFC and I do not get the complain.
     
     > If no Accept header field is present, then it is assumed that the client accepts all media types
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:31:32 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche Pleroma and Misskey both look for a magic value in the header and if it's absent, they guess (incorrectly) that you are a browser and they redirect you. PeerTube doesn't appear to even parse the header, it's an exact match or nothing.
     
     > tldr
     
     The post was shorter than the RFC. Just read the RFC. https://datatracker.ietf.org/doc/html/rfc2616
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Monday, 25-Jul-2022 19:31:39 JST NEETzsche

     in reply to
     tldr, what do they do that's wrong
   • Embed this notice
     「 Fried Fristi 」 (fristi@akkos.fritu.re)'s status on Monday, 25-Jul-2022 19:31:44 JST 「 Fried Fristi 」

     in reply to
     @p > (I love you all but please have some goddamn pride as engineers and study the things you have to implement.)
     
     I don't know how time management goes with open source projects, but at least at work I can definitely say that this is an issue of just not getting enough time to read into anything. The code at my job is a fucking mess and it's taking months and months and months for me just to slowly get one component properly sorted out, and then it usually just becomes shit spaghetti after 2 weeks anyway because "bossman wants a thing". Compared to that, everything I write at home looks like a work of engineering art.
     
     Funniest thing is, my own projects tend to develop faster and stay more stable despite the fact that I work on them like 6 hours a week tops.
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Monday, 25-Jul-2022 19:37:57 JST NEETzsche

     in reply to

     It’s an external API and they refuse to let us see it or fix it. I don’t know exactly what they’re doing. #inspect? #to_s? Either way fuck them.

     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Monday, 25-Jul-2022 19:37:58 JST NEETzsche

     in reply to
     The Ruby scripting language serializes "Hashes" -- a form of associative array -- in a certain way:
     
     ```ruby
     3.0.0 :072 > x= { a: "1234", b: "4567" }
     => {:a=>"1234", :b=>"4567"}
     ```
     
     It's actually very similar to JSON. However, a certain webserver responds with this format, and not JSON. I'm supposed to parse that. With JavaScript.
     
     You think I don't know the flaws of things like blockbots, but I do. I just choose to not deal with them until they become an issue. Because literally every day I'm always dealing with something that is a problem right now. And most of the time it's things that are totally out of my control.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:37:58 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche
     
     > The Ruby scripting language serializes "Hashes" -- a form of associative array
     
     I have sent you Ruby code that I wrote, we've talked about Rails, I know what Ruby is and what a hash table is (and I wish Ruby didn't call the class "Hash" but that's a Lesser Crime).
     
     > However, a certain webserver responds with this format, and not JSON. I'm supposed to parse that. With JavaScript.
     
     What, are they just...calling #inspect?
     
     > I just choose to not deal with them until they become an issue.
     
     I choose not to create a problem. None of the bots I've written autorespond (except the one designed to automate my responses).
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:37:59 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche
     
     > You wouldn't believe the ridiculous shit people stuff through that Ethernet pipe
     
     This is what I have been doing for a living my whole life so I know.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Monday, 25-Jul-2022 19:38:00 JST NEETzsche

     in reply to
     I read this article years ago that the Internet is, in practice, just duct tape and elbow grease and it's totally true. I'm totally unsurprised to hear these kinds of details. I deal with plenty of them in my professional life. You wouldn't believe the ridiculous shit people stuff through that Ethernet pipe boyo, that I'm expected to deal with. Actually, you probably would.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:38:01 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche Actually, I mean, for user accounts what Pleroma does is just send you index.html (with some ridiculous <meta> tags tacked onto the front) and load a web application that eventually loads the user in question.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Monday, 25-Jul-2022 19:38:02 JST NEETzsche

     in reply to
     >Pleroma and Misskey both look for a magic value in the header and if it's absent, they guess (incorrectly) that you are a browser and they redirect you. PeerTube doesn't appear to even parse the header, it's an exact match or nothing.
     
     I lol'd
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:38:07 JST pistolero :thispersondoesnotexist:

     in reply to

     • 「 Fried Fristi 」
     @fristi
     
     > just not getting enough time to read into anything
     
     That's why I said it's a problem caused by feature-factories. The environment encourages producing more things instead of good things. That's why it's important to read up on this stuff: if you can do a good job quicker than most coders can do a bad job, then the world is better.
     
     > Compared to that, everything I write at home looks like a work of engineering art.
     
     Almost everywhere I've ever worked. It's frustrating. Usually if you have this kind of problem, adding a test that fails if there's a fuckup will help discourage fuckups, or the person fucking up will comment out the test.
     
     > Funniest thing is, my own projects tend to develop faster and stay more stable despite the fact that I work on them like 6 hours a week tops.
     
     Sometimes it's "because of" instead of "despite". :putin_wink:
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:45:31 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche It's probably #to_s.
     
     I attended a talk by Evan Phoenix, and he said that before he did Rubinius, his first attempt at implementing Ruby was to start with the parser, which took him a year and was never completed. He eventually restarted and decided to just steal the MRI parser and he had a working implementation in no time.
     
     If it's just a Hash, that's not too hard, but I don't envy anyone attempting to parse Ruby from JavaScript, especially if their shit's that haphazard. (Just wait until they do something that eventually results in `{a: 1/0.0}.to_s`. At least `{a: 1/0.0}.to_json` throws an error. Ha, or `{a: Date.today}.to_s #=> "{:a=>#<Date: 2022-07-25>}". It's really nice to be able to have mixed-type hash tables but if they're sending them over the wire, there's no telling what you'll have to try to parse.)
   • Embed this notice
     Machismo (zerglingman@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:45:53 JST Machismo

     in reply to

     • rinpatch
     • NEETzsche
     @p @NEETzsche @rin Relatedly, in "normies were a mistake": Mobile subdomains/paths.
     Please, stop. Looking at you, Wikipedia.
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:46:18 JST pistolero :thispersondoesnotexist:

     in reply to

     • rinpatch
     • NEETzsche
     • Machismo
     @Zerglingman @NEETzsche @rin
     
     > Mobile subdomains/paths.
     
     :venomsnakedemon2:
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:52:11 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche
     
     > Implement a Ruby interpreter in Python. Implement a Python interpreter in Ruby.
     
     _why's unholy project would probably be a better approach to this. Compile to bytecode -> translate bytecode -> decompile in target language. :bruceforsythe:
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Monday, 25-Jul-2022 19:52:12 JST NEETzsche

     in reply to
     Implement a Ruby interpreter in Python. Implement a Python interpreter in Ruby. I am very smart.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Monday, 25-Jul-2022 19:52:15 JST NEETzsche

     in reply to
     The data type is literally `application/json`, too. I've been tempted to just try to parse it as JSON and strong-arm the subject with them: "Um, sweaty, no, just no, this isn't JSON."
     
     But I think there are reasons why the other team won't budge (likely just incompetence)
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Monday, 25-Jul-2022 19:53:06 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche
     
     > I think there are reasons why the other team won't budge (likely just incompetence)
     
     They fired the guy that wrote it, no one else knows how to tack `.to_json` onto the hash they're passing back.
   • Embed this notice
     nanachi (yes@social.handholding.io)'s status on Tuesday, 26-Jul-2022 04:33:49 JST nanachi

     in reply to

     • 「 Fried Fristi 」
     @p @fristi the key is making the adding of new unit tests easier than not, this way you don't use prod as your unit tests.
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 04:51:06 JST pistolero :thispersondoesnotexist:

     in reply to

     • nanachi
     • 「 Fried Fristi 」
     @yes @fristi Unit tests suck, you get better mileage the more you try to maximize coverage from functional/integration tests, especially if you do fuzzing (never do it if you can make a robot do it) and replays of production traffic.
     
     This pisses off the unit-testing cult, because any process cult gets furious when you point out that their process is a net drag. But there's no getting around it: if something breaks a unit test without changing the output of the system when the entire stack is tested, then the unit test didn't matter. Conversely, replays of production traffic will show you really quickly if something that you do has broken something that is actually in use, and you will find out in a hurry if something you've done has broken something important or slowed it down significantly.
   • Embed this notice
     nanachi (yes@social.handholding.io)'s status on Tuesday, 26-Jul-2022 05:09:25 JST nanachi

     in reply to

     • 「 Fried Fristi 」
     i agree with this tbh. full integration tests and fuzzing are just more effective unit tests as it tests the whole including cases you didn't know exist. the outcome is the same but the difference in effort is noticable.
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 26-Jul-2022 05:12:06 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @p That's interesting, I don't think I landed on that yet, probably could fix it in the relevant place for Pleroma, can you send something like a bug report?
     
     There is way worse for Accept header stuff btw, we should have proper parsing and handling of it while there is things that just do a string comparison (I think lemmy did that but I might remember badly, there is way too many implementations out there).
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 05:35:12 JST pistolero :thispersondoesnotexist:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan
     
     > can you send something like a bug report?
     
     The gitlab 500s for me when I try to use it logged in, but the quick version is the same thing I've been complaining about a while, essentially /notice vs. /objects, and what you get back if you GET /users/p.
     
     These already work correctly and do more or less what you want:
     
     * "Accept: application/json" returns JSON
     * "Accept: application/ld+json" returns JSON
     * "Accept: application/activity+json" returns JSON
     * "Accept: application/activity+json;q=0.9, text/html;q=0.1" returns JSON
     * "Accept: application/activity+json;q=0.1, text/html;q=0.9" results in an attempt to load the webapp
     
     These are the cases that are upsetting:
     
     * "Accept: application/json, */*" results in an attempt to load the webapp
     * "Accept: application/activity+json;q=0.9, */*;q=0.1" results in an attempt to load the webapp
     * "Accept: application/*" results in a 302
     * "Accept: */*" returns an attempt to load the webapp
     
     I don't think it's possible to get a 405 or 406 out of Pleroma. I don't think it should be the case that it attempts to *just* load the webapp, I think it should return HTML with the content on the page and the script tags that load the webapp, that way the resource is at least represented.
     
     Right now I'm just parsing JS but I plan to parse HTML (so as to make it easier for this to work properly: https://www.infoq.com/presentations/web-api-html/ ; I've done that kind of API before and the result is exceedingly pleasant).
     
     > There is way worse for Accept header stuff btw
     
     That is why PeerTube got S-tier. I played "Guess the magic string" for a while and then made a ranty post.
   • Embed this notice
     shitpisscum :shrerbia: :verified: (shitpisscum@shitpisscum.mooo.com)'s status on Tuesday, 26-Jul-2022 05:39:23 JST shitpisscum :shrerbia: :verified:

     in reply to
     @p Tfw you haven't heard about my JSON "parser"
     https://shitpisscum.mooo.com/notice/AJC6J3m0SCjlxU7OCm
     
     Also formating datetime strings using a bunch of substrings and concats in SQL (don't ask aboit that one)
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     :apa: スプリットショックウイルス † (splitshockvirus@mstdn.starnix.network)'s status on Tuesday, 26-Jul-2022 05:52:01 JST :apa: スプリットショックウイルス †

     in reply to

     • NEETzsche
     • ><∅>

     @p @NEETzsche @pleb

     >fuck peertube

     Truely the saddest day :cirno_cry:

     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 05:52:02 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     • ><∅>
     @pleb @NEETzsche Pleroma is shitty in this one facet and a few others; overall it's nice. ActivityPub is shitty all over.
     
     I did a workaround and I literally named it "BadAPCope" and it doesn't work for PeerTube so fuck PeerTube; there's a limit to the number of workarounds, I'll just figure out where their project is and file a but when I get to it.
   • Embed this notice
     ><∅> (pleb@shitposter.club)'s status on Tuesday, 26-Jul-2022 05:52:03 JST ><∅>

     in reply to

     • NEETzsche
     @p @NEETzsche pleroma was a mistake
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 05:52:44 JST pistolero :thispersondoesnotexist:

     in reply to

     • :apa: スプリットショックウイルス †
     • NEETzsche
     • ><∅>
     @splitshockvirus @NEETzsche @pleb Ah, I'll probably make it work anyway; everything seems like a huge pain in the ass that you hate right before you sleep.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 05:52:58 JST pistolero :thispersondoesnotexist:

     in reply to

     • :apa: スプリットショックウイルス †
     • NEETzsche
     • ><∅>
     @splitshockvirus @NEETzsche @pleb (But they should just fix their shit.)
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 26-Jul-2022 05:55:16 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @p
     > * "Accept: */*" returns an attempt to load the webapp
     
     Well this one is correct-ish, I mean ActivityPub spec says there should be ActivityPub stuff in the Accept header.
     
     For the rest, those are bugs, so here: https://git.pleroma.social/pleroma/pleroma/-/issues/2903
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 05:55:40 JST pistolero :thispersondoesnotexist:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan
     
     > ActivityPub spec says there should be ActivityPub stuff in the Accept header
     
     Where the ActivityPub spec conflicts with RFC2616, I'm going to just roll with Dr. Fielding instead of the octagon guy.
     
     > For the rest, those are bugs, so here: https://git.pleroma.social/pleroma/pleroma/-/issues/2903
     
     :bigbosssalute:
     
     (Although the */* turned into an italicized slash.)
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Tuesday, 26-Jul-2022 06:05:59 JST NEETzsche

     in reply to

     >I choose not to create a problem.

     You very notably did, though.

   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 06:05:59 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche The hole was the problem, not the complaints about the hole.
     
     Ignore recommendations by blue team, get embarassed by red team. Ignore red team, receive zerg rush. In this case, I was blue team and red team, and I haven't seen any zergs around but it's a matter of time.
     
     I know you don't like that reasoning, but that's the reasoning, and I'm not participating further. If you prefer, there's the fallback reasoning: I'm evil now and I do what I want. If you don't like that, either, please deposit 1 10grans to continue going down the same road we've been down before.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Tuesday, 26-Jul-2022 06:10:01 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @p
     > RFC2616
     
     Well I'll have a re-read of it anyway, maybe my opinion will change.
     
     > (Although the */* turned into an italicized slash.)
     
     Right, fixed.
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     nash's schizo daughter :ancapchanlol: (7@collapsitarian.io)'s status on Tuesday, 26-Jul-2022 06:11:21 JST nash's schizo daughter :ancapchanlol:

     in reply to
     @p This thread reminds me of an XKCD comic, but I'm thinking of it a lot more darkly.
     
     > "I mean, ostensibly yes. We mostly hacked it together from things that didn't make the API throw a fatal error"
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 06:12:12 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche
     
     > civilization, the Internet included, operates on a gentleman’s agreement to just not do certain things
     
     We haven't been using the same internet.
     
     Anyway, please deposit 1 10grans to continue going down the same road we've been down before.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Tuesday, 26-Jul-2022 06:12:13 JST NEETzsche

     in reply to

     A lot of civilization, the Internet included, operates on a gentleman’s agreement to just not do certain things even if given the opportunity. For example, I’m not going to rob, kill, or rape anybody even though I have the opportunity to, and can probably get away with it since police are retarded.

     >If you prefer, there’s the fallback reasoning: I’m evil now and I do what I want.

     Lol, in a way, yeah.

   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 06:17:22 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche Please deposit 1 10grans to continue going down the same road we've been down before.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Tuesday, 26-Jul-2022 06:17:23 JST NEETzsche

     in reply to
     Yeah we have. I just got rid of the bot because you voided that gentleman's agreement. It was either that or play a never-ending cat and mouse game with you.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 06:30:06 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche Civilization operates on a gentleman's agreement that if you're not trying to talk to me, you don't address me.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Tuesday, 26-Jul-2022 06:30:07 JST NEETzsche

     in reply to

     Your compulsion to reply to every message to you is hilarious.

   • Embed this notice
     skells@qoto.org's status on Tuesday, 26-Jul-2022 06:34:47 JST skells

     in reply to

     • nash's schizo daughter :ancapchanlol:

     @7 @p
     > I love you all but please have some pride and study the things you implement

     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 06:35:12 JST pistolero :thispersondoesnotexist:

     in reply to

     • nash's schizo daughter :ancapchanlol:
     • skells
     @skells @7 The small brain is Agile™!
   • Embed this notice
     nash's schizo daughter :ancapchanlol: (7@collapsitarian.io)'s status on Tuesday, 26-Jul-2022 06:35:14 JST nash's schizo daughter :ancapchanlol:

     in reply to

     • skells
     @skells @p
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Tuesday, 26-Jul-2022 06:42:05 JST pistolero :thispersondoesnotexist:

     in reply to

     • NEETzsche
     @NEETzsche I have a robot that can handle this for me if that turns out to be the optimal course of action.
   • Embed this notice
     NEETzsche (neetzsche@iddqd.social)'s status on Tuesday, 26-Jul-2022 06:42:07 JST NEETzsche

     in reply to
     I'M FORCING YOU TO RESPOND BY RESPONDING
   • Embed this notice
     xue (xue@bae.st)'s status on Tuesday, 26-Jul-2022 07:44:40 JST xue

     in reply to

     • NEETzsche
     @NEETzsche @p Is that intro to gay manga?
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     ベッサーヴィッサー (besserwisser@shitposter.club)'s status on Wednesday, 27-Jul-2022 18:36:25 JST ベッサーヴィッサー

     in reply to
     @p >have some goddamn pride
     
     :no:
     pistolero :thispersondoesnotexist: likes this.
   • Embed this notice
     pistolero :thispersondoesnotexist: (p@freespeechextremist.com)'s status on Wednesday, 27-Jul-2022 18:50:52 JST pistolero :thispersondoesnotexist:

     in reply to

     • ベッサーヴィッサー
     @besserwisser Craftsmanship is paramount.