In reply to post 1727045:

dash

wow that sure is
that sure is a function
appreciating how even if you modified it to do *s2++ it would still be wrong because it wouldnt return true if s1 is == s2 and would also actually read a byte past the end of s1 potentially segfaulting

наб

definitely segfaulting because in that case it reads every byte until end of memory yeah

In reply to post 1696092:

alex tax1a

sichuan peppers aren't actually peppers, they're a tree seed!

наб

hm. looks to me like both normal and sichuan pepper are fruit (though, admittedly, different plant order)?

наб

oh nevermind i forgot english overloads pepper(s) to include capsica fruits for some reason (which, also different plant order apparently; though I think in all cases the seeds themselves are largely tasteless); yeah it's fun that you get "pepper" that's a bush or a tree

alex tax1a

yeah — capsica peppers are related to tomatos and sichuan peppers are more closely related to citrus iirc

and yes the seeds of capisca are tasteless but a bunch of white people keep trying to tell our new-mexican ass that the seeds are what's hot

no honey, the only reason you think that is because when people cut the seeds out they also cut the veins of the plant, which are actually the thing that carries the heat.

In reply to post 1630242:

Nire Bryce

they all look good tbh

наб

hm. in many ways i guess this is true but my only point of reference is the 50-year-old chinese woman that always rolls out perfect rectangles and folds identical działzu. truly an indictment of the modern era

In reply to post 1628982:

Xoey

OMFG i love the keysmash sticker

In reply to post 1502610:

Nire Bryce

who put these zeldas in my memory chunk names

In reply to post 1495170:

(unavailable in archive)

In reply to post 1477636:

(unavailable in archive)
наб

how'd you mean?

(unavailable in archive)

In reply to post 1436528:

наб

does this make any sense

In reply to post 1397531:

repo-lookout

Hello there. My name is Thomas and I run the Repo Lookout project. I just wanted to clarify that this is NOT an "extortion" kind of request for money, but -as the email says- more of a "if you like what we're doing, consider supporting the project" kind of request. If you have any further questions, feel free to contact us!

In reply to post 1310764:

Nire Bryce

i have a USB switcher that uses USB3-A to USB3-A cables and when i plug my raspi3 into it as a client it powers the raspi3 through the very wrong USB A socket, so I'm glad to report this is probably still an issue

наб

i think im thick, sorry; what is?

In reply to post 1300915:

Nire Bryce

Lock Heed, Grum Man, and brother? I hurt people.

In reply to post 1277451:

Rev. Dr Five Baker

once you buy it i want a shell account

In reply to post 1260919:

Nire Bryce

it's a toki pona kinda situation where the only numbers are 👍,👆, and 💯

Nire Bryce

*anthropology voice* 🚢 indicates social approval in a rite of passage

наб

ive been using 👽 (because its the only suggested one beside 🙂 and even the least competent maintainer doesn't deserve that) for this purpose, this definitely indicates that this culture believes that codeposting was granted to them as a holy rite by prehistoric aliens

In reply to post 1219052:

alex tax1a

tbf allow_min_user=no is default for a reason, but also lol, lmao.

In reply to post 1172037:

alex tax1a

love too buy 50 bucks worth of bags

In reply to post 1163439:

наб

fixed in sid :)

2023/03/11 19:10:03 socat[19835] E getaddrinfo"szarotka", "pop3s", {1,0,2,0}, {}): Servname not supported for ai_socktype

In reply to post 1163058:

alex tax1a

is the key owned by a different user that isn't in the group?

also we are fuckheads who use dkimproxy and qmail so idk

наб

lmao yes it was owned by root..... because it complained it was owned by != euid != root; i was trying to put the socket into private/ in the postfix chroot instead of a more custom directory, so I made it run as postfix:opendkim instead of opendkim:opendkim, but it appears fundamentally impossible

In reply to post 1148523:

colin

amogapps

наб

SO fuckin true

In reply to post 1107747:

purely dysfunctional catgirl

btw this is 50% of the vertical space in my feed

наб

mine as well, which is why im voting cohost tallposting ergonomics in may; im probably holding it wrong because im not a tumblr enjoyer, soz

In reply to post 1052902:

наб

i just spent like 90 minutes putting 6 wires through 6 holes and only the final two just worked, and i have no clue why. all the others melted in my hand at some point. the majority of the time was spent failing to put a wire through a hole that had already been soldered (and removed, because the two wires that were (supposed to be) next to each other melted together so much they were a dead short) and its just impossible to do that, regardless of position in time or the configuration space. i managed to somehow (a) char and (b) cut straight through the solder mask (iron at 300) during this. top 10 worst time

In reply to post 1050609:

наб

ran it again, its been "Searching for required files" for like ten minutes now

In reply to post 1036295:

наб

sorry for party rocking

fake and gay

does libc refer to something other than the C library on UNIX systems or am I WAY out of my depth

наб

likening development of those to that of semiconductor technology through acronym recombination is indeed the joke here, yes

In reply to post 1027522:

наб

lol why did it suggest #tech review if this is the only post

In reply to post 1020806:

Nire Bryce

it seems like every business is cool with knowing just enough to get to market but then learning nothing else about their product

Nire Bryce

I still see it as a deeply dishonest marketing scheme even if they didn't plan for that -- they expect a high baseline for computer knowledge, and tell people a raspi can work for them... and then SSH is sluggish because of bad PAM credentials on the recommended OS, or because your adapter does not provide quite the right number of watts... for a USB-C device.

наб

idk about USB-C models, but mine is happy to violate the USB standard for power sucking, and indeed they "recommend" USB hosts with 2A current sourcing capability which fundamentally makes no sense; they should've make this like HDMI imo

as for PAM, idk. yescrypt takes like 430ms on this pi zero w which is Fine I Guess, a reference computer takes 30ms, and I don't think anyone expects better and how often do you run yescrypt (once a session? if you're logging in with a passphrase? but then you're logging in with a passphrase, so.); SSH with a RSA4096/SHA256 key takes 1.16s enter-to-prompt which isn't stellar but also Fine I Guess (I don't have other Wi-Fi hosts to log into so the 26ms to my router isn't really meaningful comparison-wise since i see like 25μs RTT there vs 5.6ms to the rpi); the figure jumps to 3.06s when sucket-activating sshd, but meh

the actual interactive usability ime i'd classify as "surprisingly good", to be honest, and I've been interactively debugging the deployment without wanting to off myself (but then i know better than to try to use a 500MHz uniprocessor system for anything processor-intensive, so); lord save you if you want to do heavy I/O though, but I don't, so idk. the default is still shockingly for /tmp on /, and i would probably be singing a different story if i didn't change that every time

but then all the points in the last paragraph are moot if this is advertised as a site and not an embedded/dial-out system (and, really, it's not suitable for the latter either because lol wifi, but a Normal User could potentially use it for that on a default-config bullseye (actual bullseye, not the Foundation's system; that sounds like hell on earth) image and not die probably; or this is a feldspar take), and it's fucking annoying to be used as the former because they're writing author/user fanfic in their documentation. ceterum, the raspberry pi foundation delenda est

really effective as a way of selling adapters and cheaply-rebranded electronic garbage though, you have to admit

наб

idk

Nire Bryce

nah, the PAM thing is that before recently it would cause slow ssh remote sessions because it was causing something else bundled to break, iirc

as for power, with the 3b it needs a constant 5.1v@2.5a, but nothing in the low voltage errors make it clear that even their branded ones cannot hold that constant.

the 4 needs 5/5.1v@3a, which chargers CAN provide

but both depend on cable length and thickness to actually maintain that -- my USB C 2.0 charging cables cannot.

and their solution is bad tutorials and not hardware revisions, if they haven't changed it in the last year.

the low voltage events used to only be shown on the physically connected screen and didn't show up in logs until a few years ago, too.

BUT.

they're cheap so I'm not sure i expect more

наб

lmfao "we sell devices with psychotic power input specs and our own special chargers with the same output phy; they're unrelated tho" really is amazing. i wouldnt request a better voltage either, sounds like an incredible profit incentive for the foundation and its business partners, smart choice :v

but yeah idk, if something's cheap i expect it to have more documentation (or, indeed, more working) than marketing, but maybe thats unreasonably skewed

In reply to post 1015005:

delan

link machine broke :(

наб

i had [](https//elektroda...) lol; fixed

In reply to post 1007063:

purely dysfunctional catgirl

noncompliant RFC3339 implementation? https://ijmacd.github.io/rfc3339-iso8601/

наб

explicit twinkpinion https://github.com/systemd/systemd/issues/5194 :v

In reply to post 1002162:

alex tax1a

wine mono??? like, you have to run the .NET code not just under Mono but under the Windows Mono??? what the Fuck?

наб

idk, when i first tried the exe it gave me "wine mono not installed" (or something to that effect) and early-exited, and i only overcame that after msiexec /iing wine-mono-7.4.0-x86.msi (at which point it started enough to crash for fonts, and I haven't managed to overcome that). there may be problems with my procedure owing to the fact that im (a) stupid and (b) not a prolific wine user, so idk

alex tax1a

dunno that we'd place the stupidity on you here, because i thought the entire shitfucking point of mono is that it didn't have to run inside a win32 environment

наб

well. i saw .exe so i tried wine :v

installing all 300M of mono-complete gave me a different error than just -runtime – https://lfs.nabijaczleweli.xyz/0015-cohost-images/2023-01-15-nabijaczleweli_1002162-gave-up-ran-their-e-screenshot.png – naturally, it doesnt say what the supported version is, im not enough of a C# enjoyer to know, and the exception is from a random address inside the program

running it in wine with wine-mono it still explodes on fonts in System.Windows.Forms.[...] in System.Drawing.FontFamily, and idk how id even tell it to just use whatever; under strace i see it opening every single font fc knows about and I have the fonts package so fuck knows which font it wants (well, except that theres a get_GenericSansSerif() in the call stack, but fuck knows what that means)

well, after finding the ENOENTs, i did ln -s /usr/share/wine/fonts /home/nabijaczleweli/.wine/dosdevices/c:/windows/Fonts which made it work(?!). well, it went to https://lfs.nabijaczleweli.xyz/0015-cohost-images/2023-01-15-nabijaczleweli_1002162-gave-up-ran-their-e-screenshot2.png (the last line does actually repeat every 60s, this is the only wine process), and "OleDb is not implemented." probably means that it can't open the accompanying .mdb MS Access database, so ultimately futile.

In reply to post 993357:

iximeow

oh helllly eah

In reply to post 938284:

Rev. Dr Five Baker

i love that it's called the babtop

In reply to post 924591:

alex tax1a

it says it supports diffie-hellman-group-exchange-sha1 because it supports that kex mechanism in ssh1! ssh2 does not support that kex mechanism!

наб

natch 🥴 that firmware was dated 2014, too. this (and the fact that FTP doesn't support CDUP) reeks of "we've implemented every layer of this system from zilch for some god-forsook reason"

alex tax1a

you've seen the thread where we eviscerate the firmware on the router our ISP tried to fob off on us, right?

https://twitter.com/atax1a/status/1254918692111966208

we had the device for less than 24 hours

наб

oh wow no i haven't that's horrific lmao

alex tax1a

we come out of it the next morning with the openssl dec command in hand and show our friend who works at centurylink and she's like, "you dunce, you could have just asked me for your creds and i'd have looked them up for you" and we're like "but this was more fun"

In reply to post 922578:

A myriad of Qyriad

Anything is better than a PDF

In reply to post 912821:

delan

poggers hair btw :3

In reply to post 906771:

brad emoji

Mismatched threads is my absolute biggest annoyance when it comes to rackmount gear… I’m about to try out Rack Studs instead since they’re purportedly less painful to work with

наб

those do look quite fun (and amazingly expensive to boot), but I don't think they'd help here with a pre-existing thread in the face, right

In reply to post 843284:

наб

https://help.antisoftware.club/support/tickets/7046 :v

Nire Bryce

if it's used like that it's maybe worth continuing to use it like that, but archiving seems a better fit for example 1 and maybe 3. not at all a linguist though

наб

hm yeah i can see that; well you aren't polish which makes you inherently more qualified to have an opinion than either of us; all archive-related text is fresh, hence why im consulting The Anglosphere before committing to any specific grammar for it

Nire Bryce

archival is like, archival ink or an archival system or an archival action.

so like, relating to the field/genre, compare to: "industrial machinery"

I'm not awake enough (and also still sightly intoxicated) to remember what part of speech that is

but in computers it's also used informally on its own I think, but that may also be just non-primary-english speakers. in the end I'm not sure it matters, the point is clear enough even if it's sightly off. If i didn't know you weren't a primary English speaker I would have assumed it was just some Linux/Unix tradition

наб

yes, the adjective form is very much globally attested

the noun form is also attested in the wiktionary (which doesn't cite its source) with a computer-related quote, as the practice of archiving or an instance of archiving

this i can very much find in the BSD dumps – https://lfs.nabijaczleweli.xyz/0015-cohost-images/2023-01-14-archival.png – esp. "tape archival program" (program for tape archival; unsigned) and the big block of notes-file archival in the middle (signed by ray essick from illinois, so.)

i also see noun archival used freely as such via DCS, even in the bits that aren't word salad; given these two, i wouldn't be surprised if this was a modern derivation there had simply been no need for pre-archiving-as-a-fundamental-operation, and having that in documentation gives it staying power

idk, vibes are the only correct tool for linguistic analysis (so its nice that my, loathe though i am to designate it so, computational method agreed with yours) and i roughly agree with your assessment en general

Nire Bryce

I'm not sure it matters that much in the end, people get what's meant, and a lot of computer loanwords don't make sense so it's nbd. language is made up* and changes when people add things

* well, you know what I mean. there's still rules but they're flexible

In reply to post 816238:

наб

(the non-obvious restrixion here, if you're not ratrunpilled, is that this is entirely in the shell+date, with iCals tokenised in AWK; this is perfectly fine for processing the events, but; well.)

In reply to post 795330:

purely dysfunctional catgirl

hahahahaha this bug

I've hit this for years and assumed it was normal

наб

this also says none if you do bash -c '(systemd-detect-virt) and systemd-nspawn if you do dash -c 'exec systemd-detect-virt which decidedly hints that lennart's virtualisation detexion code only worked if the caller was PID 1, which is a normal and sensible requirement, natch.

In reply to post 794842:

lea

controlsee, controlzee, ctrl-Z? maybe it's telling us to take a break :3

In reply to post 774330:

purely dysfunctional catgirl

at least they did apply this one ... eventually

наб

startlingly low bar for a system whose stated goal is "Our efforts emphasize portability, standardization, correctness"; this reminds me, i should repost my script(1) patchset that makes it actually fit for purpose, its apparently been a full year as of yesterday

alex tax1a

we apologize for our preferred firewalling unix

we aren't strong enough to sign up for tech@ yet

наб

save yourself do not do it

alex tax1a

we have a hacked copy of pf_norm.c that we want to send somewhere to start discussion on, though

the reassemble tcp option does 3 things, 2 of which are okay on a modern internet, and the third thing causes problems with hosts behind load balancers that change their tcp timestamp behavior

so we have to do this kind of shit:

===================================================================
RCS file: /cvs/src/sys/net/pf_norm.c,v
retrieving revision 1.224
diff -u -p -u -r1.224 pf_norm.c
--- net/pf_norm.c	22 Aug 2022 20:35:39 -0000	1.224
+++ net/pf_norm.c	3 Jan 2023 17:28:32 -0000
@@ -1294,8 +1294,8 @@ pf_normalize_tcp_stateful(struct pf_pdes
 
 			if (got_ts) {
 				/* Huh?  Multiple timestamps!? */
-				if (pf_status.debug >= LOG_NOTICE) {
-					log(LOG_NOTICE,
+				if (pf_status.debug >= LOG_ERR) {
+					log(LOG_ERR,
 					    "pf: %s: multiple TS??", __func__);
 					pf_print_state(state);
 					addlog("\n");
@@ -1469,23 +1469,23 @@ pf_normalize_tcp_stateful(struct pf_pdes
 			 *   an old timestamp.
 			 */
 
-			DPFPRINTF(LOG_NOTICE, "Timestamp failed %c%c%c%c",
+			DPFPRINTF(LOG_ERR, "Timestamp failed %c%c%c%c",
 			    SEQ_LT(tsval, dst->scrub->pfss_tsecr) ? '0' : ' ',
 			    SEQ_GT(tsval, src->scrub->pfss_tsval +
 			    tsval_from_last) ? '1' : ' ',
 			    SEQ_GT(tsecr, dst->scrub->pfss_tsval) ? '2' : ' ',
 			    SEQ_LT(tsecr, dst->scrub->pfss_tsval0)? '3' : ' ');
-			DPFPRINTF(LOG_NOTICE, " tsval: %u  tsecr: %u  "
+			DPFPRINTF(LOG_ERR, " tsval: %u  tsecr: %u  "
 			    "+ticks: %u  idle: %llu.%06lus", tsval, tsecr,
 			    tsval_from_last, (long long)delta_ts.tv_sec,
 			    delta_ts.tv_usec);
-			DPFPRINTF(LOG_NOTICE, " src->tsval: %u  tsecr: %u",
+			DPFPRINTF(LOG_ERR, " src->tsval: %u  tsecr: %u",
 			    src->scrub->pfss_tsval, src->scrub->pfss_tsecr);
-			DPFPRINTF(LOG_NOTICE, " dst->tsval: %u  tsecr: %u  "
+			DPFPRINTF(LOG_ERR, " dst->tsval: %u  tsecr: %u  "
 			    "tsval0: %u", dst->scrub->pfss_tsval,
 			    dst->scrub->pfss_tsecr, dst->scrub->pfss_tsval0);
-			if (pf_status.debug >= LOG_NOTICE) {
-				log(LOG_NOTICE, "pf: ");
+			if (pf_status.debug >= LOG_ERR) {
+				log(LOG_ERR, "pf: ");
 				pf_print_state(state);
 				pf_print_flags(th->th_flags);
 				addlog("\n");
@@ -1531,16 +1531,14 @@ pf_normalize_tcp_stateful(struct pf_pdes
 			 * Hey!  Someone tried to sneak a packet in.  Or the
 			 * stack changed its RFC1323 behavior?!?!
 			 */
-			if (pf_status.debug >= LOG_NOTICE) {
-				log(LOG_NOTICE,
+			if (pf_status.debug >= LOG_ERR) {
+				log(LOG_ERR,
 				    "pf: did not receive expected RFC1323 "
 				    "timestamp");
 				pf_print_state(state);
 				pf_print_flags(th->th_flags);
 				addlog("\n");
 			}
-			REASON_SET(reason, PFRES_TS);
-			return (PF_DROP);
 		}
 	}
 
наб

we may be observing the first patch in cohost comments. soon we may see the first patch sent upstream via the same method

i mean, im not subscribed either, you just click through/reply to a confirmation mail from the list, people usually group-reply when you tell them to ime

idk i like logically understand what the option does and how the diff changes it but i dont get why you'd care in the first place. maybe im not infosec/tcppilled enough
always a good sign when something that hinges on "current host behaviour" blames to 20 years ago and cites solaris 2 tho

alex tax1a

really for this patch to be mature it needs to split those three reassembly features controlled by reassemble tcp out into their own options.

the reason we care is that, apparently, some load balancers will start off connections with timestamps and then pass to backends without them, or with fucky timestamps, which makes client connections stall and time out.

we want the other reassembly features, though, so we dike out this one

because we also have to rebuild our kernel to enable PPPOE_TERM_UNKNOWN_SESSIONS, and we eventually also want to patch it such that this option becomes a link-time flag on the interface instead of a compile-time flag on the entire pppoe driver. but also effort.

наб

that was more of a royal you, because the manual is phrased as "Attacker Might" and that usually means an impossible scenario one needs to be infosec brain-poisoned to be concerned with. am I right to read that gaining/losing the parameter mid-session is legal and would Just Work, but the normaliser considers it an Attacker Might and drops the packet ⇒ clients time out?

hm, maybe my ISP is better-behaved since I've never observed this with rp-pppoe, which just tries 3 PADIs for up to 30 seconds total, and I don't see any termination code in the discovery path; maybe if you see that a lot it may make sense to pick up the connection instead of re-discovering à la rp_pppoe_sess/pppoe -e (i cant believe being the only rp-pppoe poster in 20 years is somehow relevant; a cursory glance at Ox ifconfig(8) shows that's impossible but maybe i cant read)

alex tax1a

oh! we only see this when we're doing CARP failover — ifstated on each box takes the physical upstream interface up or down based on CARP status.

Without TERMing the unknown session, during failover, there's a 60 second lacuna where the old session is still active on the PPPoEAC and the new one won't establish. With TERMing the unknown session, the failover becomes almost completely transparent. At most a minor pause.

Truly the correct solution here would be to teach CARP how to float the PPP session ID across the link.

In reply to post 751053:

наб

the strongest system in the world. howeve'r it is so fragile so as to shatter if it saw | git -C src am

In reply to post 738880:

alex tax1a

they're spamming you with swaks? swaks

наб

composed in swaks for amazonses relay it seems, yeah; is this the poster showing their ass?

alex tax1a

just utterly baffled as to how one can know about swaks to sling SMTP, and not hack it to remove the extremely obvious "this was sent with swaks" tags. amateur hour.

In reply to post 733327:

colin

poggggg

good work, big yellow

In reply to post 718768:

наб

today, on gags with a target audience of like five people,

In reply to post 716823:

iximeow

no

edit: but god i wish

In reply to post 685809:

(unavailable in archive)

In reply to post 673523:

delan

these berkeley mfs said NEGLIENCE

наб

uhoh, thats my post-processing that fucked it, the original does say NEGLIGENCE

In reply to post 602411:

alex tax1a

bigposting is okay

In reply to post 581468:

наб

day 6 is also seq 4 Inf | while read -r n; do [ $(cut -b $((n-3))-$n input | sed 's/./&\n/g' | sort -u | wc -l) -eq 5 ] && { echo $n; exit; }; done (and tune the numbers for part 2) but that's too embarrassing for the main body even for me

In reply to post 577937:

Janet

there was an attempt

In reply to post 559928:

purely dysfunctional catgirl

no idea. i also get breakage or missing stuff on not-unstable distros so like. ??? all computers don't work, no idea how anyone who doesn't have the curse of knowledge gets anything done.

наб

both of my recent debbugs adventures would've been avoided by being even on testing, since they're both so recent and so grave they would've never migrated; in general i think being On Sid means you run into the bugs that are Not Fit For The End-User ("no mesa" or "dkms injects a make flag that silently explodes your module"), which is a distinctly Worse class of bugs for normal people to encounter than "it works but kinda shittily". indeed, the user in question has been In The Field longer than I've been alive and she's more than capable of resolving bugs that aren't down-right arcane

наб

guess what im driving at is "computer kinda ass" is universal, yeah, but "computer now decorative" is not a problem class you encounter if you aren't on The Bleeding Edge™ i think am i making any sense sorry

purely dysfunctional catgirl

mmm. I've been using Arch and NixOS unstable for most of my time suffering computers and I've never had that severity of distro bug. NixOS unstable i feel like is way more yolo but has integration tests that catch most of this stuff

In reply to post 548840:

наб

user posts least novel technique, asked to leave cohost

eater

why is it in a reading state tho

наб

how do you mean? it's Running because its taking 100% of the CPU, but reading?

In reply to post 506597:

alex tax1a

it's very cool to see "<sys/types.h> doesn't exist" in the log

we would simply become unhinged upon seeing this, ourselves.

In reply to post 500865:

delan

IFS=$' \t\r\n' it’s basically word splitting!

In reply to post 472033:

iximeow

we love when renal function improves

In reply to post 451223:

Nire Bryce

whoa nice nail

In reply to post 437369:

наб

previously: https://twitter.com/nabijaczleweli/status/1583877641362239488

In reply to post 428780:

🦦alice

eggbug inside!

Curi Lagann

"Has anyone does this yet?" WHAT A HUMBLE BRAG <3

xXSC33N3QU33NXx

sadly my machine is Merced,,,

Cat

eggbug inside!! I will buy some of these stickers if you start making them :)

In reply to post 396121:

delan

are you sure i don’t?

наб

its like this german deployment of ground-ground self-propelled warheads, except splotchy's feline jaw geometry is better suited for low-area-of-effect low-collateral targets (and im not german): https://youtu.be/XpbDMo8an5w?t=713

In reply to post 305843:

наб

also why cant i paste in images; this is (technical term) "fucking agony"