We're hangin' tonight in OC, come join us:
nostr:npub12z5nym0qkxhdrvmyhup2llzp98lryr38gw8ywxktkps9eqdts7asjj9k9c Oooh, Strike actually does let me send my btc balance over LN now.
strfry-policies has a nice hellthread filter that will block events over a threshold of p tags. Defaults to 100. I set it to a single digit number on a free relay
Vendor your own assets
I should fix our snort so it doesn't use a Google font
Tweetdeck is gone.
Started reading the strfry-policies code before I implement it on the free relay. And I'm just learning Typescript after not using JS since, uh, before ES5 was a thing? Anyway, I'm learning by trying to read it and then asking copilot "What the hell is that" (`/explain`) when I don't understand some syntax.
TIL about destructuring assignment shorthand:
```Typescript
.. async (msg, opts = {}) => {
const {
interval = 60000,
max = 10,
whitelist = [],
databaseUrl = 'sqlite:///tmp/strfry-rate-limit-policy.sqlite3',
} = opts;
```
Coming from Python that just looks weird.
But yeah, it's shorthand syntax for extracting properties from an object and assigning them to variables with the same name as the properties.
```Typescript
const person = { name: 'Satoshi', age: 99 };
const { name, age } = person;
console.log(name); // 'Satoshi'
console.log(age); // 99
```
Thank you nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6
Syntax test
```Typescript
const person = { name: 'Satoshi', age: 99 };
```
Take a screenshot to find your spirit animal 👇😇 https://nostr.build/av/26ceb3b30d780648f8b63892584e1f54de7f95eddacc883b0bb90b255147e538.mov
I got the bull
you're definitely no dummy and basically the relay has a super fast database now. same one I've been running on the other free relays since beginning of this year
So I can build more cool features on this relay too
And the other peice was to update my strfry plugin to accept events only from registered users. Quick and dirty for now. Next step will be to build a registration process for new users
https://github.com/bleetube/strfry-plugin/blob/main/src/bitcoinersocial.py
Migrated the nostream db:
```
# cat /tmp/events.jsonl | doas -u strfry strfry import
# date && cat /tmp/events.jsonl | doas -u strfry strfry import && date
Wed Aug 9 06:18:59 PM UTC 2023
date time ( uptime ) [ thread name/id ] v|
2023-08-09 18:18:59.146 ( 0.034s) [main thread ]INFO| arguments: strfry import
2023-08-09 18:18:59.146 ( 0.034s) [main thread ]INFO| Current dir: /var/lib/strfry
2023-08-09 18:18:59.146 ( 0.034s) [main thread ]INFO| stderr verbosity: 0
2023-08-09 18:18:59.146 ( 0.034s) [main thread ]INFO| -----------------------------------
2023-08-09 18:18:59.146 ( 0.034s) [main thread ]INFO| CONFIG: Loading config from file: ./strfry.conf
2023-08-09 18:18:59.157 ( 0.045s) [main thread ]INFO| CONFIG: successfully installed
...
2023-08-09 18:23:32.110 ( 272.999s) [main thread ]INFO| Committing 10000 records
2023-08-09 18:23:36.526 ( 277.415s) [main thread ]INFO| Processed 756689 lines. 659998 added, 96691 rejected, 0 dups
```
Interesting to see strfry is a little more picky about what it accepts.
I also came up with a direct export straight from psql:
```
\COPY (
SELECT row_to_json(t)::text
FROM (
SELECT
event_content as content,
event_created_at as created_at,
encode(event_id, 'hex') as id,
event_kind as kind,
encode(event_pubkey, 'hex') as pubkey,
encode(event_signature, 'hex') as sig,
event_tags as tags
FROM events
WHERE deleted_at is null
) t
) TO '/tmp/events.jsonl';
```
Uhhhh yo bitcoiner.social is running on strfry now
I just want to say I love how the problem statement here is expressed with an animal meme
You're right, and that's probably a fine arrangement for some people.
Deterministic wallets have a multiple account hieararchy. You can create an account (using a 13th word, for example) that is solely for this custodian. I don't need to reveal any information to them that they won't eventually know at some point.
I have no expectation of privacy between myself and a KYC broker. Which means the only trade-off worthy of this arrangement is extreme convenience. If it is not absolute convenience, then I'd rather just do this myself without KYC.
I guess I am just discovering that having to ask Swan to set up or fix my Bitcoin stacking is unacceptably inconvenient. And I'm starting to realize the advantage of KYC brikers is simply not worth the cost.
In 2023, my only alternative is to either be paid directly in Bitcoin (my employer doesn't do this) or politely ask my KYC bank to let me transfer funds to some other KYC service like Swan for auto-debit DCA. The usual pull-based system everyone seems to be using that has their bank permitting the exchange every time it takes place.
Seems like all the wiser folks have already gone KYC-free.
I checked and looks like River only has single-sig automated withdrawals currently. I reached out to their support to ask if they were planning to implement xpub support.
Swan does but it's entirely manual set up for that use case. That's why I'm looking for options.
Strike was really promising as a lightning first company. I even pre-emptively set up direct deposit when they had it. But they never implemented lightning withdrawals from a btc balance.
In the end, if I'm going to do anything manually I may as well be using Bisq.
Is it actually an xpub though or are they just having you paste in an array of addresses? Better than single-sig I suppose but seems tedious and error prone.
What are the alternatives out there for turning a direct deposit into xpub UTXOs?