[gui error report] Error: Initializing daemon... about ipfs-desktop HOT 5 CLOSED

Thanks for submitting this issue @Brent-Sanchez, did you start ipfs-desktop after a long time? for some reason your config has a weird deprecated key in it.

Can you please attach your configs that can be found here? Then in the config file can you try renaming the key Experimental.AcceleratedDHTClient to Routing.AcceleratedDHTClient?

from ipfs-desktop.

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

from ipfs-desktop.

I have ipfs up and running, but for that super old key to make any sense, I'd have to find some super old post in (i think the ipfs companion github, n00b section ) . Microsoft has really gotten carried away with thier "storre integrations", and they were trying to grenade my machine over and over again. However, I have a sharepoint and stuff, azure functions etc etc, I need that stuff to work. In their AI haste to increase their look and push free thinking dissenters down towards the gutter I don't think they took in consideration their tactics could be used in reverse. Anyway, if you don't mind, i have here a key pulled asside from an old .js manifest, can you let me know if this is the key that needs to go? Also, for users going forward, the main obstacles were really from microsoft security and nordvpn / nodrlocker rising from the dead in the background and blocking comms. I had to go through the (winDOHz 19045) system's user profiles and get all the security settings into a sort of interlocking configuration, because my original ipfs node was in a grenaded account, as well as the 2nd ipfs node lol. And those accounts were important for other things as well that are connection specific.

I can elaberate on this scheme, but we'll have put a time limit on my messages. :-D It's so elaborate for somebody that just barely limps along with this stuff. One thing I found out after years of being discriminated against by microosft (probably unknowingly on their part) is that they have been misidentifying my machine by confusing it with my old machine, and it's like dealing with a bipolar update client. They eventually downgraded my OS to a tablet, personal windows edition, and this took literally years to figure out. Apparently, where a friend I sold my old laptop too (whiped, new hard drive) never signed in with a windohs account, it must of caused this phenomenon. So far I've had to back engineer al the connection upgrades that WERE in windohs proffessional, the old Oauth, the new Oath2, including the encryption checks in outlook, the way update works, and I made an external device that handles 4 way handshakes, and bypassing for giggles around my cloudflare zerotrust setup in a way that doesn't get their panties in a wasd. I had to fool windohs hello (face) after mistakenly signing up for that integration, but luckily it wa through nordlocker and brave browser. Giggles also dropped their key off onto the wrong device, my dev device, but thiat's where I turned this little wagon around.

There seems to be some panic in this modern work from home/ "2FA" "MFA" environment about how exactly to secure things, but I have a solution lol. I was also reading into the problem with relays and NATs, and I see why this has been such an uphill battle. I originally callled this system all together the pivot.relay but now I call it Color out of Space. It just needs to be tuned to always happen in time when interacting with 3rd party/external connections and it' would be worth publishing as a public protocol. I can post that stuff, but I'm still not sure I isolated the right key.

from ipfs-desktop.

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

from ipfs-desktop.

This issue was closed because it is missing author input.

from ipfs-desktop.