2024/09/29

Newest at the top

2024-09-29 21:32:52 +0200ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en)
2024-09-29 21:31:33 +0200xal(~xal@mx1.xal.systems) xal
2024-09-29 21:31:13 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Remote host closed the connection)
2024-09-29 21:31:04 +0200xal(~xal@mx1.xal.systems) (Quit: bye)
2024-09-29 21:30:45 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 276 seconds)
2024-09-29 21:30:06 +0200alp(~alp@user/alp) (Remote host closed the connection)
2024-09-29 21:29:28 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-29 21:28:27 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Remote host closed the connection)
2024-09-29 21:26:00 +0200morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-09-29 21:25:39 +0200vglfr(~vglfr@2607:fb91:89c:d5ab:ad3:f757:e3f3:d131) vglfr
2024-09-29 21:25:16 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-09-29 21:25:04 +0200vglfr(~vglfr@2607:fb91:871:453a:ac39:c391:b245:38fc) (Ping timeout: 260 seconds)
2024-09-29 21:16:03 +0200raehik(~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) raehik
2024-09-29 21:15:26 +0200 <haskellbridge> <sm> yes, it kind of is that
2024-09-29 21:15:03 +0200 <haskellbridge> <sm> what do you use ?
2024-09-29 21:14:52 +0200 <deepfire> like it's some sort of golden land of opportunity and adventure
2024-09-29 21:14:29 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-09-29 21:13:56 +0200 <deepfire> ..all this makes me wonder, why do people willingly suffer Matrix..
2024-09-29 21:11:41 +0200td_(~td@i53870935.versanet.de) td_
2024-09-29 21:11:06 +0200vglfr(~vglfr@2607:fb91:871:453a:ac39:c391:b245:38fc) vglfr
2024-09-29 21:10:40 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 265 seconds)
2024-09-29 21:10:09 +0200vglfr(~vglfr@2607:fb91:82c:97cb:ac39:6af1:e36b:6d36) (Ping timeout: 246 seconds)
2024-09-29 21:09:58 +0200td_(~td@i53870906.versanet.de) (Ping timeout: 252 seconds)
2024-09-29 21:09:29 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-09-29 21:07:49 +0200 <mauke> very bizarre
2024-09-29 21:07:11 +0200 <haskellbridge> <mauke> Ah, that did the trick
2024-09-29 21:05:08 +0200 <haskellbridge> <sm> Be careful of the trap! tapping 8 or 9 times risks deactivating account 🤣
2024-09-29 21:04:40 +0200 <haskellbridge> <sm> oh I remember In EX on IOS, in settings, you tap the version string 7 times to unlock a hidden dev settings. :-)
2024-09-29 21:03:58 +0200 <haskellbridge> <sm> mauke: I don't know element android at all, but every version of element I've used has a Clear Cache somewhere in settings
2024-09-29 21:03:51 +0200vglfr(~vglfr@2607:fb91:82c:97cb:ac39:6af1:e36b:6d36) vglfr
2024-09-29 21:03:43 +0200vglfr(~vglfr@2601:14d:4701:3b30:33ba:719b:bbc5:4e3a) (Ping timeout: 252 seconds)
2024-09-29 21:03:25 +0200 <haskellbridge> <sm> I don't know why they don't put you in charge monochrom , we'd get this mess straightened out :)
2024-09-29 21:03:16 +0200 <mauke> there is no Help; About is just a bunch of web links
2024-09-29 21:02:54 +0200 <monochrom> You don't need complexity for stupid bugs. You just need stupidity. Which is pervasive.
2024-09-29 21:02:25 +0200 <haskellbridge> <sm> mauke: it's hidden in Help & About probably
2024-09-29 21:02:22 +0200 <geekosaur> X apparentlyy has some ugly hacl
2024-09-29 21:02:22 +0200 <monochrom> My sister just had a coworker making 2nd-year student mistakes. There is a "char buf[N]" holding a nul-terminated string. It is to be passed to a function that doesn't use the nul-terminated convention, instead the (addr, len) convention. The coworker, like my 2nd-year naive students, wrote "f(buf, sizeof(buf))".
2024-09-29 21:02:21 +0200 <mauke> hah, "Deactivate account" isn't localized
2024-09-29 21:01:54 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 260 seconds)
2024-09-29 21:01:48 +0200 <mauke> sm: I don't see anything about caching in settings
2024-09-29 21:01:28 +0200 <geekosaur> still have no clue why or why it resolved itself eventually
2024-09-29 21:01:01 +0200 <geekosaur> definitely is, I had that bug in some rooms on regular Element for Android but not Element Web or Nheko
2024-09-29 21:01:01 +0200 <haskellbridge> <sm> also they are overloaded/underfunded, so things have to wait
2024-09-29 21:00:40 +0200caconym(~caconym@user/caconym) caconym
2024-09-29 21:00:30 +0200 <mauke> if it can display a timestamp on each message, it can sort by that timestamp
2024-09-29 21:00:18 +0200 <mauke> this is purely a frontend/rendering bug
2024-09-29 21:00:09 +0200 <monochrom> Also, stupid bugs are plentiful.
2024-09-29 21:00:08 +0200 <mauke> which is 2024-09-25 20:25, but it shows after messages on 2024-09-28
2024-09-29 21:00:02 +0200caconym(~caconym@user/caconym) (Quit: bye)
2024-09-29 20:59:59 +0200 <geekosaur> origin server timestamp is about as good as you're going to do