Uhhhh yo bitcoiner.social is running on strfry now
Discussion
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';
```
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
