--- Log for 06.12.122  Server: lithium.libera.chat  Channel: #rockbox
--- Nick: rb-logbot  Version: Dancer V4.16  Started: 10 days and 12 hours ago

00.45.58 Quit    massiveH (Quit: Leaving)
01.18.55 Join    advcomp2019__ [0] (~advcomp20@user/advcomp2019)
01.22.59 Quit    advcomp2019_ (Ping timeout: 264 seconds)
01.52.12 ***     Saving seen data "./dancer.seen"
03.31.46 Join    mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
03.52.14 ***     No seen item changed, no save performed.
04.00.03 Quit    underpantsgnome[ (Quit: You have been kicked for being idle)
04.03.24 Join    advcomp2019_ [0] (~advcomp20@user/advcomp2019)
04.07.05 Quit    advcomp2019__ (Ping timeout: 260 seconds)
04.50.59 Quit    advcomp2019_ (Read error: Connection reset by peer)
04.51.23 Join    advcomp2019_ [0] (~advcomp20@user/advcomp2019)
05.34.01 Quit    CH23_M (Read error: Connection reset by peer)
05.34.23 Join    CH23_M [0] (~CH23@revspace/participant/ch23)
05.52.18 ***     Saving seen data "./dancer.seen"
07.28.04 Quit    CH23_M (Ping timeout: 256 seconds)
07.28.53 Join    CH23_M [0] (~CH23@revspace/participant/ch23)
07.52.19 ***     Saving seen data "./dancer.seen"
08.39.12 Quit    CH23_M (Read error: Connection reset by peer)
08.39.31 Join    CH23_M [0] (~CH23@revspace/participant/ch23)
09.15.30 Quit    advcomp2019_ (Read error: Connection reset by peer)
09.15.53 Join    advcomp2019_ [0] (~advcomp20@user/advcomp2019)
09.25.38 #       <speachy> if y'all want to kick off builds or whatever go for it.  We might as well carry on as usual until we're in the final migration phases.
09.52.22 ***     Saving seen data "./dancer.seen"
09.54.00 #       <speachy> so there's still some movement on the saga, but it does seem prudent to move elsewhere.  
09.54.01 #       <speachy> https://twitter.com/fosshostorg
10.05.10 Quit    jacobk (Ping timeout: 252 seconds)
10.21.49 Join    jacobk [0] (~quassel@utdpat242097.utdallas.edu)
10.25.12 Quit    jacobk (Read error: Connection reset by peer)
11.00.16 Join    bilgus_ph [0] (~bilgus_ph@172.58.203.69)
11.02.44 #       <bilgus_ph> Or is this a power struggle coup attempt if its not a dire situation anymore maybe we should shop around or leave the wiki there and move the rest?
11.03.26 #       <bilgus_ph> Sounds like all is not well at fosshost
11.04.10 #       <speachy> hmm, there's something to be said for splitting the wiki off.
11.06.19 #       <bilgus_ph> Bahaus was successful at running builds on github with some fleshing out that could become a viable backup as well
11.06.34 #       <bilgus_ph> Till they start charging ofc
11.08.11 #       <speachy> I don't want to change what works (well).  Right now that really signles out the wiki for orbital bombardment.
11.08.28 #       <bilgus_ph> That said I've been busy AF this year and last I hope to be in a better time situation for 2023 to try and get back to all that rockbox.. Jazz?
11.09.24 #       <bilgus_ph> Making it static is still an option that we could work on
11.10.30 #       <bilgus_ph> Lower the load so we could get away with cheaper hosting
11.11.03 #       <speachy> we have three prongs; memory, disk space, and compute.
11.11.52 #       <speachy> not a lot of compute happens there.  what we really need is RAM (gerrit's the worst offender)
11.12.16 #       <bilgus_ph> Would have guessed the forum
11.14.10 Quit    mink (Ping timeout: 256 seconds)
11.14.45 Join    mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
11.14.48 #       <speachy> we could save a marginal amount by asking for 160GB but then we'd not really have any room to grow should we need it.
11.15.09 #       <speachy> they only seem to offer larger RAM instances with more vCPUs, and that's where we are
11.16.17 #       <speachy> the wiki is very spiky; making the main view of that static would save a lot of oomph, and we could make the entire "dynamic" wiki login only to deter bots.  That's probably a good first step.
11.16.55 #       <speachy> I didn't have the time to create sane-looking static export template, alas.
11.17.17 #       <bilgus_ph> And I failed miserably at it
11.17.26 #       <speachy> but it _did_ work.
11.18.37 #       <speachy> I could also try again on a foswiki2 migration; it worked okay-ish modulo a sane template until I broke something and it all went sideways.
11.18.38 #       <bilgus_ph> At this point there are some important pages in there but its not the end of the world as long as the info is still accessible
11.19.15 #       <speachy> but that was when the host was having some particularly pathological performance problems
11.20.33 #       <speachy> (...if I had more bandwidth here...)
11.21.27 #       <speachy> I have three (beefy) servers powered down, including the one that was hosting rockbox prior to the fosshost move.
11.23.50 Quit    bilgus_ph (Quit: Connection closed)
11.24.51 #       <speachy> I'm hoping over the xmas-ish period I'll have some time to put into this stuff.  Wiki first; the rest can follow.
11.27.07 #       <speachy> anyhoo.  moving to a new host is effectively just a transfer-n-restart cycle.  I don't want to complicate it beyond that.
11.27.40 Join    bilgus_ph [0] (~bilgus_ph@172.58.203.16)
11.28.22 Join    jacobk [0] (~quassel@utdpat241106.utdallas.edu)
11.28.45 Quit    mink (Remote host closed the connection)
11.29.07 #       <bilgus_ph> yeah your time is just as important as the other monetary concerns
11.33.06 Quit    jacobk (Ping timeout: 255 seconds)
11.37.01 #       <Richard42> sorry bilgus_ph I just saw your suggestion now. last night I dug through the code and figured out what was going on and just submitted another change which does fix the backlight going off too early problem
11.37.03 Join    jacobk [0] (~quassel@utdpat241035.utdallas.edu)
11.37.17 #       <Richard42> if you want I can rewrite it to use the virtual button as you suggested
11.42.47 #       <Serke> Seeing that you guys have been tinkering with bookmark code recently, it occured to me that now would be a good time to report a minor bug I've been slightly annoyed with since forever (as a Sansa Clip+ user).
11.43.05 #       <Serke> After creating/updating a bookmark I'm sometimes taken to the main menu and sometimes to the bookmarks menu - there's no consistency, it seems to be arbitrary.
11.43.22 #       <Serke> It doesn't sound like a big deal (and indeed, it isn't), but it's still annoying, since in order to leave the main menu one has to press 'home' and to leave the bookmarks menu one is required to use 'back/rewind' button - pressing 'home' will bring up 'delete?' (bookmark) menu and one has to be careful not to delete the bookmark accidentally.
11.43.38 #       <Serke> Basically that means that you can't depend on being able to find your way back without looking at the screen first to confirm your current location.
11.52.00 Join    chris_s [0] (~chris_s@ip-095-223-073-220.um35.pools.vodafone-ip.de)
11.52.25 Join    advcomp2019__ [0] (~advcomp20@user/advcomp2019)
11.52.27 ***     Saving seen data "./dancer.seen"
11.55.29 Quit    advcomp2019_ (Ping timeout: 246 seconds)
11.56.21 #       <chris_s> Serke: Do you mean, after selecting a bookmark from the "Recent Bookmarks" screen? I think you are returned to that screen (only, I think) when you had started playback from there and basically didn't access another screen apart from the WPS in the meantime.
11.56.25 #       <chris_s> My guess is, that behavior has probably developed more by accident than anything else
11.57.41 #       <chris_s> uh, I forgot to add "after stopping playback" – that's when you are returned to the screen
11.58.13 #       <chris_s> there's a logic to it, but it seems somewhat ill-defined
12.00.55 #       <Serke> No, I mean immediately after creating a bookmark (or updating one) by pressing 'power' button (I believe it's called 'bookmark on stop')
12.03.18 #       <chris_s> Which screen are you returned to though? Aren't you talking about Recent bookmarks in the root menu?
12.04.58 #       <Serke> That's the thing - sometimes I'm returned to the 'Recent bookmarks' and sometimes to the Rockbox main menu.
12.05.22 #       <Serke> That is, one level up from the 'Recent bookmarks'
12.06.04 #       <chris_s> Yeah. It *should* depend on whether you started playback from that menu – and then didn't switch away from the WPS to somewhere else before pressing the power button.
12.07.04 #       <chris_s> e.g. if you open the playlist viewer afterwards, and only then press Power, you'll be returned to the main menu instead
12.07.55 #       <chris_s> which, I agree, is not necessarily what you would expect
12.09.18 #       <chris_s> That is, unless I'm missing something, it doesn't actually depend on whether a bookmark is created or updated when stopping playback
12.11.07 #       <Serke> Oh, I see. 
12.11.48 #       <chris_s> The only question is whether it should ever return to the Bookmarks menu (or do it more consistenly). It would be easy to change it so it never does.
12.14.39 #       <bilgus_ph> richard42 I haven't looked at your submission if you have time the virtual key way might be cleaner but tbh idk if it'll work but I can throw something together tonight if you dont
12.15.33 #       <chris_s> A separate concern is whether buttons, especially the Home button, should behave so differently on the Bookmarks screen (probably not :D  , but it's possible there was no other sensible option for assigning the Delete hotkey in the case of the Sansa Clip+)
12.38.33 #       <Serke> Can't speak for all users of Sansa Clip+ of course, but I would most certainly welcome the change for simplicity and predictability. It beats having to remember where one started playback in order to figure out the right way to return after creating a bookmark.
12.55.22 #       <chris_s> yeah,  there's probably a lot to be said for always returning to the main menu when playback is stopped from the WPS
12.55.38 #       <speachy> oh lovely, OVHCloud's order page is throwing out an error when it's time for payment.  *snort*
12.57.48 Quit    fourHZ (Quit: Client closed)
12.58.01 Join    fourHZ [0] (~fourHZ@92-52-40-121.dynamic.orange.sk)
12.58.25 #       <chris_s> :D
13.00.21 #       <speachy> two hours before we lose the pricing.
13.00.48 #       <speachy> site keeps glitching
13.03.45 #       <speachy> sigh.
13.07.00 Join    mink [0] (~mink@125.215.164.109.static.wline.lns.sme.cust.swisscom.ch)
13.07.12 Quit    mink (Remote host closed the connection)
13.07.23 #       <speachy> yeah it looks like one of the internal services is throwing a 403 error.
13.07.53 Join    mink [0] (~mink@125.215.164.109.static.wline.lns.sme.cust.swisscom.ch)
13.09.24 Quit    jacobk (Ping timeout: 255 seconds)
13.10.00 Quit    advcomp2019__ (Read error: Connection reset by peer)
13.10.23 Join    advcomp2019__ [0] (~advcomp20@user/advcomp2019)
13.13.44 Quit    CH23_M (Ping timeout: 256 seconds)
13.14.41 Join    CH23_M [0] (~CH23@revspace/participant/ch23)
13.32.45 Quit    bilgus_ph (Quit: Connection closed)
13.41.05 Quit    chris_s (Quit: Connection closed)
13.45.22 Quit    CH23_M (Read error: Connection reset by peer)
13.45.59 Join    CH23_M [0] (~CH23@revspace/participant/ch23)
13.49.14 Join    jacobk [0] (~quassel@utdpat241033.utdallas.edu)
13.52.28 ***     Saving seen data "./dancer.seen"
14.21.25 Join    chris_s [0] (~chris_s@ip-095-223-073-220.um35.pools.vodafone-ip.de)
14.46.04 Quit    mink (Remote host closed the connection)
15.12.05 Quit    jacobk (Ping timeout: 260 seconds)
15.25.55 Join    jacobk [0] (~quassel@utdpat241106.utdallas.edu)
15.30.18 Quit    Malinux (Ping timeout: 256 seconds)
15.33.24 Quit    jacobk (Ping timeout: 248 seconds)
15.52.29 ***     Saving seen data "./dancer.seen"
16.17.37 Join    Malinux [0] (~malin@2001:4641:4dfa::12c:c4a7)
16.28.55 Join    advcomp2019_ [0] (~advcomp20@user/advcomp2019)
16.32.30 Quit    advcomp2019__ (Ping timeout: 268 seconds)
17.04.31 Quit    advcomp2019_ (Read error: Connection reset by peer)
17.04.52 Join    advcomp2019_ [0] (~advcomp20@user/advcomp2019)
17.12.49 Join    jacobk [0] (~quassel@utdpat241106.utdallas.edu)
17.16.58 Quit    advcomp2019_ (Read error: Connection reset by peer)
17.29.02 Join    advcomp2019 [0] (~advcomp20@user/advcomp2019)
17.52.32 ***     Saving seen data "./dancer.seen"
17.59.32 #       <speachy> bluebrother: I was thinking; the way most folks seem to get rockbox installed is via rbutil.  What do you think about adding some sort of "please donate" button to it somewhere?  Seeing as we're goig to now have actual ongoing costs again.
18.24.24 Quit    jacobk (Ping timeout: 255 seconds)
19.15.57 Quit    fourHZ (Quit: Client closed)
19.36.51 Join    massiveH [0] (~massiveH@2600:4040:a993:4900:4ab:744e:1afd:5639)
19.52.36 ***     Saving seen data "./dancer.seen"
19.58.39 Quit    advcomp2019 (Read error: Connection reset by peer)
19.59.02 Join    advcomp2019 [0] (~advcomp20@user/advcomp2019)
20.19.21 #       <buZz> speachy: why the new costs?
20.20.09 #       <buZz> maybe i can wiggle up some funding viavia
20.25.48 Quit    chris_s (Quit: Connection closed)
20.52.58 Quit    massiveH (Quit: Leaving)
20.58.30 Join    massiveH [0] (~massiveH@2600:4040:a993:4900:b9f7:731b:2197:1e52)
21.52.37 ***     Saving seen data "./dancer.seen"
22.38.22 #       <_bilgus> buZz Fosshost
23.11.00 Quit    Malinux (Ping timeout: 256 seconds)
23.37.10 Quit    m01 (Quit: Konversation terminated.)
23.37.13 Join    Saratoga [0] (~Saratoga@2604:ca00:17c:31bb::c65:608)
23.38.02 #       <Saratoga> I think in the long term time becomes a bigger constraint than money so I'd say do whatever requires the least time commitment going forward
23.38.20 #       <Saratoga> Happy to chip in towards hosting as well
23.39.19 Join    m01 [0] (~quassel@vps-b172b88b.vps.ovh.net)
23.40.04 #       <rb-bluebot> Build Server message: 3New build round started. Revision 152a238947, 303 builds, 7 clients.
23.47.33 Join    advcomp2019_ [0] (~advcomp20@user/advcomp2019)
23.48.13 Quit    Saratoga (Ping timeout: 260 seconds)
23.48.29 #       <_bilgus> richard42 nevermind we already got the first stuff committed so carry on
23.51.42 Quit    advcomp2019 (Ping timeout: 265 seconds)
23.52.40 ***     Saving seen data "./dancer.seen"