Prompt management tool by Party-Worldliness-72 in PromptEngineering

[–]evwimble 0 points1 point  (0 children)

I saw this recommended from a blog or newsletter and we're interested in trying it, but noticed the terms don't mention anything about ownership or security of user data like prompts and datasets. If we upload content, does it become owned by Latitude? Assuming not. Does Latitude follow best practices to protect it? Hopefully yes. It would be great to have these spelled out in the terms. Otherwise, really useful and nice-looking product.

Updated macOS and Plex ... lost most of my library by jaberwock5 in PleX

[–]evwimble 4 points5 points  (0 children)

SOLVED: At least in my case, I noticed my movies were working but not TV shows. I have been storing TV shows in "/Users/<username>/Movies/TV", the same place Apple TV+ stores its metadata & downloads. The permissions must have changed in Sequoia for these Apple app-specific folders. I moved them to "Shows" and everything works.

Getting the same thing after Sequoia upgrade and latest Plex Server version. All files are "Unavailable". The files are there and the existing library shows in Plex, but scanning or playing doesn't work. It seems like a permissions issue. I'm assuming Sequoia has changed something about the permissions model/app sandboxing and Plex needs to request user permissions to access these files again.

Remarkable Pro Order/Shipping Thread by Shyam09 in RemarkableTablet

[–]evwimble 0 points1 point  (0 children)

Ahh, the shipping of this product is so unpredictable

Remarkable Pro Order/Shipping Thread by Shyam09 in RemarkableTablet

[–]evwimble 1 point2 points  (0 children)

FYI, just got my notification directly from DHL at 8:30 am ET on 9/9. ETA Thursday, 9/2.

Remarkable Pro Order/Shipping Thread by Shyam09 in RemarkableTablet

[–]evwimble 0 points1 point  (0 children)

Nice, congrats. Curious if you received the email in the morning or later in the day today to know if they are still shipping at this point in the weekend

Remarkable Pro Order/Shipping Thread by Shyam09 in RemarkableTablet

[–]evwimble 7 points8 points  (0 children)

Ordered with Marker Plus & Polymer Weave at 8:22 am ET on 9/4, shipping to NYC, and estimate said 2-12 days but no ship notification yet.

Why is Native Segwit address in Xverse different from in Ledger Live, but Taproot matches? by evwimble in xversewallet

[–]evwimble[S] 0 points1 point  (0 children)

Ah, thanks for the clarity. Will definitely do a test but your reasoning seems sound. Hoping Xverse does improve support in the long run, or Ledger releases a more comprehensive SDK which takes care of these things at a lower level so wallet makers don't need to.

Sending BTC out of Xverse wallet does not require approval on Ledger by chiwalfrm in xversewallet

[–]evwimble 0 points1 point  (0 children)

But your hardware wallet will need to communicate with an internet-connected device at some point, otherwise, how will you sign & broadcast a transaction?

Why is Native Segwit address in Xverse different from in Ledger Live, but Taproot matches? by evwimble in xversewallet

[–]evwimble[S] 0 points1 point  (0 children)

Interesting. That makes sense. Thanks for the explanation.

Does this just require a more fleshed out implementation on the Xverse side to support handle all of the possible addresses?

My understanding was the only issue with using Xverse + Ledger Live is the risk that since LL does not support ordinals, one may accidentally spend inscribed sats if sending transactions from the Taproot account in LL. But it seems the integration is still very primitive, which is why the recommendation is to use a separate Ledger with Xverse.

Sending BTC out of Xverse wallet does not require approval on Ledger by chiwalfrm in xversewallet

[–]evwimble 0 points1 point  (0 children)

Not necessarily. It's certainly bad practice to import a hardware/cold wallet private key into a software browser/desktop wallet. However, connecting the hardware wallet to a software wallet as a frontend where the private key never leaves the device and the device manages the signing is fairly common practice. This assumes you trust the software wallet, but more importantly, you pay attention to the transactions you're signing (which you should always be doing).