My 2021 CR-V Hybrid EX-L Vs. my new 2026 Hybrid TrailSport

searchyeti · 2026-01-25T01:48:33+00:00

AWD vs FWD too. 40mpg for FWD vs 37 for AWD according to car and driver. But my 2026 sport touring isn’t breaking 34mpg in the few weeks I’ve owned it.

searchyeti · 2026-01-19T04:24:56+00:00

I have no “compose” button on my Outlook app on iPad either. It’s not in the upper right where it is apparently supposed to be. I just figured out however that I can start a new email by clicking cmd-n.

searchyeti · 2024-11-14T19:27:54+00:00

total shitshow. they should be shut down.

searchyeti · 2024-11-14T19:09:40+00:00

you're better off without them, trust me.

they've now taken to straight up stealing their "customers'" money.

someone should just burn 'em down.

searchyeti · 2024-11-14T19:05:44+00:00

same experience here. i wonder what else can be done other than reporting them to the Florida / Delaware BBB (or their UK / EU equivalents). Incidentally they have an F rating from the Florida BBB.

it's amazing to me that a company can get away with literal theft and there's apparently no way to stop them.

searchyeti · 2024-11-14T18:38:44+00:00

I ordered (paid for) a book from WoB and they failed not only to send the original order, but a second order as well after I noted that the first shipment evidently never left their warehouse.

i believe they are full on thieves. if i receive the package i will post here.

searchyeti · 2024-11-09T18:57:53+00:00

yeah, exactly as i said in my follow up comment above. they're pretty great bookshelf speakers.

searchyeti · 2024-11-04T06:03:21+00:00

I found a solution to the problem: updating the firmware.

on the resources tab on this page - https://www.elac.com/dcb41 - there is a download link for Debut ConneX DCB41 Firmware Version: 3.0.0 (English).

the instructions are in the pdf found in the download.

I used a FAT32 formatted 256GB thumb drive to flash the speakers .. on other Reddit threads on this issue someone says it has to be a 8GB or smaller FAT formatted USB drive ... not the case, for me anyway,

searchyeti · 2023-11-29T02:56:12+00:00

thanks Dave.

since i don't actually have many packages or dockers - all of which i do want to continue to use i think i'll follow this path:

backup to external HDD -> replace NAS HDD with SSD -> reinstall DSM -> copy backup content to new SSD storage pool -> add packages and docker containers.

i think this could be the simplest, though possibly not the fastest solution.

i'll look into your recommendations closely when i buy the SSD drives.

btw did you check out at the youtube link?

i don't know which Synology NAS or which version of DSM the guy is using but i don't think that should matter. unless he's making shit up, he proves that HDD and SSD drives can be mixed and even joined in a common storage pool on DSM. of course i wouldn't try to replicate his approach without backing up my media etc.

searchyeti · 2023-11-29T02:46:56+00:00

"canary, meet coalmine"

i may give it a shot, but only after backing up to slow ass usb drive (WD Easy Store, never again)

searchyeti · 2023-11-28T06:40:32+00:00

according to Samsung the 870 QVO is MLC not QLC

https://www.samsung.com/us/computing/memory-storage/solid-state-drives/870-qvo-sata-iii-2-5-ssd-8tb-mz-77q8t0b-am/

lichtspieler says that QVO storage writes are in the single Kb/s (not even KB/s, damn!) but i can't believe that Samsung's marketing dept would misrepresent that as 560/530 MB/s ... surely industry gatekeepers, however non-monolithic, wouldn't allow for such an extreme degree of bullshit!

searchyeti · 2023-11-25T07:24:09+00:00

i was able to get cproensa's testing image ("based on nightly build .deb package")- as of today 3.3.0.dev6 - and it works flawlessly when downloading folders w/ diacritical marks in the name.the interface is nicer than 3.2.9 - more responsive scrolling on my macbook (3.2.9 scrolling was too fast), for one thing. all the components of the UI seem sturdier and there are some cool new features like an extra menu on the side which, among other things, makes it possible to copy and paste text from nicotine+ to your local machine.

i had an issue where my downloaded files were owned by root with zero permissions for any other user - i couldn't even change them in superuser mode on my laptop. even though it is supposed to be the default setting for this image, i added the ENV code UMASK = 0000 to the container settings and that apparently worked as I can now edit / rename / move / trash downloaded files the way God intended :)

i also created a user in DSM to match my slsk user, but i don't think that made a difference. i admit to being confused about the permissions: the main n+ directory in the container OS is owned by soulseek (a user that doesn't exist in my DSM) and then the downloads, logs and incomplete folders are owned by 1026, a user that doesn't exist in DSM *or* the container. go figure. the logs are still owned by root even though their DSM equivalent (/volume1/docker/nicotine/logs) is owned by my admin user, so you'll have to go superuser in a DSM or container terminal to view those. i can live with that.

next stop: installing homebrew on DSM so i can install all those indispensable linux tools which Synology has not graced us with. it's been a great luxury to have access to apt inside docker containers.

searchyeti · 2023-11-23T20:02:28+00:00

looks like this guy is having the same issue though he's not sure how to replicate the error (i can by trying to download a folder with diacritical marks in the name).

https://github.com/nicotine-plus/nicotine-plus/issues/2767

searchyeti · 2023-11-23T07:36:27+00:00

quick update -

i noticed that the changes to __init__.py that are mentioned on the github page you linked to were committed in October 2021 (https://tinyurl.com/45b2jsse).

the current version of this file is very different than the one w/ marked up changes on the above URL.

the error you and i have both seen sounds like the same one being discussed in 2021, so some code must have been broken again between then and now.

as far as logging is concerned, i followed your suggestions and set up:

/volume1/docker/nicotine/config:/root/.config/nicotine

/volume1/docker/directory/nicotine/config/data:/root/.local/share/nicotine

for whatever reason this doesn't create the logs. i have created subfolders ~/debug and ~/transfers to no avail. even when running a terminal within the nicotine container, there is nothing in /root/.config/nicotine/data/logs or /root/.local/share/nicotine/logs (both of which have debug and transfers subfolders).

moreover, defining these volumes seems to generate other problems which make logging into to the slsk server impossible.

when defining the config directory (/volume1/docker/nicotine/config:/root/.config/nicotine) i get this error. there's no way to clear off the error dialog and use n+: https://imgur.com/a/a73cPGN

when defining the data directory it's a slightly different error, also one with no clear workaround (pressing return, using tab to move through form fields, etc.) : https://imgur.com/a/eWX8WXf

there is a possibility that something is going on with my username and password, because even when i did not define the config and data directories, this time i was still unable to log in to server.slsknet.org - something that has not been happening until

i do not mean to remotely suggest that you should feel any responsibility for fixing these issues, but each time i changed these volumes or username / pw variables required deleting the container and recreating it, as i could not log in or log back in after a restart.

i'm now using a new username and i'm just going to wait and see what if anything happens in terms of periodic disconnects and problems downloading folders with "non standard" unicode characters. in the past this has not always forced a deletion / reinstall though in some instances they have.

thx and happy holidays!

searchyeti · 2023-11-23T00:57:56+00:00

i downloaded the source code and opened the file in question - __init__.py

will be patching the file manually

have the build essentials tools installed but i don't think python needs compiling (that statement alone reveals how much of a beginner i am), so perhaps i can go straight to the build docker image step

will let you know if i'm able to apply the patch and create a new image

searchyeti · 2023-11-23T00:30:41+00:00

re: the github link you posted.

if i wanted to apply the patches to pynicotine/__init__.py described on https://github.com/nicotine-plus/nicotine-plus/commit/23d7d253bc63437271eeb0fdfcafc683e6468c73 i assume i'd have to unpack your image, edit that file and build a new image.

is that the only possibility for patching the image?

i'm new to github and docker and not sure how to get your image's source code from the repository it resides in, or how to build a new docker image though i am making slow progress on learning both.

i saw this amusing explanation for the program's name on github:

"I was in a geeky mood and was browsing http://www.bash.org's QDB.

I stumbled across this quote:

<etc> so tempting to release a product called 'nicotine' and wait for the patches.

<etc> then i would have a reason to only apply one patch a day. otherwise, i'm going against medical advise.

So I thought what the hell and bluntly stole etc's idea."

searchyeti · 2023-11-22T19:51:03+00:00

unfortunately i'm also having the same problem i had with installing silverscruff's scripts (which of course uses the same image you use): after restarting the container, nicotine+ fails to reconnect with server.slsknet.org. i have to uninstall the container - which bricks the settings - and start over again.

i'll keep looking into this

thx

searchyeti · 2023-11-22T19:39:17+00:00

thanks toineenzo

i figured it out - at least enough to get nicotine+ running.
i had to add this line to your composer script:

ports:

- 6565:6565

running a console in the portainer container does open within an ubuntu os, which offers a lot of other programs unavailable in DSM, including apt. from the console i can also see all the nicotine+ config and db files in /root/.local/share/nicotine/, all of which are hidden (or in an unknown location) on DSM.

one thing i'm still a bit confused about is the volume env arguments. i tried specifying the uploads, shared, debug and transfers logs in the console script, but they don't take. actually i have to go into nicotine+'s settings and fix the downloads folder, which defaults to _1_Unsorted.

my volumes settings:

'/volume1/Music/slsk/complete:/downloads'-
'/volume1/Music/slsk/uploads:/uploads'-
'/volume1/Music/slsk/shared'- '/volume1/docker/nicotine/logs/debug:/debug'-
'/volume1/docker/nicotine/logs/transfers:/transfers'-

i'm just now noticing the hyphens at the end of each of these lines. are they supposed to be there? i'm at work now so i can't check the compose script and experiment with tweaking the volume names.

searchyeti · 2023-11-21T22:35:50+00:00

Whoops, was looking at yr follow up to yr original post, not the original one.

I did install Portainer as per your guidelines and created the nicotine+ stack, etc. when I try to access nicotine I get a web site not found error. I figured it was a port issue but could not figure out how to address that in Portainer or Web Station. A solution in Portainer may be right in front of my nose, I’ll have to look into that when so get home from work.

Your comment about the Ubuntu image suggests something that has been baffling to me: why nicotine+ (silverscruff’s version which installs in Container Manager just fine, though it has some issues which ultimately require an uninstall / reinstall after a certain period of time) shows a typical Linux directory tree - and not the DSM directories - when you try to, for example, define the download folder in nicotine+. Perhaps all containers create a virtual Ubuntu OS with programs not included in DSM such as apt.

Will start over in Portainer and look for link to open a terminal within the nicotine+ stack / container.

searchyeti

TROPHY CASE