Damus
Dikaios1517 profile picture
Dikaios1517
@Dikaios1517

│Christian│Husband│Father│Presbyterian│Bitcoiner│

In that order.

Find my reviews at nostr:npub1rsv7kx5avkmq74p85v878e9d5g3w626343xhyg76z5ctfc30kz7q9u4dke

Bolt12: lno1pgz95ctswvtzzq3kw0eghxwlgwrsq84tp28uqc8cewk83vhendsnz3jdum7hut3y75

Relays (6)
  • wss://nostr.land/ – read & write
  • wss://proxy.nostr-relay.app/37d4c33b6dd11e1553c3d7aabbed24bce9a50fc72f71464d39f8f52ce83becf8 – write
  • wss://relay.brightbolt.net/ – write
  • wss://spatia-arcana.com/ – read & write
  • wss://wot.brightbolt.net/ – read
  • wss://relay.brightbolt.net/inbox – read

Recent Notes

TheGrinder · 43w
GG (for some reason this note remains on the top of my timeline with posted "now") 🤔
Nunya Bidness · 43w
Is there a thing going around?
Shawn · 43w
nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q FYI that this note from earlier today is now stuck at the top of my timeline and shows as "Now" permanently. nostr:npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe you have been enshrined. lol
Derek Ross · 42w
internest that #notedeck says this note is from 23 years ago...
Derek Ross · 42w
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s why does #notedeck keep this pinned at the top of my feed. i can't get rid of it. it has a timestamp of +23 years.
CTarian · 42w
The Declaration on tour right now?
ManiMe · 40w
nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe 👆🏼 Is this post is gonna remain at the top of my timeline every day for the next two decades? > “It was actually an attempt at a date of July 4th, 1776, but I didn't realize that anything prior to January 1st, 1970 would ...
The Daniel 🖖 · 40w
I can’t even see this note in any client besides Damus or Notedeck because it’s apparently set to a date 23 years in the future.
Dikaios1517 profile picture
GM

He is risen!

"Concerning his Son, who was descended from David according to the flesh, and was declared to be the Son of God in power according to the Spirit of holiness by his resurrection from the dead, Jesus Christ our Lord." - Romans 1:3-4
Vibe Captain · 1d
but is it a general term for king, or does it have a specific meaning in terms of Israel? David was the Lord's annointed, but he was not the Messiah
Dikaios1517 profile picture
It comes from the Hebrew verb "mashach", which simply means to annoint as with oil, which was a common practice for kings, but also for other offices, and even objects. The participle form, "meshiach," from which we get the term Messiah, is used of kings for sure, but also of priests and prophets, which is of interest since Christ is not only king, but also priest (of the order of Melchizedek) and prophet.
Dikaios1517 profile picture
We've got some really great clients that support the outbox model and also support Tor natively in the app. That's really great for freedom of speech, since users don't have to feel locked into using the big relays in order to be seen, but can use their own relay or a community relay.

The next big step is going to be easy to run personal or community relays and Blossom servers with Tor endpoints. Is anyone already building something like this? @Geektoshi built Haven-Kit, forked from Haven, a while back, but ran into trouble exposing the relay endpoints over Tor. It only wanted to expose the GUI via Tor and that's obviously not ideal.

@Cody also has Nostr Relay Tray, which is a really easy to run relay that can be exposed to clearnet via a proxy in a single click. Very handy, but no Blossom server integration and no Tor.
Analogue Dog · 2d
Publishing content to my own homeserver implies that my data is owned by me regardless of whether it's scraped by a third party. This is different to me publishing my content to half a dozen different...
Dikaios1517 profile picture
We weren't talking about ownership, though. We were talking about reliable deletion of data. Ownership has little to do with whether you can reliably expect that your data has been deleted, access does. If anyone can access the data, they can copy it.

Of course, having only one server that you are posting ypur data to makes it less likely that it will still be living anywhere else when you want it deleted, and that is an advantage of Pubky, but it comes with the disadvantage of not having redundancy: less censorship resistance.
Analogue Dog · 2d
The redundancy and censorship resistance is augmented by PKARR. (Public Key Addressable Resource Records). Your Pubky points towards one or multiple resource end-points. And since the PKDNS entry lives in Mainline DHT, it is impossible to censor.
Analogue Dog · 2d
Pubky uses 'homeservers'. Users control their private keys as well as their content. pubky.app
Dikaios1517 profile picture
Homeservers don't solve this by any measure. If you run your own homeserver, you might have more assurance, but if you don't then you are still just trusting that the operator actually deleted your data and didn't keep a copy.

If the data on that homeserver can be read by others, then you have no way of knowing whether any of them made a copy that could be republished elsewhere.
Analogue Dog · 2d
Publishing content to my own homeserver implies that my data is owned by me regardless of whether it's scraped by a third party. This is different to me publishing my content to half a dozen different relay destinations. Pubky also has an elegant solution to mitigage data scraping... more info on p...
Analogue Dog · 2d
Credible exit (i.e. ability for user to delete all their content)
Dikaios1517 profile picture
There is no such thing.

Centralized platforms give us the illusion of being able to delete our data, but we have no way of knowing whether they or anyone else with an interest in doing so, has created a copy.

It is also impossible to prove the non-existence of anything.

Deletion on Nostr will always be "best effort," and a client like Amethyst in particular really can't do anything about that, because deletion policy is handled where the data is stored: on the relays. All Amethyst can do, which I believe it already does, is send a deletion request to all known relays in accord with NIP-62. It is then up to that relay to comply with that request.

Relays that are offline, or that are not public may never receive that request. Still other relays might receive the request and ignore it. There is nothing Amethyst or any other client can do to prevent that.
Analogue Dog · 2d
Pubky uses 'homeservers'. Users control their private keys as well as their content. pubky.app