Dusty the Fuzzy Dragon
dusty.chcl.se
Dusty the Fuzzy Dragon
@dusty.chcl.se
Mostly on masto - chcl.se

Twitter: @ChlorideCull
Bridged fedi profile: @ChlorideCull.masto.fuzzy.systems.ap.brid.gy (for me to see replies, you must also set up the bridge in the other direction)
and ordered! :)

Any idea when you'll reopen orders to EU? My freight forwarder isn't the cheapest, haha
February 16, 2025 at 7:06 PM
well, time to dig out my mail forwarder, I suppose
February 15, 2025 at 8:18 PM
Reposted by Dusty the Fuzzy Dragon
People need to understand that there can be joy in making music, even when you still haven't mastered all the skills. The process of learning stuff is actually worthwhile.
January 12, 2025 at 9:32 PM
You probably want to look at the shipping options, because something is definitely wrong here (shipping to sweden is $38 for the cheapest option, and $130 for priority mail, which is a lot for things that would go in an envelope)
December 4, 2024 at 7:36 PM
for me that ended up being the thermal paste having crumbled to dust from age
November 25, 2024 at 12:34 PM
I know it's been broken since at least kubo 0.22.0, so it shouldn't have been from something introduced after that - I might do a proper bisect in the future, I suppose :)
September 12, 2024 at 8:25 PM
The bad node was running 0.29.0 (version bundled with the latest IPFS Desktop), but I manually told it to use 0.30.0, which seems to have fixed it!

Quick gut feeling when it comes to what fixed it, it's probably github.com/libp2p/go-li...
config: fix AddrFactory for AutoNAT (#2868) · libp2p/go-libp2p@f80d18f
--------- Co-authored-by: Marco Munizaga <git@marcopolo.io>
github.com
September 12, 2024 at 12:17 PM
Yeah, that one has 4001 manually forwarded, and is set to manually announce my public IP. It's on the same network as the other one.
September 12, 2024 at 11:55 AM
One thing I notice is that despite the automatic forwarding succeeding and giving it a port of 36916, it doesn't seem to announce it, instead announcing port 4001.
September 11, 2024 at 1:51 PM
I don't feel like I have a super weird setup (currently opnSense with UPnP/NAT-PMP enabled) - the peer ID on the bad node is 12D3KooWAAH54haWUUnZQDQyuYxeY3dBeK8nKvMtQufxkFiAL143.

12D3KooWQuwz8pcL8Tm8kg2vqaFi2mARZYVYphsGyZSDesbg8iv3 is a good node that has had the announce "fixed" to the right IP.
September 11, 2024 at 1:42 PM
For bridgy, you need to set it up by following an account, since the bridging is opt-in :)

fed.brid.gy

But I'll come over here to continue the conversation instead :P
Bridgy Fed
fed.brid.gy
September 11, 2024 at 1:30 PM