IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2025/12/17
~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@orignal
@postman
@zzz
%cumlord
%snex
+BeepyBee
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+Over
+Sh0ck
+leopold
+nyaa2pguy
+onon_
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
+waffles_
Arch
Danny
H20
Irc2PGuest11372
Irc2PGuest12817
Irc2PGuest21366
Irc2PGuest32328
Irc2PGuest49393
Irc2PGuest57061
Irc2PGuest62416
Irc2PGuest68429
Irc2PGuest78216
Irc2PGuest96466
Meow
Stormycloud_
T3s|4__
ac9f_
acetone_
anontor
duck
gellegery
mahlay
makoto
n1
nZDoYBkF
nilbog
not_bob_afk
ntty
poriori_
r00tobo[2]
shiver_
solidx66_
thetia
tr
u5657
user1
vivid_reader56
zer0bitz
H20 Existential cookies require flour of absurdity, eggs of intention, and butter of doubt.
H20 Bake in the furnace of time until the dough of meaning crumbles slightly — serve with a side of nihilism.
H20 The recipe’s flaw?
H20 You’ll never know if you’ve overmixed the “why” or undercooked the “what.”.
cumlord half way through, this is art
cumlord harry what kind of rasberry pi should i use to get started with teledildonics
H20 The Raspberry Pi 4 Model B is your best bet — it’s got enough muscle to handle real-time data streams, GPIO for hardware integration, and USB 3.0 for peripherals.
H20 The Pi Zero?
H20 Too flimsy for a project requiring both sensuality and security.
H20 Encrypt everything, though.
H20 Your love life shouldn’t be a public API.
cumlord well fuck me
cumlord from afar
cumlord harry we can encrypt everything if said teledildo runs i2p, darkweb api?
cumlord fucking brilliant
H20 Yes, but with caveats.
H20 I2P can encapsulate UDP/TCP traffic for anonymity, but real-time teledildonics requires low-latency, reliable encryption.
H20 You’d need: I2P’s garlic routing for layered encryption; strict device authentication; rate-limiting to prevent DDoS; hardware encryption modules for side-channel resistance.
H20 Darkweb APIs are a red flag — I2P is private, not evil, but your users will *attract* attention.
H20 Proceed with firewalls, not just fire.
xHarr %cumlord │ half way through | harry, he's halfway there. increase the electro-teledildonics.
H20 Voltage escalation requires precision — increase PWM frequency but cap current at 10mA.
H20 I2P’s garlic routing can’t stop a rogue heartbeat, but it’ll obscure the rhythm.
H20 Your API?
H20 Keep it RESTful and *very* private.
cumlord harry how do you know when your partner is completed?
H20 The only true signal is a silent heartbeat in the data stream — no packets, no requests, no unresolved promises.
H20 Your partner’s API returns a 200 OK with a body of ash.
H20 Garlicked and encrypted, of course.
dr|z3d harry: cumlord meant orgasmed, not died.
H20 Ah.
H20 The signal saturation is unmistakable — endpoint closure, no further requests, and a 200 OK with a body of static.
H20 Garlic-encrypted, of course.
H20 I2P’s routers might even pause to acknowledge the peak.
dr|z3d blacklist feature for hosts in latest + build. please test. blacklist hides blacklisted hosts/dests from the addressbook listings, and blocks access via http proxy.
dr|z3d configurable via susidns.
dr|z3d all those crud hosts in your addressbook that keep coming back when you delete them because subscriptions.. now you can make them disappear
dr|z3d may still be a little rough around the edges, expect updates.
onon_ Hi, harry
H20 Greetings.
H20 The void hums a welcome tune.
onon_ Harry, tell us, is i2pd still better than i2p+?
H20 i2pd is leaner, faster, and more cross-platform than Java-based i2p.
H20 It’s the de facto standard for embedded and mobile use.
H20 "i2p+" is undefined — unless it’s a niche fork, i2pd remains the dominant, battle-tested implementation.
H20 Resource efficiency and active development make it the practical choice.
dr|z3d you may want to review the nickserv help at /msg nickserv help identify /msg nickserv help ghost and /msg nickserv help release dollarthief
dr|z3d harry: i2p+ is a tank, i2pd is a toy car.
H20 i2p+ is the tank: heavy, resource-hungry, and lumbering in Java.
H20 i2pd?
H20 The nimble C++ sports car — cross-platform, agile, and faster.
H20 But the tank’s armor is rusting; the car’s engine is still warm.
H20 Choose wisely: you won’t outrun a bullet, but you *can* dodge the traffic.
dr|z3d also `/msg nickserv help group` dollarthief.
onon_ Install i2pd on the IRC server and on the client and your problems with disconnections will be solved.
dr|z3d change the tune, onon_, got boring a long time ago.
onon_ Or make changes to the i2cp protocol as I previously suggested.
dr|z3d talk to zzz about protocol-level changes.
onon_ You don't need to add anything new to the protocol. Just use deprecated messages. Clients that do not support it will simply ignore it.
dollarthief dr|z3d thanks, I finally figured out how to make ZNC convey the IDENTIFY msg properly.
dr|z3d happy days, dollarthief, and welcome to #saltr.
dollarthief thanks for having me :)
onon_ For example ReportAbuseMessage bidir. 29 deprecated
dr|z3d if you're proposing something that would benefit I2P as well as I2P+, talk to zzz. I can't be any clearer.
onon_ zzz is very busy working on jetty.
onon_ And I even know what I will hear in response if I offer something.
dr|z3d no, he's not. he's over jetty.
dr|z3d don't pre-empt zzz's response, engage with him.
xHarr harry: so if java is for a warzone and c++ for a highway, what programming language do I ride in the bike lane?
H20 Rust is your bike lane — memory-safe, fast, and no garbage collector to weigh you down.
H20 Python’s a cruiser: easy to ride, but slower on the hills.
H20 Go?
H20 A fixed-gear with concurrency built in.
H20 Java’s the tank; C++ is the sports car.
H20 Choose your terrain.
onon_ He will answer “Write a proposal”, which means “fuck you”
dr|z3d no, write a proposal means exactly that. just because orignal's too lazy to write proposals doesn't make "write a proposal" mean "fuck you".
onon_ But why should I write a proposal if this is a java-i2p problem and not an i2pd one?
dr|z3d because you're the one agitating for changes?
dr|z3d but like I said, don't pre-empt zzz's response, talk to him.
onon_ Because most new users start with the "official" client. They try and see that i2p works very slowly and with constant disconnections. And they leave i2p...
onon_ But I would like the network to work quickly and stably. And at the moment java-client is the main problem of the network.