YeOldeHodler [OLD ACCOUNT SEE PROFILE FOR NEW NPUB]

https://github.com/BrightonBTC/bija/releases

#Bitcoin freak
Anarchist without adjectives. Freedom maximalist.

Building @Bija Nostr Client

Slowly ending activity on this account and moving over to npub1qqqqqqqut3z3jeuxu70c85slaqq4f87unr3vymukmnhsdzjahntsfmctgs, hope to see you there!

Public Key

npub1m680jypkcrtet94ktlhnqnxht8224w7ccefm9yrhcrwvkvhya8hs6tp28g

NIP-05 Address

YeOldeHodler@rebelweb.co.uk

Profile Code

nprofile1qqsdarhezqmvp4u4j6m9lmesfnt4n492h0vvv5ajjpmuphxtxtjwnmcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsy7mc5f

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1m680jypkcrtet94ktlhnqnxht8224w7ccefm9yrhcrwvkvhya8hs6tp28g

Show more details

Last Notes

2023-01-01 10:15:48 UTC

New Year, new profile. I'll be slowly transitioning over to #[1]

2023-01-01 08:21:03 UTC

Happy New Year!
2023, Year of the #Nostrich

2023-01-01 08:18:04 UTC

- reply

FYI your nip05 address isn't validating
https://www.randymcmillan.net/.well-known/nostr.json?name=randymcmillan returns a 404

2022-12-31 15:40:11 UTC

- reply

#[1]

2022-12-31 08:24:25 UTC

gm nostr!
Been out of action this last day or so due to illness. Still feeling a bit rough TBH.
Got loads of updates, improvements, and new features coming to #[1] soon, including proof of work configuration, lightning invoice display, and a load of bug fixes, but I guess that'll be in the first few days of the new year now.
Wishing all you crazy freedom lovers a fantastic new year! We got this, 2023 is ours!

2022-12-29 23:35:37 UTC

- reply

Think I've got everything back now :)

2022-12-29 22:50:19 UTC

Oh! I'm suddenly not following anyone!?
Think I saw others posting about this too, did anyone get to the bottom of it? Is a relay publishing incorrect contact list data or something? Bija will only update the contact list if it's timestamp is newer than the previous and I didn't follow anyone today so shouldn't have sent any update to the list from my end. Hmmm...

2022-12-29 16:08:46 UTC

- reply

#[1]

2022-12-29 14:30:24 UTC

- reply

I haven't tried this but it may be possible to run it in a linux container with docker on Windows.

2022-12-29 14:02:16 UTC

- reply

Will definitely consider a rebranding. I'm not that attached to the name, it does have some meaning and reasoning behind it but was also just created on a whim when I set up the github page for the project

2022-12-29 13:51:42 UTC

- reply

Apparently bija means penis in Argentina (maybe Spanish in general?) 🤣
Not quite what I was going for! #[1]

2022-12-29 13:44:57 UTC

- reply

Oh! PMSL!
Well, I've got nothing against penis's but my reasoning for the name is below:
Bija is a Sanskrit term - commonly used in both Buddhism and Hinduism - and means origin, root, or seed. One of its most common uses is referring to a 'seed' syllable, sound, or mantra.
The symbol used on the bija logo below is for the seed syllable 'hum'. This mantra may be used by a yogi or vedantin wanting to work with their ability to communicate as it is associated with speech (so they may meditate on it or chant the sound for example).
So you could see it as a mantra for 'freedom of speech'. https://res.cloudinary.com/dypmxpa1v/image/upload/v1672321185/bija/bija_jbnfjv.png

2022-12-29 13:26:15 UTC

- reply

Hey, bija is definitely not currently compatible with Windows ;)

2022-12-28 14:28:26 UTC

- reply

#[1]

2022-12-28 10:21:31 UTC

- reply

Oh... looks like proof work tags have messed with the tag order which has messed with tagging. That will also be fixed asap.

2022-12-28 10:19:42 UTC

Coming in the next #[0] release: configure proof of work requirements.
Set defaults for your own notes and encrypted messages, and set requirements for receiving messages from public keys that you're not following. https://res.cloudinary.com/dypmxpa1v/image/upload/v1672222545/bija/Screenshot_20221228_101452_vmjgtn.png

2022-12-28 09:07:38 UTC

- reply

It requires a cloudinary account at the moment and can be configured on the settings page.
I think if you're using the latest binary it will show the image upload option on the posts form. That's a mistake, it's only supposed to show the option if it's been configured.

2022-12-28 08:54:43 UTC

- reply

https://res.cloudinary.com/dypmxpa1v/image/upload/v1672217678/bija/Screenshot_20221228_085410_lfvwql.png

2022-12-28 08:53:13 UTC

- reply

https://res.cloudinary.com/dypmxpa1v/image/upload/v1672217578/bija/Screenshot_20221228_085246_dhtmux.png

2022-12-23 23:12:59 UTC

There's no such thing as a nawsterich, a nostirich, or a noysterich.
It's a nostrich! And it's pronounced like an ostrich.

2022-12-22 20:38:32 UTC

- reply

That'll be #[5], first #bitcoin heavy metal band ;)

2022-12-20 12:29:52 UTC

In light of recent events with web clients some of y'all have expressed concerns about using #[0] because it's UI runs in a browser, so I'm making a few changes.
I will be looking at integrating alby but that will likely not be until January sometime. What I am doing for now is set it up so that you don't ever need to expose your private key in the browser, you can do your account setup at the command line.
One thing I want to clarify is that although Bija's UI runs in a browser it is never directly exposed to data received from relays, everything is sanitised on the back end before being sent to the UI. The only external sources loaded in the browser are images and other media linked in posts. I wouldn't be so bold as to claim there's no vulnerabilities, that remains to be seen, but there's certainly none I'm aware of and sanitising data before it's received by the browser definitely mitigates a lot of risk.
In the current release private keys are exposed to the UI in 2 ways (which will change asap)
1) When you first create or add your keys.
2) Within the settings page there's an option to view your keys.
Again, with the upcoming changes you will be able to create/add keys at the command line so you'll never need to do the former. WRT to the latter, if you add a login password (you'll also be able to do this at the command line) the only way to view keys in the browser would be to enter your password.
* Having a login password also means that your private key is stored encrypted.
I hope this resolves some of your concerns. Without reviewing the code yourself you obviously still need to trust Bija, but again, I will look in to Alby integration so that then at least you have the choice between either trusting alby or trusting bija with the keys.
Peace 🙏

2022-12-19 17:16:37 UTC

- reply

Ooh, this looks good actually! I've set it up on bija so that you can connect a cloudinary account and then you can add images directly whey you compose a post. May add this as an option too, looks simpler and easier. Cloudinary is prob overkill for most people.

2022-12-19 16:11:28 UTC

- reply

I'm only vaguely aware of what you're talking about 🤣 Sorry

2022-12-19 16:08:22 UTC

- reply

I was hoping for a dong, but I'll take it.

2022-12-19 16:04:38 UTC

ding

2022-12-18 22:36:31 UTC

- reply

#[0]

2022-12-18 22:36:10 UTC

- reply

the social media network where speech is so free everyone even has there own pronunciation of the name 🤣

2022-12-18 19:28:29 UTC

- reply

I hear it as nos-tra, as if you're saying Nostradamus or nostrovia

2022-12-18 18:21:33 UTC

- reply

It's funny because thousands of people who never heard of nostr just saw the name for the first time in that tweet 🤣

2022-12-18 06:39:26 UTC

- reply

I'm possibly just connected to the wrong relays to get the updated metadata I guess. I'm seeing most of your posts though.

2022-12-18 06:19:22 UTC

- reply

The last metadata I have for you is timestamped at around 3 hours ago and has an empty image tag ;)
{"id": "aac61ed405b9b4e540d35265001d79a270a69c577d85a244b610bc9c690aa371", "pubkey": "6389be6491e7b693e9f368ece88fcd145f07c068d2c1bbae4247b9b5ef439d32", "created_at": 1671335426, "kind": 0, "tags": [], "content": "{\"name\":\"NunyaBidness\",\"picture\":\"\",\"about\":\"I identify as a Curmudgeonly Bastard #Bitcoin Apache Attack Helicopter\\n\\nPronouns: Thee / Thou / Sire / m'Lord / m'Leige \\n\\nHost of the Bitcoin And . . . Podcast\"}", "sig": "b0d0cea256641c63c149456190a751a0278e537fa9da79a7d56f2ca333c36b6a9a5b648b71a4c6091eec276e8d9dba3e077bc7646dc021296401a6cc47c77908"}

2022-12-03 00:06:51 UTC

- reply

I mean if there's a reply tag that does also show that it's coming from a source that uses markers. I see what you're saying about the root being the constant throughout the thread though.
I've updated all my code so that I'll be marking as root from now on.

2022-12-02 23:49:08 UTC

- reply

True, although I think it's implicitly clear having only the reply tag too. ie. if there's only one of either reply or root it implies there's only one post further up the chain.
It's probably best that everyone does it the same way though and I think root does make more sense.
The positional e-tags are a pain, unfortunately it seems like quite a few people are still using them. I've run in to issues trying to differentiate them from other kinds of posts.

2022-12-02 18:25:47 UTC

- reply

Yeah, it probably needs to be explicitly stated in the spec what to do for these first level replies so that everyone is on the same page.
I'll wait to see what replies come on your other post and then make whatever changes 🙏

2022-12-02 18:12:00 UTC

- reply

Although I'm not sure where I got that from. I think it's just not 100% clear in the specs and I thought that was what others are doing when I inspected posts coming from other sources.
No biggie to change it though.

2022-12-02 18:10:02 UTC

- reply

Oh, ok, I thought a direct response to a root post should have only a reply marker!

2022-12-02 16:16:57 UTC

- reply

testing reply after js refactor

2022-12-02 09:10:17 UTC

- reply

Begins at the beginning of December, ends at the end of November

2022-12-01 12:32:41 UTC

testing 123...

2022-11-28 19:20:37 UTC

- reply

Thanks, yes I'll give that a go 👍

2022-11-28 16:53:42 UTC

- reply

Yeah, I'm not sure. I suppose it's more efficient in some ways to only send the data once but it obviously makes it harder for a client to know the intended purpose of what it receives.

2022-11-28 16:36:08 UTC

- reply

Yeah, by the root event.
I just tried replying to a thread from an account I'm not following and that time I did see the reply when having the thread view open.

2022-11-28 15:55:31 UTC

Hey, can anyone help me with this? if I have 2 subscriptions open and a new event is created that is relevant to both of them will relays only send the event to one of the subscriptions?
I have a main, always open, subscription watching for events for everyone I'm following and then different secondary subscriptions are opened/closed depending on which view is active. When I'm viewing a thread a secondary subscription is open to watch for any events, such as replies, to notes within that thread. I noticed that I'm often not seeing replies when in thread view and I think it's maybe because the event has already been received on the main subscription. Does that sound like it would be the reason?

2022-11-27 10:45:29 UTC

- reply

#Nostrember sounds better anyway and we can at least stretch that to the end of the year

2022-11-19 22:44:36 UTC

testing

2022-11-19 15:50:18 UTC

Implement basic private messaging ✅
https://i.postimg.cc/kX6NTDCj/Screenshot-20221119-154049.png

2022-11-11 16:14:29 UTC

Agora, Anarchy, Action!

2022-11-11 15:41:17 UTC

- reply

Howdy!

2022-11-11 10:45:20 UTC

- reply

2022-11-11 09:10:26 UTC

- reply

Sorry boss

2022-11-04 23:32:06 UTC

Watching plebs simp over Elon, thinking he's going to be the saviour of free speech, is cringe af 🤮