The question I have is: should I spend time tearing the leaves off the oregano stems so they dry faster, or wait them dry and then peel the leaves off?
#m=image%2Fjpeg&dim=1920x1440&alt=Greek+oregano+sits+on+a+colorful+dinner+plate.+Half+of+the+plate+is+covered+in+leaves+while+the+other+half+has+sprigs.&blurhash=%239Csv%3AIr4b4oIRaIR2NGeS8w%24xNP%25gNhxuRko2Wq0uIc%5EWR%23-QRjx%5Enio%7CQlxVT2x%5BNLaiV%3DNHs%2Bx.InQ%2Cw%5Btlo%24k%40%25MIY%25FxuEVN0r%3AM%7Bx9W9xuRYs%2B%24%5ERpJE%25KIWRns6&x=cf8650abd83e7b5330543148890b545e793d35cd2c7e813bba67585f56d362ae
In other cases I've found I want to process them before drying (scallions, chives, etc.) because they dry faster and retain their color, as opposed to browning. This flies in the face of what most of the internet says is the "right way" to dry spices (they say to hang them out to dry).
#food #foodstr #herbs #spices #prepper #prepping #homestead #homesteading #GrowNostr #garden #gardening
Ava is going H.A.M. 🤜🤛
Feburary means freezing at night and not freezing during the day. Time to tap the maple tree!
#m=image%2Fjpeg&dim=1440x1920&alt=A+large+pot+hangs+froma+tap+that+was+installed+into+a+maple+tree.&blurhash=_7EM2o00%5Ej9FWA%25N%25M.S%3FI4njEogafozISoJt9xaRjt8M%7BMINH-%3DNHazofV%3FR%2B%25MITt7s%3AM%7Bt7.AIUslf5ayt7WDM%7Bt7M%7BxuIUt7ogr%3BRjxvRjjGWBt7oIa%7Dj%5DWBW%3DjZWA&x=617f80d84fe59f81d2e0bb1a1da6743ef51d03125be246fba9e172059a74a794
#homesteading #homestead #prepper #selfreliance #GrowNostr #gardening #food #foodstr
When I can't say it better myself, I just point to those who can: Why we love free software, by Saccha Chua.
#m=image%2Fjpeg&dim=1247x1663&alt=A+comic+about+%22Why+I+love+free+software%22+by+Sacha+Chua%3A+Free+software+is+like+having+more+gifts+that+I+can+even+imagine+%28with+image+of+person+reaching+for+presents%29.+Each+first+is+a+building+block+that+I+can+have+fun+with+%28image+of+blocks%29.+More+than+that+--+each+block+is+a+glimpse+into+someone+else%27e+life+%28image+of+same+blocks+with+talking+people+inside%29.+I+can+combine+things+with+bubblegum+and+string+to+make+something+that+fits+me+so+well+%28image+of+blocks+combined+with+gun%3B+then+image+of+glove%29.+%5B...%5D+at+the+end+it+says%2C+%22So%2C+bit+by+bit%2C+we+grow.+Free+software.%22&blurhash=_9RfkBD%25t7%25M%7Eq-%3B_3M%7BIUIUt7xuxuxuM%7Bt7WBt7j%5BWBt7-%3Bxuj%5BRjRjWBM%7B%25M%25MofWBIUM%7BIUxuxut7M%7BM%7BRjRj-%3Bxuj%5BayRjRjRjM%7Bt7t7ofWBayt7WBofWBayayofof&x=56a5e0ffce3d1a6c5849f2c1617faf745aa1fddafdd4fbd9a4d90a1eda347b6f
dmesg in qube show: unlink->seqnum and urb->status -104
In journalctl in sys-usb: unlinked by a call to usb_unlink_urb()
I see selinux is enabled in sys-usb, which adds another possible layer that might be messing around with things...
How the USB proxy works in Qubes https://github.com/QubesOS/qubes-app-linux-usb-proxy
I also found that while the docs point me to /etc/qubes-rpc/policy, the configs have moved to /etc/qubes/policy.d, which was incredibly confusing because there ARE still config files in the documented location. It's just that the main stash moved and it's pulling in the configs from the documented (deprecated) location.
I have not yet found anything that looks like it would be filtering specific traffic to the device, so I'm not sure where the issue lies with not being able to communicate with my hidraw device
Looks like it could be something the kernel is doing, either in sys-usb, or the qube that the device is being attached to.
I saw issue 3628 that was kernel bugs/incompatibilities related to USBIP.
That issue isn't what I'm facing, but I am seeing some weird stuff in the syslogs...
Thanks for your suggestion.
Oh, I found some additional notes after clicking all the different kinds in my query. I still didn't find the ones I was looking for.
The software that I'm investigating must be using multiple accounts so there is better privacy. Clever.
How the USB proxy works in Qubes https://github.com/QubesOS/qubes-app-linux-usb-proxy
I also found that while the docs point me to /etc/qubes-rpc/policy, the configs have moved to /etc/qubes/policy.d, which was incredibly confusing because there ARE still config files in the documented location. It's just that the main stash moved and it's pulling in the configs from the documented (deprecated) location.
I have not yet found anything that looks like it would be filtering specific traffic to the device, so I'm not sure where the issue lies with not being able to communicate with my hidraw device
This is great! I wasn't able to find the posts I was looking for, but I did find one post from the account in question, so I think the tool is working just fine and something works differently than I expected.
There are 3 types of login: a nsec, an extension and a seed phrase. We offer all three, but from a security perspective, I want to have confidence and I want users to have confidence that all are secure.
nostr:npub16v82nr4xt62nlydtj0mtxr49r6enc5r0sl2f7cq2zwdw7q92j5gs8meqha would like your perspective on how we can improve both security and confidence🤔
I haven't surveyed what's out there (beyond what I saw on nostr.cooking) but the first thing that comes to mind is the website issues a challenge (e.g. a 32-byte long random number) and the user has to post that to a relay. If they can do so, the website knows the user controls the keys and can authenticate that session.
This challenge would need to include the site you are logging into, otherwise I could pass along a challenge for nostr.cooking and tell the user this challenge is for my site (which it would be, but then I could tell nostr.cooking that I signed the thing so I should be authenticated).
With the FQDN in there, when I hand a challenge to a user that says the FQDN is nostr.cooking, they should know I'm trying to scam them and refuse to post.
The upshot is that the user only provides their npub, the URL for a relay they're going post to, and the post.
This is basically how FIDO2 works, so if you think this sounds like a good system, give them the credit. I just read the spec, wrote some little implementations of it, and can vouch that it seems solid.
That's my issue. I have a user ID and I kniw things have been posted, but the feed shows up as empty everywhere I look because the feeds are only showing kind 1 notes.
I can solve this with some python code and a computer, but if I can do it from my phone it's much more likely to get done sooner.
I do. I thought all posts were posts and some were notes and some were other stuff
Is there a site like njump.to that can display posts that are not "notes"? I want to explore.
You see, what we learned in school can be relevent in real life! It just took a quarter century to come across the right reference manual. 😂
Shout out to nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z for improving the error messages when zaps don't work right. Looking forward to the release that has this one so we can work toward getting the issues resolved.
https://github.com/vitorpamplona/amethyst/issues/127#issuecomment-1924885676
#Tor #Privacy #Bitcoin #Zaps
And there is a sequal they are crowdfunding called "Disappear"
https://www.kickstarter.com/projects/1587081065/disappear-the-documentary
Oh! I forgot to mention the point of this 9.5 hour debugging session! The device never gets the startup message from the client. This implies:
Qubes 4.2 filters writes to rawhid devices
Qubes 4.1 and earlier did not do this
I have more research to do in order to track down exactly how Qubes is accomplishing this. It doesn't look like it is usbguard (which seems to be running in dom0).
I don't see anything in the release notes about this.
https://www.qubes-os.org/doc/releases/4.2/release-notes/
Next stop: how does qubes accomplish making devices available from one qube to another? 🚂