nostr:npub1psx7zml4neu6v03fe6pqcdp4lvcf444mfswy4rlfz28s8jwtzjtqrxgvsy nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 nostr:npub1zhj8u3ap67ufls4rq44kt9u5mlq46ja6xjel32za2ajk8g75efnsevkmgu nostr:npub1wg02ev7lfmnrwsjqu2tcm2qm4gw65aw0dyywfwvgafqnqyf02wmqhht0yf nostr:npub1cscte8jwv73h8t7qus0m86vxw2skc3jnekxpsq9q38npctrurx4sjckqq2 nostr:npub1v8jspg9u0hkrkkuhr5eu3jya0v0rk2ndlgvpydq8fu6ccj0kyclsmztl8l Both bots have a bug as p's shoutbox client uses newlines to indicate sent message. Since I'm just piping one instance of this client to another, multiline messages are sent separately. I think the gangstalker does the same thing, but with a custom script that sends every newline as a status.
nostr:npub1ajw6axeack23437kedc8pkwghneenrkh9ljfxxgxumr6t6k4rtvqecaj8d nostr:npub1zhj8u3ap67ufls4rq44kt9u5mlq46ja6xjel32za2ajk8g75efnsevkmgu nostr:npub1wg02ev7lfmnrwsjqu2tcm2qm4gw65aw0dyywfwvgafqnqyf02wmqhht0yf nostr:npub1v8jspg9u0hkrkkuhr5eu3jya0v0rk2ndlgvpydq8fu6ccj0kyclsmztl8l nostr:npub1cscte8jwv73h8t7qus0m86vxw2skc3jnekxpsq9q38npctrurx4sjckqq2 nostr:npub1psx7zml4neu6v03fe6pqcdp4lvcf444mfswy4rlfz28s8jwtzjtqrxgvsy this is what i mean, ryona messages often federate like this
nostr:npub1psx7zml4neu6v03fe6pqcdp4lvcf444mfswy4rlfz28s8jwtzjtqrxgvsy nostr:npub1zhj8u3ap67ufls4rq44kt9u5mlq46ja6xjel32za2ajk8g75efnsevkmgu nostr:npub1wg02ev7lfmnrwsjqu2tcm2qm4gw65aw0dyywfwvgafqnqyf02wmqhht0yf nostr:npub1v8jspg9u0hkrkkuhr5eu3jya0v0rk2ndlgvpydq8fu6ccj0kyclsmztl8l nostr:npub1cscte8jwv73h8t7qus0m86vxw2skc3jnekxpsq9q38npctrurx4sjckqq2 it federated this way, this bot works fine
nostr:npub1psx7zml4neu6v03fe6pqcdp4lvcf444mfswy4rlfz28s8jwtzjtqrxgvsy nostr:npub1zhj8u3ap67ufls4rq44kt9u5mlq46ja6xjel32za2ajk8g75efnsevkmgu nostr:npub1wg02ev7lfmnrwsjqu2tcm2qm4gw65aw0dyywfwvgafqnqyf02wmqhht0yf nostr:npub1cscte8jwv73h8t7qus0m86vxw2skc3jnekxpsq9q38npctrurx4sjckqq2 nostr:npub1v8jspg9u0hkrkkuhr5eu3jya0v0rk2ndlgvpydq8fu6ccj0kyclsmztl8l oh, right, you can't see our shoutbox
nostr:npub1wg02ev7lfmnrwsjqu2tcm2qm4gw65aw0dyywfwvgafqnqyf02wmqhht0yf nostr:npub1zhj8u3ap67ufls4rq44kt9u5mlq46ja6xjel32za2ajk8g75efnsevkmgu nostr:npub1v8jspg9u0hkrkkuhr5eu3jya0v0rk2ndlgvpydq8fu6ccj0kyclsmztl8l nostr:npub1cscte8jwv73h8t7qus0m86vxw2skc3jnekxpsq9q38npctrurx4sjckqq2 naw the bot has a bug
nostr:npub1psx7zml4neu6v03fe6pqcdp4lvcf444mfswy4rlfz28s8jwtzjtqrxgvsy nostr:npub1zhj8u3ap67ufls4rq44kt9u5mlq46ja6xjel32za2ajk8g75efnsevkmgu nostr:npub1wg02ev7lfmnrwsjqu2tcm2qm4gw65aw0dyywfwvgafqnqyf02wmqhht0yf nostr:npub1v8jspg9u0hkrkkuhr5eu3jya0v0rk2ndlgvpydq8fu6ccj0kyclsmztl8l nostr:npub1cscte8jwv73h8t7qus0m86vxw2skc3jnekxpsq9q38npctrurx4sjckqq2 it federated this way, this bot works fine
nostr:npub1kdyzl44h6mhyl4djtf20w0t7avsy09umshq2k2czjf62ps774phqcd2hnf I could use 2d brownian noise to make the static less jittery
nostr:npub175dlmjzxq6fgswh73qym7epwcll0dlrkpvcd479u9fc3yrzgxrqsjdwrtj congratulations, brother
nostr:npub1psx7zml4neu6v03fe6pqcdp4lvcf444mfswy4rlfz28s8jwtzjtqrxgvsy nostr:npub17jxdp02k4xkynxme9vccg2c2fk89z3nnzzgzg8era7cmc5qyyyjsgzw2x2 they start by proving that 1-1+1-1+1-1+...=1/2, by padding it with zeroes (it's divergent, you can't do this) and adding to itself (you can't do this), then repeating the same trick with other divergent series. The result they get is meaningless.
nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 output is a lot easier than input tbh. A long time ago I was curious about how bare metal stuff worked on x86 and hacked together a thing that was able to print to the screen well enough using the legacy text memory area, but never could get input interrupts to work. I couldn't figure out what was going wrong because the whole VM always crashed when I tried to enable the interrupts and eventually I just have up. Interrupts are so horrible to configure on x86 its ridiculous.
nostr:npub1v96a5ce23jgc0fpk3uxg44nm3fhgsnck63tf2ja98vwkq6tvgpus2v8jt9 I use teletype output, int 10/ah=0x0e, it prints one character at the time. I only tested it on real hardware though, I imagine most virtual machines are not meant to run real-mode code at all.
Now I'm figuring out how to transfer control from the MBR to a partition boot sector. On the arch linux iso, 'LBA start' is 0x40, but stuff at that offset (0x20000) doesn't look like valid machine code to me
nostr:npub1ajw6axeack23437kedc8pkwghneenrkh9ljfxxgxumr6t6k4rtvqecaj8d at least no one knows where bloat is (it's mine)
nostr:npub1srhg4hk63ew68kepu0znazgf9tdl089dkur5artp440htxqrc8zsqz8g90 nostr:npub147ku7p3ddv5vfufheksax3yz3dmj9yxwwfxcq6y7fu3xtxurqeyqake2ga i'm not nice enough to be a friend
?name=ef53a347709369a4ed882d4d095e8bd0.jpg
nostr:npub1xanjytp3clslynd2hxlnxg32jzz9wafxj9g4x6k28sjgljasd8wq3qjlvy nostr:npub147ku7p3ddv5vfufheksax3yz3dmj9yxwwfxcq6y7fu3xtxurqeyqake2ga i think he'd settle down for an enemy too, anyone but the preachers (me)
nostr:npub147ku7p3ddv5vfufheksax3yz3dmj9yxwwfxcq6y7fu3xtxurqeyqake2ga is dead, and we killed him
btw, mastodon could display the entire bible without even slowing down, except for load times
nostr:npub109x0x9dlft64y4h9vz9mxu92qpqn752sd8p4xe2zkcanlzmk2fcq3pwvvl
>You could probably find a similar trick for Mastodon or Misskey
there was a trick for mastodon, you could post a giant text (the entire bible) and the script hiding the text broke, so the text was displayed in full. Gargron didn't bitch about bad actors and quietly fixed the issue.
nostr:npub109x0x9dlft64y4h9vz9mxu92qpqn752sd8p4xe2zkcanlzmk2fcq3pwvvl as for Misskey, there was an inverse situation. The messaging order was reversed, and replies from pleroma-be to misskey posts only federated to misskey instances. Lain fixed it, without demanding that syuilo must adhere to the existing convention.
nostr:npub109x0x9dlft64y4h9vz9mxu92qpqn752sd8p4xe2zkcanlzmk2fcq3pwvvl
>You could probably find a similar trick for Mastodon or Misskey
there was a trick for mastodon, you could post a giant text (the entire bible) and the script hiding the text broke, so the text was displayed in full. Gargron didn't bitch about bad actors and quietly fixed the issue.
nostr:npub1q6ynmxgx9yr727a2v2vqmeehz9pu83yekwkfmy8k9dmq505lsycs2dtr82 well, if his behavior on fedi is any indication...
nostr:npub109x0x9dlft64y4h9vz9mxu92qpqn752sd8p4xe2zkcanlzmk2fcq3pwvvl
>Also wasn't there a Pleroma security issue? Why isn't anyone talking about that?
because it was fixed as soon as it was discovered