Dikaios1517

https://linkstack.brightbolt.xyz/@dikaios1517

│Christian│Husband│Father│Presbyterian│Bitcoiner│

In that order.

Find my reviews at Nostr Reviews (npub1rsv…4dke)

Bolt12: lno1pgz95ctswvtzzq3kw0eghxwlgwrsq84tp28uqc8cewk83vhendsnz3jdum7hut3y75

Public Key

npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe

NIP-05 Address

dikaios1517@nostrplebs.com

Profile Code

nprofile1qqstwf6d9r37nqalwgxmfd9p9gclt3l0yc3jp5zuyhkfqjy6extz3jcpzpmhxue69uhkummnw3ezumrpdejqz9mhwden5te0wdcxzarfvykkzunrv9hxztnrdaks5xc3tx

Publishing to

Author Public Key

npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe

Show more details

Published at

2026-06-24T07:01:13Z

Kind type

0 Metadata

Event JSON

{ "id": "581791ee3ec4a70b68e2bc27c1f698086cb2351788003544b34f8b25df1c5d69", "pubkey": "b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb", "created_at": 1782284473, "kind": 0, "tags": [ [ "alt", "User profile for Dikaios1517" ], [ "client", "Dr. Nostr" ], [ "name", "Dikaios1517" ], [ "display_name", "Dikaios1517" ], [ "picture", "https://i.nostr.build/iQvgmYTilwvrXJVw.jpg" ], [ "banner", "https://relay.brightbolt.xyz/5c7bc3df8314f453c1d6a55a72c94253ad5ec414ea57082d58eaf44f405b604b.jpg" ], [ "website", "https://linkstack.brightbolt.xyz/@dikaios1517" ], [ "about", "│Christian│Husband│Father│Presbyterian│Bitcoiner│\n\nIn that order.\n\nFind my reviews at nostr:npub1rsv7kx5avkmq74p85v878e9d5g3w626343xhyg76z5ctfc30kz7q9u4dke\n\nBolt12: lno1pgz95ctswvtzzq3kw0eghxwlgwrsq84tp28uqc8cewk83vhendsnz3jdum7hut3y75" ], [ "nip05", "dikaios1517@nostrplebs.com" ], [ "lud16", "dikaios1517@nostrplebs.com" ] ], "content": "{\"about\":\"│Christian│Husband│Father│Presbyterian│Bitcoiner│\\n\\nIn that order.\\n\\nFind my reviews at nostr:npub1rsv7kx5avkmq74p85v878e9d5g3w626343xhyg76z5ctfc30kz7q9u4dke\\n\\nBolt12: lno1pgz95ctswvtzzq3kw0eghxwlgwrsq84tp28uqc8cewk83vhendsnz3jdum7hut3y75\",\"banner\":\"https://relay.brightbolt.xyz/5c7bc3df8314f453c1d6a55a72c94253ad5ec414ea57082d58eaf44f405b604b.jpg\",\"display_name\":\"Dikaios1517\",\"lud16\":\"dikaios1517@nostrplebs.com\",\"name\":\"Dikaios1517\",\"nip05\":\"dikaios1517@nostrplebs.com\",\"picture\":\"https://i.nostr.build/iQvgmYTilwvrXJVw.jpg\",\"website\":\"https://linkstack.brightbolt.xyz/@dikaios1517\"}", "sig": "f823dfb42210e4bd6e0d7ffc2ec02370afdc3d004f0c12664204bafa637dc20475a4d3ae14cf0ada12fc856dd946cfd20844b82d4736a1667317a0296b1490a7" }

Last Notes

2026-07-07 11:28:55 UTC

GM Nostr.
Headed to the airport. ✈️

2026-07-07 06:11:03 UTC

- reply

Nostr relays only really handle text based notes. For the audio side of things, we would need it stored on some kind of media host, like a Blossom server.
I actually have a recent example of doing just that.
#nevent1q…0xkq

2026-07-07 04:10:15 UTC

Shakespeare does a bangup job creating websites with Nostr integration! What models are y'all getting good results from without breaking the bank?
Claude Opus really chewed through my credits creating a pretty basic blog site.
#asknostr

2026-07-06 22:59:37 UTC

- reply

Nothing I am aware of, but I support this initiative. You thinking #pintchain or get rid of the "chain" language and go with something else? I am terrible at thinking of anything catchy.

2026-07-06 22:53:25 UTC

- reply

Silly question. It will depend on how they were exposed, but in most cases the blame is not one-sided. Enough blame to go around for both sides.

2026-07-06 21:13:16 UTC

- reply

My Gen-Z daughter got it, but she's homeschooled, so she doesn't count.

2026-07-06 19:20:59 UTC

- reply

I see my mutes! Took a minute. I had to make a change to publish a new version of my list from Amethyst, so it must not have been able to find my previous one. Looks great now!
Search relays all loaded properly, too.

2026-07-06 19:14:02 UTC

- reply

I'll be away for a few weeks. Won't have opportunity to test anything new and shiny. Will definitely be excited to do so when I get back home, though!

2026-07-06 18:09:13 UTC

Forgive the article spam from me over the next few minutes. I am updating my articles with some hashtags that I am hoping will make my new blog site automatically categorize them.

2026-07-06 02:57:36 UTC

Wonderful Lord's day worshiping with God's people here in North Idaho!
Will miss them over the next two Lord's days, but looking forward to seeing the Holy Spirit work in the hearts of those who hear the gospel in Prague!

2026-07-05 07:15:16 UTC

- reply

https://kojira.github.io/nostr-license/

2026-07-05 07:05:05 UTC

- reply

Yeah, I had my Hermes Agent create a report on the read and write relays that my follows have listed in their kind 10002 and legacy kind 3 relay lists.
The first 25 or so ranked by number of npubs reading or writing from the relay is not bad. Mostly solid relays that are all still online. After that it goes downhill fast.

2026-07-05 06:48:22 UTC

Pretty hilarious. My Nostr license says I joined back in 1975. I believe that's because I was messing around with posting notes with false timestamps.
https://relay.brightbolt.net/f4175b1ae4f8ccee11389f90c34dc665a8d511e9f730a79fcee26f846a0f0a10.png

2026-07-05 06:21:51 UTC

Some of y'all got some long dead relays in your relay lists.

2026-07-05 01:51:57 UTC

- reply

Very true. As a general rule for anyone just using the version available in Umbrel's app store, though, it definitely applies.

2026-07-05 00:40:30 UTC

- reply

I wouldn't recommend running NostrRSrelay on Umbrel as a public relay. It's intended to just be a private backup of your notes for a reason.
The GUI is on the same port as the relay, so if you expose the relay at 'wss://relay.yourdomain.com' the GUI will be accessible at the same domain, but 'https://', and NostrRSrelay has no authentication required to access the GUI.
Now, there's not much that someone can do from that GUI, but they can change out the npub whose notes are automatically backed up to any other npub... Then you end up with content hosted on your relay that you did not intend nor want.

2026-07-05 00:29:24 UTC

- reply

Absolutely! If it's encrypted, it should stay encrypted unless the user actively chooses to publish it in plain text.

2026-07-04 23:06:42 UTC

- reply

So, it will blast events that are written to it directly, but I assume not events that it aggregates, right?

2026-07-04 22:52:49 UTC

- reply

New WoT aggregator relay?

2026-07-04 22:25:03 UTC

- reply

"Git is..."?
Phone keyboard typos...
*Got it figured out.

2026-07-04 22:21:46 UTC

Nostr Devs,
I chatted with @npub15yp…mpcx about this last night, as I have been testing out his new client #Circl, but it bears notice of any client dev that supports lists of various kinds (relay lists, mute lists, bookmark lists, etc) in their client, or who plan to in the future.
NIP-51 states that these lists "can be public or private" and therefore may have plain text entries, or encrypted entries in the "content" field. It does not specify what list kinds may or may not have encrypted data. Therefore, your client should be able to handle encrypted data in almost any of them.
NIP-51 also says, "When new items are added to an existing list, clients SHOULD append them to the end of the list..." Appending only adds information, it does not remove any information that is already there. Adding an item to a list should never result in the loss of existing entries from that list, encrypted or otherwise.
If Nostr clients fail in this, Nostr interoperability and user experience suffers.
Here is what I would suggest:
Minimum: Your client should not overwrite encrypted data when adding a new entry to a list that has an encrypted payload in the "content" field. Leave that field there and as is if your client isn't set up to utilize it.
Better: At least decrypt and display the data to the user, so they don't think their whole mute list has been nuked because your client doesn't display the encrypted entries. And when your client is used to add new entries to the list, leave the encrypted data alone. Just add a new plain-text entry if you don't want to support adding encrypted entries to lists.
Best: Not only display the encrypted entries to the user, but indicate in the UI which entries are public and which are private. When the user wants to add a new entry, present them the option to add it as public or private.
There are certain lists this does not apply to, because their content has to be public for the list to function, such as kinds 10001, 10002, or 10050. However, the vast majority of other list types often do contain encrypted entries, especially since one of the most popular Nostr clients (Amethyst) is encrypting a lot of these lists by default.
The most common way I have personally had list entries get nuked lately is from clients that did know what to do with encrypted entries in the "content" field of my mute list, my favorite relays list, and my search relays list. Things like this are what make many people feel like Nostr is broken, when it's just that client devs aren't paying attention to NIP-51 when they implement lists.
#devstr #ndoc

2026-07-04 21:35:30 UTC

- reply

I am sure @npub1syj…f6wl would appreciate that. He mentioned that he'd like to have it, but has been putting it off.
If you do, can you build in a retention window where it will delete notes older than X days, where the user can set the timeframe, and also the ability to select npubs that it never deletes notes for.

2026-07-04 21:25:57 UTC

- reply

Oh, I know that part. My question was about your notes that DON'T tag me that have been showing up in my WoT relay.
Turns out, they're getting blasted there by nostr.land's event cannon feature.

2026-07-04 20:04:42 UTC

- reply

Yes, the content is what matters, but in this case the question is what word was used in the original document. The word Jefferson used was "unalienable."

2026-07-04 19:46:00 UTC

- reply

I want, but I probably won't have a chance to fiddle with that for a while.

2026-07-04 19:44:37 UTC

- reply

Ok, that makes a whole lot of sense now. Thanks!

2026-07-04 19:38:43 UTC

- reply

For instance, here's a reply you made to @npub12r0…9qrx earlier that I have on my WoT relay. But @npub12r0…9qrx doesn't use my relay as an inbox relay, and I am not p-tagged in your reply.
But... @npub12r0…9qrx DOES use nostr.land, and the event cannon may be blasting to me.

2026-07-04 19:35:58 UTC

- reply

Yeah, replies with me tagged, that makes sense. It's the kind 1 notes, or replies to other people who don't have my relay listed as an inbox that make less sense why I am getting them.

2026-07-04 19:31:43 UTC

- reply

I do have it set as an inbox relay, but that would only explain notes where you've tagged me ending up on it. I have regular kind 1 notes from you without me tagged.
I bet it is the nostr.land blaster. @npub1226…grkj how does nostr.land determine where the event cannon will blast notes? Is my WoT relay one of the relays it blasts to?

2026-07-04 19:21:16 UTC

- reply

@npub10np…tl5h @npub1m64…uaks @npub1qyx…mu7u are you guys publishing or blasting to my WoT relay? How is it getting your notes?

2026-07-04 19:20:07 UTC

- reply

Really? So all of the folks' notes on my wot.brightbolt.xyz relay, which is just my Nostr Relay Tray relay, are people actively choosing to publish to it? I thought for sure it must be aggregating them, because I have done absolutely zero advertizing of that relay, other than having it in my own relay list.

2026-07-04 18:36:02 UTC

- reply

Except, it's actually "unalienable."
Source: https://www.archives.gov/founding-docs/declaration-transcript

2026-07-04 18:22:30 UTC

- reply

You a Reformed brother too @nprofile…2yvq?

2026-07-04 18:16:53 UTC

- reply

Git is figured out. Apparently it was restricted to Firefox Mobile with Glow as a PWA.
No issues when accessing through the regular browser UI, and no issues when using Brave either through the browser UI or as a PWA.

2026-07-04 10:03:15 UTC

- reply

I see this list of relays on the right side of the page on desktop. Most of them are my inbox/outbox relays, but some of them are not on any of my relay lists. Are these the relays that #Circl is currently connecting to, and how is it deciding what relays to connect to in addition to my inbox/outbox relays?
https://image.nostr.build/b498962872516308beb83fdd7c6753aad0c4cd01da1e7fd5f19584309c2d1568.jpg

2026-07-04 09:56:22 UTC

- reply

This leaves open the possibility that users simply won't realize that some of their list entries are public and some are private, but this can be indicated with an open or closed lock icon next to the entry in the UI, and tapping on it can display a message indicating that the entry is public or private.

2026-07-04 09:52:34 UTC

- reply

Right? It really is Nostr in a nutshell.
Here's what I would hope for:
Client encounters a list, let's say kind 10007 since that's what we've been dealing with most recently, and it has a mixture of encrypted entries and public entries. It should parse the list and be able to display both encrypted and public entries to the user. This way users who didn't realize that a different client (Amethyst) was adding encrypted entries don't think that their list got nuked because they don't see anything where their search relays should be.
When the user wants to add a new entry to the list, the client should ideally offer them the option to save that entry as public or private. If you don't want your client to support adding private entries to the list, then at minimum it should just add the public entry and leave the rest of the entries already on the list in whatever state they are, public or encrypted.
The same should be the case for clients like Amethyst that want to default to adding encrypted entries to lists. If there are public entries already on the most recent version of the list, then the client should just add the new encrypted entry and leave the existing public entries unencrypted.

2026-07-04 09:40:31 UTC

- reply

The curse of the fall made exercising dominion more difficult (see Genesis 3:17-18), but did not eliminate our mandate from God to "fill the earth and subdue it, and have dominion over the fish of the sea and over the birds of the heavens, and over every living thing that moves on the earth."
Of course, it won't be fully realized until the new heavens and new earth when the saints inherit the renewed creation as fellow heirs with our Lord Jesus Christ. Nevertheless, the ultimate fulfillment does not absolve us from our duty to exercise dominion now, when appropriate and possible.

2026-07-04 09:30:08 UTC

- reply

How does Nostr Relay Tray find the notes that it aggregates when WoT mode is turned on? Is it just polling popular relays, then, rather than the relay owner's follows' outbox relays?

2026-07-04 09:25:24 UTC

- reply

Yeah, it's tough to balance for some things. WoT, for instance, is only useful if follow lists are public. But then, if you want to follow someone privately, there are kind 30000 lists for that, which can have private entries.
Mute lists could be a good form of crowd-sourced spam mitigation, but then I don't always mute someone because they're a spammer, either. So maybe we should make reporting great again for those within our WoT to optionally use for hiding spam and such.
Relay lists in particular are an interesting case. Having some social indicators from your WoT around what relays might be good to use for search or for proxy relays, and what relays to avoid might be really good signal, but it should be the user's choice whether they want to "advertise" for that relay by having it as a public entry in those relay lists.

2026-07-04 09:05:51 UTC

- reply

Yeah, I have noticed that Amethyst is pretty well defaulting to private for any NIP-51 list kind that does not absolutely have to be public.
I would check to make sure Satori can handle encrypted data in any of the list kinds you plan to support, except the ones that obviously would not have encrypted entries, like 10002 and 10050.

2026-07-04 08:32:47 UTC

- reply

Nerd here. I have a couple different options for always-on NIP-46 signers, between Amber on my phone and Signet or Bunker46 on my Start9. Yet, I wouldn't know where to start with setting up a scheduler DVM.
I do agree that an always-on NIP-46 signer is probably not the solution for most users. Do most users have a need to schedule posts, though?

2026-07-04 08:18:00 UTC

- reply

Got it. That must be the case, because nothing is showing up for me in #Circl. I am pretty sure I have a couple threads muted and a few words as well.

2026-07-04 08:15:31 UTC

- reply

Yeah, but I probably could have had the same results with 90% of other clients that support kind 10007.
Seems most client devs don't realize that just about ANY list type can have encrypted entries, and I think @npub1gcx…nj5z philosophically believes most lists should be private by default, so Amethyst just encrypts every list that doesn't absolutely have to be public. I tend to agree with that approach.

2026-07-04 07:54:40 UTC

- reply

Called it! Added search.nostrarchives.com as a search relay from a different client, went back to Amethyst and all my other search relays are GONE.

2026-07-04 07:51:51 UTC

TIL that Amethyst encrypts kind 10007. Search relay list. So any client that doesn't look for and decrypt the "content" section treats it like you have no search relays...
Now for the fun of testing whether adding a search relay from another client will nuke the encrypted portion of the list. My sats are on, yes, yes it will.

2026-07-04 07:45:33 UTC

- reply

Not supporting private mutes yet, I take it? My mute list shows as empty because they are all encrypted.

2026-07-04 07:25:36 UTC

- reply

Thanks for playing along. I was testing out @nprofile…qnef's new client's "Circles" feature.

2026-07-04 07:24:03 UTC

- reply

2026-07-04 07:13:12 UTC

- reply

Nah, that's great. Created a circle of my Reformed brothers, and now I can poke all of them when I have theology to discuss. 😂

2026-07-04 07:10:37 UTC

- reply

I had not. I have now.

2026-07-04 07:03:49 UTC

- reply

My daughter also got a great shot of the aurora tonight.

2026-07-04 07:02:55 UTC

@npub15yp…mpcx #Circl is looking great! Haven't run into any issues so far while logged in via @npub1h0u…rwx8 on Android.
From what I can tell, posting something to a "Circle" just p-taggs everyone in that circle, but it is otherwise just a normal kind 1?

2026-07-04 06:52:56 UTC

Q1: What is the chief end of man?

2026-07-04 06:38:11 UTC

- reply

I seem to remember this being an issue for us in the past as well, back when I ordered a hoodie from you.

2026-07-04 06:36:53 UTC

- reply

Correct.

2026-07-04 06:18:31 UTC

- reply

Nevermind! Got it in 0xChat, just not in Amethyst or Wisp. lol!

2026-07-04 06:17:05 UTC

- reply

Got nothin'. NIP-04 or NIP-17?

2026-07-04 03:05:21 UTC

- reply

Except, it's not up, and there is no reason to believe it will ever be up again.

2026-07-04 03:02:44 UTC

- reply

Ummm... Glow is accessed through the web browser. At least the one Biebs mentioned above. There is no new version to install.

2026-07-04 00:28:35 UTC

- reply

Is haven-kit on Umbrel updated to include the latest features, like whitelist and blacklist?

2026-07-03 23:38:17 UTC

- reply

Yeah, I don't know what the default relays are in Damus, but I imagine you are right that the vast majority of the notes on their feed just come from that relay, unless they have taken the time to add some aggregator relays already.

2026-07-03 23:32:19 UTC

- reply

Great. Just clarifying, because your previous reply had stated, "if damus relay goes away, they (Damus client users) cannot see any notes." But that's not the case. Damus users will still see notes from the other relays in their list.
This service is very useful for those who are using clients that don't have outbox model, including Damus. I imagine users will see a more full feed with this added even before Damus relay is shut down.

2026-07-03 23:27:12 UTC

- reply

Worth it for users who can't or don't want to host their own WoT relay, for sure!

2026-07-03 23:16:11 UTC

- reply

They'll still see notes that are on one of the other relays in their relay list, right? Just not any notes that were on Damus' relay. Damus isn't like Primal, only reading from Damus's own relay like Primal only reads from its own caching server.

2026-07-03 23:13:00 UTC

- reply

Follow-up question. Are the notes being stored on your infrastructure? Looks like they must be since one can adjust the polling frequency. I would think this would need to be a paid service unless the retention time-frame is low enough that storage is minimal. But then, bandwidth would also become an issue, depending on how many people use it.

2026-07-03 23:07:55 UTC

- reply

Updating now!

2026-07-03 23:03:55 UTC

- reply

@npub1syj…f6wl is this similar to what Nostr Relay Tray already does by pulling in notes from the relay owner's WoT?
@npub10np…tl5h would this be ideally used as a proxy relay in Amethyst? These are described as "Aggregator relays the app must use to download your feeds from, like filtr.nostr.wine. This replaces the outbox model and will make the app connect to only the relays in your lists."
Or do you imagine it more as a single-relay feed in a client like Jumble or your own Relay Tools app, where the user can browse notes from that single relay, rather than relying on the client to compile notes into a feed from their follows' outbox relays.

2026-07-03 18:47:16 UTC

- reply

@nprofile…z585 why can't I type in this field? Immediately opens and automatically closes my keyboard every time I tap on it.
https://relay.brightbolt.net/a750ab4335bf73df1e3c2c053fd3e47c3ffdfea320b60419cc51aa0bf2f56ad2.mp4
Also, no NWC that I could find makes it less useful for Nostr.

2026-07-03 18:17:19 UTC

- reply

I don't know about good ones. These are the current default search relays in Amethyst, which are the ones I have been using.
https://relay.brightbolt.net/3bc2177162f3f357d9ac5b4708775bab309a6736889400f487a02f3105d9ae9d.jpg
Don't mind the slow ping numbers. That's just because I have Tor turned on.
The main thing is the relay needs to support NIP-50, and it should ideally be aggregating notes that you would be interested in. Unfortunately, finding relays on the basis of the NIPs they support isn't an easy task.

2026-07-01 19:39:19 UTC

If you aren't determining what Bitcoin is for yourself, someone else is determining it for you.
If you aren't verifying the supply of Bitcoin for yourself, you are trusting that your custodian's IOU is worth more than the paper it's printed on.
Run a node. Connect your wallet to it. Custody your own stack.

2026-07-01 19:14:40 UTC

- reply

Looking good!
Little UI bug I noticed: When selecting to compose an Article, the option to select "Picture" goes away. It is available as an option when selecting "Poll" or "Note" though, so the user just has to go back to one of those options to have the option to select "Picture" again.
https://relay.brightbolt.net/134f6d2b83de0733b7727a6c4219ae805f0fc015102ab12854d28810bf15a69d.png

2026-07-01 17:48:07 UTC

- reply

"an ad re han"? I meant "an ad he ran."

2026-07-01 17:46:38 UTC

- reply

Livera used to have an ad re han for an out of the box node, can't remember which one, but in it he said that the easiest way to tell whether Bitcoin is healthy is whether the number of nodes is going up, or going down. Is it becoming easier to run a node, or harder?
Somewhere along the line, many Bitcoiners have forgotten that.

2026-07-01 04:37:21 UTC

- reply

Rocking the Dark Garnet. Too bad I hardly ever use my iPhone.

2026-07-01 04:33:16 UTC

- reply

Cigars and drinks with the two of you gents, and a few of our Reformed brothers on here, is definitely something I would love to see happen.

2026-07-01 02:46:30 UTC

Bitcoin = Low time preference.
Christ = Eternal time preference.
#nevent1q…pce3

2026-07-01 01:26:41 UTC

- reply

Yeah, it's the experimenting with various clients that can sometimes result in things getting nuked.
The absolute best tool I have ever found for fixing things when that happens is Luminostr: https://tsukemonogit.github.io/luminostr/
Very simple interface. Just plug in your npub and the kind number of note that got nuked, and then tell it how many relays you want it so search for that note on. I typically just leave it at the max number of relays (400). The search takes longer, but then you can be pretty confident that the previous version of the note you are looking for will be found. You can then choose to publish the previous version of that note to restore what was nuked.
The only thing that makes this tool a bit less user friendly is that it expects you will know the kind number you are looking for, rather than providing you with a dropdown to select "short text note" or "follow list" and such. So here's a breakdown of the main note kinds you may find this tool useful for:
Kind 3 - Your follow list. These things get nuked all the time when switching between clients.
Kind 10002 - Your Outbox/Inbox relay list. That's the one I just looked up on Luminostr for you to find out when it got wiped.
Kind 10000 - Your mute list. Like the follow list, I hear about this one getting nuked a lot.
Kind 10012 - Your favorite relays list. Not to be confused with your regular relay list for outbox/inbox. This list is just relays you like to browse. I recently had mine get wiped and had to restore it using Luminostr.
If you want a list of other note kinds and what they are for, you can find one at https://github.com/nostr-protocol/nips

2026-07-01 00:33:04 UTC

- reply

Hmmm, I have not seen relay lists get nuked very often.
Taking a quick peek, it looks like it happened today when you added "chat.virginiafreedom.tech" as an outbox/write relay. Do you recall what client you did that from? That client apparently could not find your previous relay list.
Speaking of which, here's what you previously had set, so you can easily set it back up again:
Outbox/Write:
wss://relay.primal.net/
wss://nostr.land/
wss://eden.nostr.land/
wss://spatia-arcana.com/
Inbox/Read:
wss://nostr.land/
wss://eden.nostr.land/
wss://spatia-arcana.com/
wss://spatia-arcana.com/inbox
Probably only need to have "spatia-arcana.com/inbox" listed in your inbox relays, and not "spatia-arcana.com" as well.

2026-06-30 23:53:06 UTC

- reply

On a separate but related note, is there a way to have Haven on Start9 use the Tor service for blasting notes to other relays?

2026-06-30 23:39:06 UTC

- reply

Sorry. What was the quesion?

2026-06-30 23:37:47 UTC

- reply

Don't know of any desktop clients that you can restrict to only pulling from your local relay. Where your IP is going to get leaked one way or the other is when you are posting. If you only post to that relay, then no one outside of your local network can see what you posted. If you have your relay blast your notes to other relays, then your IP will be leaked by your relay, unless it is posting from behind Tor or a VPN.
If you run a Start9, you can check out @npub1m2j…3wgu 's very bare-bones and early development client called Satori, which can use Start9's Tor service for both inbound and outbound traffic. It can also be used to browse a particular relay's feed, but bear in mind that since Satori uses Tor, you will need to give it your relay's Tor address, if it has one, since it won't be able to access your relay via its local address.

2026-06-30 23:03:17 UTC

- reply

So, my follow-up question for that would be: If we readily admit that the noetic effects of sin hamper our ability to rightly interpret the general revelation version of the moral law, or "muddy the water" as you put it, even in the best circumstances, why would we rely on the natural law as "sufficient" for ordering society, when the clearer and more certain version of the moral law is readily available in special revelation? For the sake of finding supposed common ground with heathens, unbelievers, and God-haters?
I would generally agree that the first table is not to be enforced civilly, but that is because the mandate of civil government according to Scripture is "Whoever sheds the blood of man, by man shall his blood be shed" (Gen 9:6), and is therefore entirely to be men enforcing penalties on the sins of men against one another that rise to the level of criminality, and not enforcing penalties on sins only against God, who will finally and eternally vindicate himself. It is not because natural law only reveals to us that we must love our neighbor as ourselves (2nd table), but rather because special revelation itself limits the scope of the civil magistrate's mandate. Natural law places no such limit, for even Romans 1 clearly points out that general revelation plainly tells us we ought to love the Lord our God with all our heart, soul, mind, and strength (1st table), since by it men can plainly see "his invisible attributes, namely, his eternal power and divine nature, have been clearly perceived, ever since the creation of the world, in the things that have been made. So they are without excuse" (Rom 1:20).
That's not to say that we won't still misinterpret special revelation when applying it to the civil sphere, but we'll be better off than trying to rely on general revelation alone, since it is quite literally spelled out for us in the pages of the inerrant and authoritative Word of God. Why should we abandon the superior epistemological standard of the Word of God written, in favor of an inferior one? We would not do so in any other area of life, but we should be required to do so in relation to the magistrate?

2026-06-30 22:31:15 UTC

- reply

It did not. But that's not @npub14hq…jjzu 's point, is it?
He's not saying that "because kings, priests, and others in the 'ruling class' didn't write the Bible, they have no power." Rather, he is merely saying that the Bible cannot be dismissed as having been written by the ruling class to shore up their power.
It should be noted that the Vatican only gained so much power in the first place by locking the Bible away from the common man. Protestants broke that stranglehold 500 years ago, and that eventually led to even Rome admitting that the Word of God should be available in the language of the people. That has continued to loosen the Vatican's control even over Roman Catholics.

2026-06-30 22:25:04 UTC

- reply

I don't know if it's so much "bored theology students" as it is men wanting to be known for thinking of something that has not been thought of before, so they can have their name become an "ism."

2026-06-30 21:03:22 UTC

- reply

Matthew 23. Note: "scribes and pharisees" would fall under the class of clergy.
Also note that as @nprofile…2qz5 pointed out, the priests were the ones who killed Jesus. Or as Peter preached to the priests after they apprehended him and John: "This Jesus is the stone that was rejected by you, the builders, which has become the cornerstone. And there is salvation in no one else, for there is no other name under heaven given among men by which we must be saved.”
— Acts 4:11-12
The proud, even among the clergy, are recorded as having rejected and killed their Messiah, while the humble and contrite come to him.

2026-06-30 20:14:32 UTC

- reply

Beat me to it.

2026-06-30 20:10:34 UTC

- reply

They certainly thought it did, but God called them out for that, too.

2026-06-30 20:06:48 UTC

- reply

Wait, is Tipton's very standard Christology causing the stir, or Garner's wonky view of Christ receiving adoption at the resurrection?
Tipton's criticism of Garner is bog standard Nicean Christology that all orthodox Christian denominations have agreed upon for 1700+ years.

2026-06-30 14:15:00 UTC

#nevent1q…5new
#nevent1q…5new

2026-06-30 05:27:51 UTC

- reply

That helps. I don't know if I fully agree that the decalogue is identical with the law of the conscience, and what even fallen man "cannot not know." I think the noetic effects of sin have marred and hampered our ability to rely on our conscience effectively. Otherwise, it would not make much sense for Paul to say, "I would not have known what it is to covet if the law had not said, 'You shall not covet'" (Rom 7:7). There must be, at minimum, some clarifying or correcting effect of the revealed moral law to the "natural law" men know by way of their conscience hindered by their fallen estate.

2026-06-30 01:08:39 UTC

- reply

There are all sorts of reasons that a client may not be able to connect to a relay besides it just being down.
I won't say that it couldn't be a client performance issue, but most of the time inconsistencies on Nostr in general are due to not being connected to the same relays for one reason or another. No one's fault. Just the nature of working with multiple relays rather than a centralized server.

2026-06-29 23:39:52 UTC

- reply

The relays Amethyst can successfully connect to do factor in, though. It would be doing text search via your search relays. If the note isn't on the ones Amethyst was able to connect to, and is only on a search relay it could not connect to, then it won't find it.

2026-06-29 22:51:55 UTC

- reply

Yeah, exactly. The reason being that it is inconsistent what relays can be connected to at a given time and the note doesn't exist on Amethyst, it exists on some relay or another.

2026-06-29 22:40:29 UTC

- reply

You call that natural law and then quote God's revealed moral law. Would you classify "natural law" as part of general revelation or special revelation?

2026-06-29 22:37:02 UTC

- reply

There are probably a lot of reasons behind that. First, people aren't necessarily using the same relays they used a few years ago. I know I'm not. When they switch, they rarely export their notes from their old relays and import them to their new ones.
Relays also don't necessarily keep notes for that long. Popular relays may have automatic deletion of old notes, or then theres the Damus relay, which gets fully nuked from time to time.
If the note does still exist somewhere, it might be on a relay that is currently offline, or that the client is having trouble connecting to, or that doesn't support search, or that has rate-limited requests, or... You can see where this is going.
So long as notes can live on various different relays that aren't all following exactly the same policies, it's going to be unpredictable whether you can find a specific note.

2026-06-29 10:32:37 UTC

- reply

Going to have to track down some of my musings on that topic and compare notes.

2026-06-29 09:40:04 UTC

- reply

Stop giving me things to read!!!
That looks really good...

2026-06-29 04:48:29 UTC

- reply

I love the sentiment, but this is not entirely accurate. What was actually handed down to us from 1646 read quite differently in WCF 23.III.
Here's the original:
"The civil magistrate may not assume to himself the administration of the Word and sacraments; or the power of the keys of the kingdom of heaven: yet he hath authority, and it is his duty, to take order, that unity and peace be preserved in the Church, that the truth of God be kept pure and entire; that all blasphemies and heresies be suppressed; all corruptions and abuses in worship and discipline prevented or reformed; and all the ordinances of God duly settled, administered, and observed. For the better effecting whereof, he hath power to call synods, to be present at them, and to provide that whatsoever is transacted in them be according to the mind of God."
This was amended in 1788 to read as you quoted it, and as was adopted by the newly formed PCUSA in 1789, and later by the OPC and PCA when they broke away from the mainline denomination.
Likewise, what you quoted as 31.IV was originally 31.V in the 1646 version, but the 1788 revisions removed the original section 31.II, thus bumping paragraphs III, IV, and V to being numbered II, III, and IV respectively. The original paragraph II read as follows:
"As magistrates may lawfully call a synod of ministers and other fit persons to consult and advise with about matters of religion; so, if magistrates be open enemies to the Church, the ministers of Christ, of themselves, by virtue of their office, or they, with other fit persons, upon delegation from their churches, may meet together in such assemblies."
So what the Presbyterian Church, even in the colonies, confessed was a much more integrated idea of the Church and State mutually protecting one another from corruption. To that end, it granted the civil magistrate some significant ecclesiastical authority and it was not until 1788 that the WCF was amended to remove reference to any authority of the civil magistrate over ecclesiastical affairs.
This was in close relation to the drafting of our Constitution itself, which was drafted in September of 1787 and ratified in June of 1788. Just as the US Constitution built protections for the Church from civil government into the First Amendment, the Church likewise built protections for itself from the civil magistrate into the Confession that had not been present before.
So, what you quoted doesn't show the influence of Westminster on Enlightenment thinkers (since that version of the text did not exist at the time), so much as it shows the influence of having overthrown tyrannical government on the Church's previously held views concerning the relationship between Church and State.

2026-06-29 03:22:05 UTC

- reply

The registry on Start9 is not mine. It belongs to @npub1c0r…qs7w