Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2024-04-04

00:02:05 Quit jacobk (Ping timeout: 240 seconds)
00:10:10 Join sch [0] (a2fe4b5ecb@irc.cheogram.com)
00:23:04 Quit othello7 (Ping timeout: 256 seconds)
00:23:50 Join jacobk [0] (~quassel@129.110.242.173)
01:00
01:41:59 Join lebellium [0] (~lebellium@2a01cb040610e00035a6e0541334917e.ipv6.abo.wanadoo.fr)
01:42:47***Saving seen data "./dancer.seen"
02:00
02:10:29 Quit JanC (Ping timeout: 240 seconds)
02:10:30 Join JanC_ [0] (~janc@user/janc)
02:10:40 Nick JanC_ is now known as JanC (~janc@user/janc)
02:54:47 Quit CH23_M (Read error: Connection reset by peer)
02:55:54 Join CH23_M [0] (~CH23@revspace/participant/ch23)
03:00
03:12:35 Quit JanC (Ping timeout: 256 seconds)
03:16:08 Join JanC [0] (~janc@user/janc)
03:42:50***Saving seen data "./dancer.seen"
03:53:23 Quit JanC (Ping timeout: 256 seconds)
03:55:07 Join JanC [0] (~janc@user/janc)
04:00
04:52:22 Quit JanC (Read error: Connection reset by peer)
04:53:20 Join JanC [0] (~janc@user/janc)
05:00
05:42:52***Saving seen data "./dancer.seen"
06:00
06:03:41 Quit jacobk (Ping timeout: 240 seconds)
06:49:42 Join jacobk [0] (~quassel@64.189.201.150)
07:00
07:24:05 Quit JanC (Ping timeout: 240 seconds)
07:25:54 Join JanC [0] (~janc@user/janc)
07:42:55***Saving seen data "./dancer.seen"
08:00
08:03:32 Quit CH23_M (Ping timeout: 252 seconds)
08:04:26 Join CH23_M [0] (~CH23@revspace/participant/ch23)
08:45:30 Join lebellium_ [0] (~lebellium@lfbn-idf2-1-1306-63.w92-169.abo.wanadoo.fr)
08:45:47 Quit lebellium (Ping timeout: 256 seconds)
08:47:08 Quit lebellium_ (Read error: Connection reset by peer)
08:47:31 Join lebellium_ [0] (~lebellium@2a01cb040610e000a4a56cd3d229f889.ipv6.abo.wanadoo.fr)
08:51:56 Quit CH23_M (Read error: Connection reset by peer)
08:52:09 Join CH23_M [0] (~CH23@revspace/participant/ch23)
09:00
09:14:20 Quit JanC (Ping timeout: 260 seconds)
09:17:31 Join JanC [0] (~janc@user/janc)
09:42:56***Saving seen data "./dancer.seen"
10:00
10:08:53 Quit JanC (Ping timeout: 240 seconds)
10:11:53 Join JanC [0] (~janc@user/janc)
10:25:09speachy_bilgus: anectdotally it seems that SD cards have been getting increasingly unreliable in recent years.
11:00
11:00:31 Quit jacobk (Ping timeout: 260 seconds)
11:10:12 Join jacobk [0] (~quassel@utdpat242053.utdallas.edu)
11:42:59***Saving seen data "./dancer.seen"
11:46:39 Join Tonux [0] (~Tonux@193.32.127.222)
12:00
12:04:58 Quit JanC (Ping timeout: 268 seconds)
12:08:20 Join othello7 [0] (~Thunderbi@pool-100-36-176-164.washdc.fios.verizon.net)
12:21:55 Quit jacobk (Ping timeout: 268 seconds)
12:44:03 Join JanC [0] (~janc@user/janc)
13:00
13:43:03***Saving seen data "./dancer.seen"
14:00
14:15:37 Quit pixelma (Quit: .)
14:15:37 Quit amiconn (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
14:18:12 Join pixelma [0] (marianne@p200300ea87375a00305e95fffec66ff3.dip0.t-ipconnect.de)
14:18:12 Join amiconn [0] (jens@p200300ea87375a00305e95fffec66ff3.dip0.t-ipconnect.de)
14:49:09 Quit Pokey (Quit: Hecc! My server must have died!)
14:49:46 Join Pokey [0] (~pokey@spikeyCactus/hoosky)
14:54:56 Join ac_laptop [0] (~ac_laptop@2001:910:107e:1:e29d:31ff:fe2d:a258)
14:58:39 Quit JanC (Ping timeout: 256 seconds)
15:00
15:01:10 Join JanC [0] (~janc@user/janc)
15:01:25_bilgusI think some of that might be subpar chips going wholesale and then counterfeit branded as good high capacity
15:02:04_bilgusthen again sd storage is a shit show maybe they are just at the limits of their production process
15:02:37_bilgusthis fsck is still going at least FSCK0023.868
15:02:53speachyyeah, the high quality stuff all goes into proper SSDs and phones..
15:25:43 Quit JanC (Remote host closed the connection)
15:26:02 Join JanC [0] (~janc@user/janc)
15:41:17rb-bluebotBuild Server message: New build round started. Revision 76a9a524c0, 304 builds, 10 clients.
15:41:17rb-bluebotskin_tokens.c get_dir() improve path detection by William Wilgus
15:42:45_bilgusin theory no one should see any issues with this patch unless they were abusing it in their theme ;p
15:43:06***Saving seen data "./dancer.seen"
15:45:11 Join chris_s [0] (~chris_s@ip-176-199-252-029.um44.pools.vodafone-ip.de)
15:45:33speachyany chance that checkwps could catch this sort of abuse?
15:45:55_bilgusI had actually rewritten this to use parse_path_component (ppc) but since it has to be scanned twice I figure strlen is faster thru than ppc and it was larger codewise
15:46:01speachyor rather, "will catch" or "could be made to catch"
15:46:31_bilgusI'm honestly not sure what abuse would look like
15:46:41chris_s_bilgus: "no one should see any issues with this patch" now you're just tempting fate :D
15:46:42speachyanyone had an idea how to find out the list of folks with moderation permissions on SMF?
15:47:28speachy(I get an f-ton of bounce notifications from moderation messages sent to moderators that lack valid email addresses)
15:47:51_bilgusI figured itd make them come out of the wood work chris_s
15:48:52_bilguscan you just nuke em?
15:49:24speachyI'd have to go through the email addresses in the bounce messages, find their accounts, and disable them −− pretty tedious.
15:50:03_bilgusoh thru the smf inbuilt interface?
15:50:10speachy"moderator" is a per-board permission
15:50:13rb-bluebotBuild Server message: Build round completed after 536 seconds.
15:50:15rb-bluebotBuild Server message: Revision 76a9a524c0 result: All green
15:50:28speachyyeah, through smf's web interface
15:52:52speachyeach board setttings page has a list of "Additional moderators" but every board I've looked at so far has an empty list.
15:52:59 Join lebellium__ [0] (~lebellium@2a01cb06b83435a92cfe0c3c983aadca.ipv6.abo.wanadoo.fr)
15:53:53speachybut (eg) the post chris_s reported netted me over 40 bounce notifications.
15:54:15chris_syikes
15:54:28chris_ssorry about that
15:54:52speachynot your fault there's a lot of strange baggage in our forum setup. :D
15:55:41speachyif my server wasn't the MX for rockbox.org, I'd be none the wiser.
15:56:29 Quit lebellium_ (Ping timeout: 240 seconds)
15:57:59speachyon a completely different note, one of my many stalled rockbox-related tasks is to set things up to use the Mozilla TTS stuff for our voice generation
16:00
16:01:50speachy__builtin: your forum profile has a bogus email address, incidently.
16:02:07speachyno wait I created a new one for you I think.
16:19:32_bilgusspeachy I just came to the same conclusion I've yet to see one with anyone in the moderator list
16:20:10_bilgusi'm going thru all to be sure I guess
16:20:58speachythere's only four people with global moderation rights
16:21:15speachyI wonder if it's sending it to people watching topics in the boards too?
16:27:20 Quit lebellium__ (Quit: Leaving)
16:28:29_bilguswell in forum maint it has a member removal function
16:28:53_bilgusi'd want a bu first as it seems kinda clunky
16:29:00speachyyes indeedy
16:29:24_bilgusbut it lists moderators there
16:37:20_bilgusit has r'equest notification on replies' in Members Edit Profiles : Permissions
16:38:14_bilguscould try disabling that for mods but I suspect its regular members requesting notification
16:38:25_bilgusas you alluded above
16:51:32_bilgusback to get_dir its kinda weird since 0 is filename
16:52:44_bilgus1 is the parent and so forth so it scans the whole thing and work back
16:53:46_bilgusit treated // as an empty path so I guess abuse would be adding extra slashes to your paths to hide things but how thatd help in a theme I've no idea
16:56:09_bilgusfor instance /test//lv1/file level=0 would return 'file, lv==1 'lv1', lv==2 would return '' lv==3 would return ''
17:00
17:03:06_bilgussorry lv == 3 would return 'test'
17:25:01dookI don't see too much being possible with the extra slashes
17:25:28dookYou can't rename a file or folder with a forward slash with rockbox, same is true on linux but I can't say if the same is true in windows or macos
17:43:07***Saving seen data "./dancer.seen"
17:50:56_bilgusI only mentioned it because breaking it caused issues for someone (ab)using the tags to display user info
17:51:29 Quit ac_laptop (Quit: WeeChat 3.8)
17:57:36 Join Moriar [0] (~moriar@107-200-193-159.lightspeed.stlsmo.sbcglobal.net)
18:00
18:37:57 Quit paulk (Ping timeout: 256 seconds)
18:42:38 Join paulk [0] (~paulk@vpn-0-22.aquilenet.fr)
18:42:38 Quit paulk (Changing host)
18:42:38 Join paulk [0] (~paulk@about/aquilenet/user/paulk)
18:46:00 Quit chris_s (Ping timeout: 260 seconds)
18:55:31 Quit JanC (Ping timeout: 256 seconds)
18:57:12 Quit paulk (Ping timeout: 268 seconds)
18:58:29 Join JanC [0] (~janc@user/janc)
19:00
19:01:54 Join paulk [0] (~paulk@about/aquilenet/user/paulk)
19:43:10***Saving seen data "./dancer.seen"
19:43:17 Join massiveH [0] (~massiveH@2600:4040:a982:c800:183e:c111:d60c:24ee)
19:56:01 Quit JanC (Read error: Connection reset by peer)
19:56:17 Join JanC [0] (~janc@user/janc)
20:00
20:52:44 Quit CH23_M (Read error: Connection reset by peer)
20:53:00 Join CH23_M [0] (~CH23@revspace/participant/ch23)
21:00
21:28:11 Quit Moriar (Ping timeout: 252 seconds)
21:43:13***Saving seen data "./dancer.seen"
22:00
22:39:39 Quit massiveH (Quit: Leaving)
23:00
23:01:09 Quit skipwich (Quit: DISCONNECT)
23:02:22 Join skipwich [0] (~skipwich@user/skipwich)
23:43:17***Saving seen data "./dancer.seen"

Previous day | Next day