Avatar
Dr. Hax
d30ea98ea65e953f91ab93f6b30ea51eb33c506f87d49f600a139aef00aa9511
Cypherpunk. Infosec veteran of about 15 years (vulnerability research, exploit development and cryptography). Cypherpunks write code. :-) Signet maintainer. Self-custody your passwords... in hardware! https://hax0rbana.org/signet Want to see wider adoption so Bitcoin can be used as digital cash and not just an investment vehicle. XMR: 44RDkTFmTeSetwAprJXnfpRBNEJWKvA5dBH5ZVXA4DofgoZ9AgjyZdSa2fo7pMD3Qe3pdKga8X22y3Lyn1xYde5kPQPzVUu

The enamaled wire appreads to be glued in place. I guess if it's all being ripped out anyway, that won't stop anyone though.

I was hoping it would be an open circuit that I could just patch, but no such luck. I have hand spun coils before and I'd have to be pretty desperate to want to go through that hassle. Even in the most dire of times, I might just used a crank drill before going to that trouble.

Tried to repair a Craftsman drill that was made in the 1960s. The problem is that one of the inner coils is shorted out. They don't make parts for it anymore, so it's not really repairable.

Apparently I could replace it for $40.

https://www.ebay.com/itm/266976958735

But then I'd have another drill (I don't need another drill) and this one would still be broken.

However it could be spare parts for someone who has the same model but a different broken part. Model 315.10491 If you have an inner core lying around, hit me up and I'll try to bring this puppy back to life!

#tools #repair #DIY

There's a lot of truth here. I've struggled to get people who were curious set up with an on-chain wallet. I lost one person because they didn't want to put a PIN on their phone. Another didn't like all the screens explaining what everything was before they could use the app.

Regardless of what some people think of these are barriers, they are very real, and they DO limit adoption. Lightning is 10x more complicated.

So it does need to be easier, and they only thing that is really easy to use is a custodial solution (but those are vanishing rapidly due to KYC rules).

Even putting micropayments aside for a moment, nostr is absurdly complex as compared to what it was a year ago. It used to be you just opened a client and started posting. If you wanted to change the default list of relays, you could. Now clients want every user to manage half a dozen lists of relays and understand what each list means.

As for bitcoin content being in the way of adoption, I don't agree with that. I'd agree that if it is all memes about bitcoin, not many people will be interested who aren't already here.

I'm not sure what the way forward is. Some things that would help include:

- Easier discovery of content

- Being able to filter out posts in languages you can't read would be a nice start

- Clients being immediately usable. None of this high time preference requirement to learn details about the protocol, or having to configure a bunch of stuff

- Following hashtags is big, as is using them if you want to be seen. Clients could help with this by adding suggestions or reminders

- Relay operators can help fight spam

- Tools to deal with abuse should be better. The web of trust model could help here. There's a delegate balance between blocking spam/crap and being able to discover new content.

- Micropayments are not the only thing that distinguishes nostr from other protocols like Bluesky or ActivityPub, but I think it's an important one. Zeus is reasonably easy to use when using Olympus (their LSP). The integration between nostr clients and wallets is reasonable. I wouldn't call it "good", "great" or "fantastic".

I think the common theme here is easier to pick up and use without reading the manual.

The more difficult question is how do we get there? Traditional tech companies have VC money to pay for development, operations, and lawyers. When that runs out, they have money from selling everyone's information to the highest bidder (data brokers, advertising networks, corporations, etc.).

How do nostr developers pay for food, rent, utility bills, healthcare and the like. Donations from the users? Ha! And the idea that donations matching the salary they could earn by getting a "normal tech job" is even harder to imagine. So far it seems like the answer is to work for free and hope to win the lottery of OpenSats or similar. If they're rich and don't need a job, I guess that's cool as long as they never get bored of nostr.

How do relay operators do the same plus cover costs of operation? There may be some clever solutions here, such as users contributing things like bandwidth in addition to money. Something similar to bittorrent, perhaps.

Maybe clients could set up a default of splitting donations between developers and relay operators. Relay operators could then split income between infrastructure costs, developers, and moderators who fight spam. The incentives need to be there.

Today's experiment: 6 new hydroponic plants (hopefully). I planted some seeds and we'll see what sprouts.

Celery, cilantro, and thyme.

That last one was poorly thought out since two thyme plants aren't going to be enough to do much of anything (if they even germinate), however it'll be an experiment and I don't have to repeat it.

"I have been shepherding a Matrix Spec Change that tries to choose easy-to-understand wording to explain Cryptographic concepts to non-technical users.

I think the first draft is ready! Comments and suggestions welcome."

https://github.com/matrix-org/matrix-spec-proposals/pull/4161

#matrix

Via: https://mastodon.social/@andybalaam/113090382618638276

It is, but it should be uncontraversial and a good feature to have in its own right, well beyond just the problem of the day.

Remember, no matter what featers #nostr clients include, every single user will have to duplicate the effort to block spammers.

If you suggest this is inferior to allowing people to share filters, or having relays help address the problem, you'll be told to GFY, accused of censorship and being an authoritarian.

You may not like it, but this is the nostr way.

Replying to Avatar Amethyst

#Amethyst v0.91.0: Edge to edge feeds

Hidden words now filter by the user's fields as well. You can hide by name, profile picture, banner, lightning and nip-05 addresses and about me fields.

Features:

- Finishes Edge to Edge transition for Android 15

- Adds compression settings to the media uploading screen by nostr:nprofile1qqsv4zwtz8cuwh2mvc3zdrl5853g365t9j6mn25edlul7uz0eyzt0zcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsshgmkj

- Adds sliding animations in all inner screens

- Adds copy stack to clipboard for error messages that have an exception

- Enables the use of hidden words for all visible properties of the user

Bug Fixes

- Fixes blank alt field when no alt text is provided on NIP-96

- Fixes missing Private Home/Outbox relay list after loading from backup

- Fixes keyboard padding issues when using physical keyboards on the message screens.

- Fixes token sanitization when using gcompatup with unified push by nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck

- Fixes moving top buttons on the full screen dialog for images and videos.

- Fixes weird padding of the key backup screen

- Fixes using npub instead of pubkey in hex when communicating with Amber

- Fixes blinking on crossfades when the system's light/dark theme is different than the app's theme

- Fixes a mix of languages after changing language in Settings

- Fixes disables saving m3u8 files locally (streaming can't be saved)

- Fixes Community tab not loading up with Global filter

- Fixes size of default banner when the profile is not loaded yet.

Code Quality Improvements:

- Inverts Layouts to place Navigation on top of Scaffold and allow custom scaffolds per route

- Refactors navigation to improve clarity

- Restructures screens into their own packages

- Restructures navigation functions as a single object

- Refactors all TopBars to use default material 3 ones

- Simplifies the "and 2 more" translations for the relay recommendation user lists

- Removes unnecessary observers from the transition in the bottom nav layouts.

- Normalizes cache directories in the Application class

- Fixes text field recompositions because of new keyboard actions

- Moves the profile zap to threads

- Updates to AGP 8.6.0

- Updates zoomable and kotlin serialization

Updated translations:

- Czech, German, Swedish and Portuguese by nostr:nprofile1qqsv4zwtz8cuwh2mvc3zdrl5853g365t9j6mn25edlul7uz0eyzt0zcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsshgmkj

- Thai by nostr:nprofile1qqsxdhmq2cke8xk6scfyxeyfj3dyancavg6xk0v50r023gec7vsrceqpzemhxue69uhkvun9deejumn0wd68yvfwvdhk6qg6waehxw309aex2mrp0yezumn0wd68yctnd9sjumn9wsq3yamnwvaz7tm0venxx6rpd9hzuur4vghen3hm

- Dutch by nostr:nprofile1qqs82l74z7g3x8j3avpn2wrjrwn855nyvmpxa4v5pftfvtv5lrvrc5cpz9mhxue69uhkummnw3ezuamfdejj7tk0drp

- Hungarian by nostr:nprofile1qqs88rmfrp9wmfn4qq4kslly0j8futmmrgn86mu3gkc3jvcjl97p3mcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz8nhwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgtcqngjsj

- Bengali by nostr:nprofile1qqsgs9hgjw87vz36jf2r83m5zree2q87zvs8s7kty9jljdz7wprytyspzpmhxue69uhkummnw3ezumt0d5hstgqjd9

- Polish by nostr:nprofile1qqsdyfz0ewdhmgp3a4r3pxvezx5r8yalrgvjn38v2ml5qrusnv7yywg25ynng

- Hungarian by nostr:nprofile1qqs88rmfrp9wmfn4qq4kslly0j8futmmrgn86mu3gkc3jvcjl97p3mcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz8nhwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgtcqngjsj

- Chinese by nostr:nprofile1qqsyxnuhnymz0u0xru2watmqe25vlh8vzzje9jhlsfgvsff9942gc9gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxthwden5te0wfjkccte9ekk7mt0wd68ytnsd9hxktcpzfmhxue69uhkymmnw3ezucmc9ekhxtc24vk7q

Download via [Obtainium](http://amethyst.social) or [Zap.Store](https://zap.store/)

I guess the point is to call out a couple relays that don't deal with spam and try to get them to censor this guy's speech?

OMG, the Hungarian peppers I have ARE the same genius, species and variatal as is sometimes used to make paprika!

I don't know what the heck they're doing differently than me, but when I dry them and grind them into a powder, it makes spicy pepper powder, not anything like paprika.

Maybe if I took the seeds out and wasn't using the "benign neglect" strategy of watering them?

If I ever get enough of my normal pepper powder, maybe I'll try making paprika. By removing the seeds that is, because remembering to water them the perfect amount every day for months on end is going to take automation.

I like this. Screw the outbox model, the broadcast model, and relay. Go straight to p2p!

People are working on 3d printing pharmaceuticals. Wow

https://infosec.exchange/@tinker/113087807778793836

I misunderstood the documentation here. I also think it may have been different in the past because I see other people on the forum making the same "devices can sniff passwords" claim that I was. E.g. in https://forum.qubes-os.org/t/understanding-security-implications-of-usb-keyboard-usage-key-logging/2817

Anyway, I wanted to explain why I now believe this claim is incorrect, and why I still believe my USB to PS/2 adapter is useful in terms of security.

According to this, traffic from devices is only sent to the controller. https://web.archive.org/web/20190708035849/https://www.totalphase.com/support/articles/200349256

They mention that the host has the choice to either send each packet to a specific device or broadcast it.

The security benefit my device will provide is not connecting the keyboard to any VM, which means we can limit the control a compromised USB Qube would have on your system. The Qubes documentation is pretty unambiguous here:

"If you connect USB input devices (keyboard and mouse) to a VM, that VM will effectively have control over your system."

https://www.qubes-os.org/doc/device-handling-security/#security-warning-on-usb-input-devices

By avoiding using a USB keyboard or mouse, the UAB qube can be fully untrusted.

nostr:nevent1qqs2yz6h2375n0h7rsvdmgu9r3kwfamyct0du8mykpqmg5xr0gx6glcpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdxr4f36n9a9fljx4e8a4np6j3aveu2phc04ylvq9p8xh0qz4f2ygrqsqqqqqpekze9y

Fixed the flat on the hand truck today.

Broke the main paper shredder.

(unrelated incidents)

I guess the constant stream of repairs gives me something to post about so we can #GrowNostr 😅

I was asking about receiving, not realizing it was any different than transmitting. I thought a poorly tuned antenna would give a poor SNR for receiving and not transmit as well when transmitting (though I don't know the metric for that).

When I said an FM antenna being a wire, I was thinking of a home stereo and an antenna like this:

?v=1552667011

With those clarifications out of the way, the example was very helpful. I can't say I understand all the theory, but maybe I can take a crack at explaining what I think to be the case and we can iterate?

The waves come in and hit the antenna, inducing a current. In the middle section, it's blocked, but it gets in above and that's the resonant frequency, so the signal will be nice and strong. Below the double shield, the cable is still shielded, so it gets minimal interference on that segment.

I know my terminology is probably wrong here, but is that the gist of it?