charek

It would take years to onboard 1 billion people to custodial lightning. Specifically, if 100k transactions per day are possible, in a year we can onboard 36.5 million people (and that is only if every single transaction is dedicated to opening a lightning channel).
It would take 30+ years to get 1 billion people on custodial lightning ...
and this is an optimistic estimate!
surely people will use custodial solutions, but then why use btc rails at all? just swap to stable coins, or some other chain for small txs.

2025-07-27 15:20:35 UTC

- reply

same here! also really enjoy the level headed takes, and the lack of fear of doubting lightning adoption. #self canceling due to rational criticism should be frowned upon.

2025-06-08 18:18:13 UTC

- reply

the new fit looks great!

2025-06-01 21:16:06 UTC

- reply

#nevent1q…xnvn

2025-05-31 21:37:07 UTC

Let's talk business models
what are really novel ways to start businesses with nostr, and with all the other people that dedicate time to it?
can we collect them here for the interest of anyone curious

2025-05-27 22:08:32 UTC

- reply

it does for me

2025-05-27 22:08:03 UTC

- reply

nice and clean interface!

2025-05-26 12:40:42 UTC

- reply

Relevant
#nevent1q…tas4

2025-05-17 22:57:00 UTC

https://cdn.nostrcheck.me/d0f84acab316796b046ff48d1b53f51271f6e4164550d15a7e1dc72faa4898a4.jpeg

2025-05-16 13:18:33 UTC

- reply

#nevent1q…f5fu
Awesome use cases, note to selves

2025-05-16 13:09:49 UTC

- reply

#nevent1q…wge4
Awesome use cases, notes to selves.

2025-05-09 23:37:56 UTC

- reply

or are they visible to anyone

2025-05-09 23:35:43 UTC

What happens to images sent in private chats and stored on blossom servers: Do they get encrypted?

2025-05-04 09:13:46 UTC

Social Media may not be the strength of NOSTR
the ability to integrate social features into any other use case IS a strength if NOSTR

2025-05-04 09:12:28 UTC

- reply

Decentralized, Proof of Work, Fair Launched, and confirmation times in the order of seconds

2025-05-04 09:10:17 UTC

Anyone else out here paying attention to the Kaspa HardFork
https://kas.live

2025-04-30 21:16:50 UTC

I should post more

2025-03-24 14:26:30 UTC

- reply

*april, middle of april xD

2025-03-24 14:26:00 UTC

- reply

That's awesome! Before then, I'll be I Berlin middle of August. Would love to meet any Berliner Nostriches then!!
DM me <3

2025-03-23 18:08:39 UTC

- reply

#nevent1q…wc9x

2025-03-23 13:26:47 UTC

- reply

Awesome idea. We need a LLMs training on NIPs

2025-03-19 19:30:53 UTC

I understand that nostr private keys are generated with https://bips.xyz/340
I'm interested to know what the likelihood of generating the same priv key twice is.
In other words, how many private keys are possible, and how does a generator like the one in nostr-tools generate new keys?

2025-03-19 15:30:15 UTC

- reply

Saving this for Future Reference ;)
How to create a nostr app quickly using [applesauce](https://hzrd149.github.io/applesauce/)
In this guide we are going to build a nostr app that lets users follow and unfollow [fiatjaf](@npub180c…h6w6)
## 1. Setup new project
Start by setting up a new vite app using `pnpm create vite`, then set the name and select `Solid` and `Typescript`
```sh
➜ pnpm create vite
│
◇ Project name:
│ followjaf
│
◇ Select a framework:
│ Solid
│
◇ Select a variant:
│ TypeScript
│
◇ Scaffolding project in ./followjaf...
│
└ Done. Now run:
cd followjaf
pnpm install
pnpm run dev
```
## 2. Adding nostr dependencies
There are a few useful nostr dependencies we are going to need. `nostr-tools` for the types and small methods, and [`rx-nostr`](https://penpenpng.github.io/rx-nostr/) for making relay connections
```sh
pnpm install nostr-tools rx-nostr
```
## 3. Setup rx-nostr
Next we need to setup rxNostr so we can make connections to relays. create a new `src/nostr.ts` file with
```ts
import { createRxNostr, noopVerifier } from "rx-nostr";
export const rxNostr = createRxNostr({
// skip verification here because we are going to verify events at the event store
skipVerify: true,
verifier: noopVerifier,
});
```
## 4. Setup the event store
Now that we have a way to connect to relays, we need a place to store events. We will use the [`EventStore`](https://hzrd149.github.io/applesauce/typedoc/classes/applesauce_core.EventStore.html) class from `applesauce-core` for this. create a new `src/stores.ts` file with
> The event store does not store any events in the browsers local storage or anywhere else. It's in-memory only and provides a model for the UI
```ts
import { EventStore } from "applesauce-core";
import { verifyEvent } from "nostr-tools";
export const eventStore = new EventStore();
// verify the events when they are added to the store
eventStore.verifyEvent = verifyEvent;
```
## 5. Create the query store
The event store is where we store all the events, but we need a way for the UI to query them. We can use the [`QueryStore`](https://hzrd149.github.io/applesauce/typedoc/classes/applesauce_core.QueryStore.html) class from `applesauce-core` for this.
Create a query store in `src/stores.ts`
```ts
import { QueryStore } from "applesauce-core";
// ...
// the query store needs the event store to subscribe to it
export const queryStore = new QueryStore(eventStore);
```
## 6. Setup the profile loader
Next we need a way to fetch user profiles. We are going to use the [`ReplaceableLoader`](https://hzrd149.github.io/applesauce/overview/loaders.html#replaceable-loader) class from [`applesauce-loaders`](https://www.npmjs.com/package/applesauce-loaders) for this.
> `applesauce-loaders` is a package that contains a few loader classes that can be used to fetch different types of data from relays.
First install the package
```sh
pnpm install applesauce-loaders
```
Then create a `src/loaders.ts` file with
```ts
import { ReplaceableLoader } from "applesauce-loaders";
import { rxNostr } from "./nostr";
import { eventStore } from "./stores";
export const replaceableLoader = new ReplaceableLoader(rxNostr);
// Start the loader and send any events to the event store
replaceableLoader.subscribe((packet) => {
eventStore.add(packet.event, packet.from);
});
```
## 7. Fetch fiatjaf's profile
Now that we have a way to store events, and a loader to help with fetching them, we should update the `src/App.tsx` component to fetch the profile.
We can do this by calling the `next` method on the loader and passing a `pubkey`, `kind` and `relays` to it
```tsx
function App() {
// ...
onMount(() => {
// fetch fiatjaf's profile on load
replaceableLoader.next({
pubkey: "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
kind: 0,
relays: ["wss://pyramid.fiatjaf.com/"],
});
});
// ...
}
```
## 8. Display the profile
Now that we have a way to fetch the profile, we need to display it in the UI.
We can do this by using the [`ProfileQuery`](https://hzrd149.github.io/applesauce/typedoc/functions/applesauce_core.Queries.ProfileQuery.html) which gives us a stream of updates to a pubkey's profile.
Create the profile using `queryStore.createQuery` and pass in the `ProfileQuery` and the pubkey.
```tsx
const fiatjaf = queryStore.createQuery(
ProfileQuery,
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
);
```
But this just gives us an [observable](https://rxjs.dev/guide/observable), we need to subscribe to it to get the profile.
Luckily SolidJS profiles a simple [`from`](https://docs.solidjs.com/reference/reactive-utilities/from) method to subscribe to any observable.
> To make things reactive SolidJS uses accessors, so to get the profile we need to call `fiatjaf()`
```tsx
function App() {
// ...
// Subscribe to fiatjaf's profile from the query store
const fiatjaf = from(
queryStore.createQuery(ProfileQuery, "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d")
);
return (
<>
{/* replace the vite and solid logos with the profile picture */}
<div>
<img src={fiatjaf()?.picture} class="logo" />
</div>
<h1>{fiatjaf()?.name}</h1>
{/* ... */}
</>
);
}
```
## 9. Letting the user signin
Now we should let the user signin to the app. We can do this by creating a [`AccountManager`](https://hzrd149.github.io/applesauce/accounts/manager.html) class from `applesauce-accounts`
First we need to install the packages
```sh
pnpm install applesauce-accounts applesauce-signers
```
Then create a new `src/accounts.ts` file with
```ts
import { AccountManager } from "applesauce-accounts";
import { registerCommonAccountTypes } from "applesauce-accounts/accounts";
// create an account manager instance
export const accounts = new AccountManager();
// Adds the common account types to the manager
registerCommonAccountTypes(accounts);
```
Next lets presume the user has a NIP-07 browser extension installed and add a signin button.
```tsx
function App() {
const signin = async () => {
// do nothing if the user is already signed in
if (accounts.active) return;
// create a new nip-07 signer and try to get the pubkey
const signer = new ExtensionSigner();
const pubkey = await signer.getPublicKey();
// create a new extension account, add it, and make it the active account
const account = new ExtensionAccount(pubkey, signer);
accounts.addAccount(account);
accounts.setActive(account);
};
return (
<>
{/* ... */}
<div class="card">
<p>Are you following the fiatjaf? the creator of "The nostr"</p>
<button onClick={signin}>Check</button>
</div>
</>
);
}
```
Now when the user clicks the button the app will ask for the users pubkey, then do nothing... but it's a start.
> We are not persisting the accounts, so when the page reloads the user will NOT be signed in. you can learn about persisting the accounts in the [docs](https://hzrd149.github.io/applesauce/accounts/manager.html#persisting-accounts)
## 10. Showing the signed-in state
We should show some indication to the user that they are signed in. We can do this by modifying the signin button if the user is signed in and giving them a way to sign-out
```tsx
function App() {
// subscribe to the currently active account (make sure to use the account$ observable)
const account = from(accounts.active$);
// ...
const signout = () => {
// do nothing if the user is not signed in
if (!accounts.active) return;
// signout the user
const account = accounts.active;
accounts.removeAccount(account);
accounts.clearActive();
};
return (
<>
{/* ... */}
<div class="card">
<p>Are you following the fiatjaf? ( creator of "The nostr" )</p>
{account() === undefined ? <button onClick={signin}>Check</button> : <button onClick={signout}>Signout</button>}
</div>
</>
);
}
```
## 11. Fetching the user's profile
Now that we have a way to sign in and out of the app, we should fetch the user's profile when they sign in.
```tsx
function App() {
// ...
// fetch the user's profile when they sign in
createEffect(async () => {
const active = account();
if (active) {
// get the user's relays or fallback to some default relays
const usersRelays = await active.getRelays?.();
const relays = usersRelays ? Object.keys(usersRelays) : ["wss://relay.damus.io", "wss://nos.lol"];
// tell the loader to fetch the users profile event
replaceableLoader.next({
pubkey: active.pubkey,
kind: 0,
relays,
});
// tell the loader to fetch the users contacts
replaceableLoader.next({
pubkey: active.pubkey,
kind: 3,
relays,
});
// tell the loader to fetch the users mailboxes
replaceableLoader.next({
pubkey: active.pubkey,
kind: 10002,
relays,
});
}
});
// ...
}
```
Next we need to subscribe to the users profile, to do this we can use some rxjs operators to chain the observables together.
```tsx
import { Match, Switch } from "solid-js";
import { of, switchMap } from "rxjs";
function App() {
// ...
// subscribe to the active account, then subscribe to the users profile or undefined
const profile = from(
accounts.active$.pipe(
switchMap((account) => (account ? queryStore.createQuery(ProfileQuery, account!.pubkey) : of(undefined)))
)
);
// ...
return (
<>
{/* ... */}
<div class="card">
<Switch>
<Match when={account() && !profile()}>
<p>Loading profile...</p>
</Match>
<Match when={profile()}>
<p style="font-size: 1.2rem; font-weight: bold;">Welcome {profile()?.name}</p>
</Match>
</Switch>
{/* ... */}
</div>
</>
);
}
```
## 12. Showing if the user is following fiatjaf
Now that the app is fetching the users profile and contacts we should show if the user is following fiatjaf.
```tsx
function App() {
// ...
// subscribe to the active account, then subscribe to the users contacts or undefined
const contacts = from(
accounts.active$.pipe(
switchMap((account) => (account ? queryStore.createQuery(UserContactsQuery, account!.pubkey) : of(undefined)))
)
);
const isFollowing = createMemo(() => {
return contacts()?.some((c) => c.pubkey === "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d");
});
// ...
return (
<>
{/* ... */}
<div class="card">
{/* ... */}
<Switch
fallback={
<p style="font-size: 1.2rem;">
Sign in to check if you are a follower of the fiatjaf ( creator of "The nostr" )
</p>
}
>
<Match when={contacts() && isFollowing() === undefined}>
<p>checking...</p>
</Match>
<Match when={contacts() && isFollowing() === true}>
<p style="color: green; font-weight: bold; font-size: 2rem;">
Congratulations! You are a follower of the fiatjaf
</p>
</Match>
<Match when={contacts() && isFollowing() === false}>
<p style="color: red; font-weight: bold; font-size: 2rem;">
Why don't you follow the fiatjaf? do you even like nostr?
</p>
</Match>
</Switch>
{/* ... */}
</div>
</>
);
}
```
## 13. Adding the follow button
Now that we have a way to check if the user is following fiatjaf, we should add a button to follow him. We can do this with [Actions](https://hzrd149.github.io/applesauce/overview/actions.html) which are pre-built methods to modify nostr events for a user.
First we need to install the `applesauce-actions` and `applesauce-factory` package
```sh
pnpm install applesauce-actions applesauce-factory
```
Then create a `src/actions.ts` file with
```ts
import { EventFactory } from "applesauce-factory";
import { ActionHub } from "applesauce-actions";
import { eventStore } from "./stores";
import { accounts } from "./accounts";
// The event factory is used to build and modify nostr events
export const factory = new EventFactory({
// accounts.signer is a NIP-07 signer that signs with the currently active account
signer: accounts.signer,
});
// The action hub is used to run Actions against the event store
export const actions = new ActionHub(eventStore, factory);
```
Then create a `toggleFollow` method that will add or remove fiatjaf from the users contacts.
> We are using the `exec` method to run the action, and the [`forEach`](https://rxjs.dev/api/index/class/Observable#foreach) method from RxJS allows us to await for all the events to be published
```tsx
function App() {
// ...
const toggleFollow = async () => {
// send any created events to rxNostr and the event store
const publish = (event: NostrEvent) => {
eventStore.add(event);
rxNostr.send(event);
};
if (isFollowing()) {
await actions
.exec(UnfollowUser, "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d")
.forEach(publish);
} else {
await actions
.exec(
FollowUser,
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"wss://pyramid.fiatjaf.com/"
)
.forEach(publish);
}
};
// ...
}
```
## 14. Adding outbox support
The app looks like it works now but if the user reloads the page they will still see an the old version of their contacts list. we need to make sure rxNostr is publishing the events to the users outbox relays.
To do this we can subscribe to the signed in users mailboxes using the query store in `src/nostr.ts`
```ts
import { MailboxesQuery } from "applesauce-core/queries";
import { accounts } from "./accounts";
import { of, switchMap } from "rxjs";
import { queryStore } from "./stores";
// ...
// subscribe to the active account, then subscribe to the users mailboxes and update rxNostr
accounts.active$
.pipe(switchMap((account) => (account ? queryStore.createQuery(MailboxesQuery, account.pubkey) : of(undefined))))
.subscribe((mailboxes) => {
if (mailboxes) rxNostr.setDefaultRelays(mailboxes.outboxes);
else rxNostr.setDefaultRelays([]);
});
```
And that's it! we have a working nostr app that lets users follow and unfollow fiatjaf.

2025-03-18 21:37:12 UTC

- reply

word

2025-03-17 09:13:18 UTC

- reply

Great to be there!

2025-03-05 16:55:41 UTC

Does NOSTR already have a standard to sign an event with multiple pubkeys?
say you have a post that is actually a collaboration between two authors
it's in their interest to reach out to both of their followers with the same event
rather than tagging, commenting, replying, they may like to BOTH sign the event, and for BOTH of their user bases to see the same event

2025-02-24 22:22:39 UTC

- reply

Awesome stuff 👏

2025-02-24 14:42:29 UTC

- reply

I would counter, optimistically, that NOSTR allows anyone to have any number of identities. One being hacked does not mean that all are lost, more can be made, and old content remains accessible!

2025-02-24 10:16:29 UTC

- reply

well, how exciting that you're there to see it! It always starts somewhere ;)

2025-02-24 07:42:42 UTC

- reply

Have you read the Tao of Physics?

2025-02-24 07:40:59 UTC

- reply

Cool! Hello 👋 How's bitcoin adoption looking in Tanzania?

2025-02-10 11:27:17 UTC

- reply

it's worth studying their successes

2025-02-10 11:27:02 UTC

- reply

they are many steps ahead

2025-02-10 11:13:00 UTC

Did you know
In India, people have been implementing Open Data protocols on massive scale?
Becknprotocol.io
they have open ride sharing for example
nammayatri.in

2025-01-24 23:46:14 UTC

- reply

Yes, I am interested! DM:)

2025-01-24 09:47:34 UTC

- reply

Nice! is there a link for this chat, or what Relays is it on?

2025-01-23 19:37:04 UTC

- reply

and it's open source!!! Beasts <3

2025-01-23 19:35:51 UTC

- reply

Ohhh amazing, another progressive web app 👏
Love the minimalist look and feel

2025-01-23 19:22:13 UTC

- reply

This sounds very interesting!
The website references "bitcoin timechain technology"
This is a bit generic and obscure
Could you help us understand what's going on behind the hood?
How are BTC blockchain timestamps used to create dates of creation for files that are not stored on chain?
Thank you!

2025-01-21 15:05:08 UTC

- reply

He's got more than enough to commission some bodyguards to keep us bullies at least 10 feet distanced xD

2025-01-21 15:02:04 UTC

- reply

And they are both progressive web apps! Great stuff. Planning to go that direction too

2025-01-16 09:39:29 UTC

- reply

why no go tu gulag
shame

2025-01-16 09:38:46 UTC

- reply

Wow, so you can't tell ppl they must go to gulag? is such necessary to tell sometimes,
To gulag, you must, go

2025-01-16 09:34:00 UTC

- reply

Open AI can fight the lawsuits, but I can't

2025-01-08 13:28:33 UTC

- reply

@nprofile…t3vy

2025-01-05 17:06:07 UTC

- reply

Thanks to your note, now I am too <3

2025-01-02 10:19:32 UTC

@nprofile…4ph5 @nprofile…weu7
I fell in love with the idea of SEC-meetings, and would love to attend.
Any plans for the future SEC-Xs?
Thank you!

2025-01-02 09:23:38 UTC

- reply

This sounds beautiful.
How do you plan to account for multiple versions of similar or the same headers?
I imagine that you are not aiming for a Wikipedia like approach which achieves consensus on the content in the background.
Thank you for your work!

2024-12-31 15:03:40 UTC

- reply

bookmark

2024-12-28 15:54:13 UTC

- reply

A zap poll? Cool!

2024-12-27 07:43:47 UTC

- reply

You are a helpful assistant
Yes I am

2024-12-22 19:47:16 UTC

- reply

Thoughts in the dynamic creation of a new form of digital tools. May they enhance our humanity?
#nevent1q…428c

2024-12-17 17:29:28 UTC

lnbc1pnkrdx3pp5gec98adnf4q5x8w6dvzyfxk4ljyzxw99q7f7hxylf4xqh62z398sdp82pshjgr5dusyymrfde4jq4mpd3kx2apq24ek2uscqzpuxqr8pqsp5xhedg6ve34xwx234v3npjz6lq5640y4ehrtsg0tcjnhh7rj4fnss9p4gqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqpqysgqf2sp6u6dr8vnjcdsx9dspf3pya8kpxzjwacmenhr0gm92ftxu39hesgcex8md72azq89c753244ksc95saq3crhxteapnm94z2wkjfqqweykqx

2024-11-27 10:04:53 UTC

- reply

85 years, just about a lifetime

2024-11-25 10:12:53 UTC

#asknostr
I've started putting substantial work into a new open source nostr project.
The end game is to create local sharing communities!
I'm developing mobile first with react-native, using nostr-tools and nostr-ndk
What are good places to share and receive feedback on nostr related questions?
I'm sure nostr itself is a good place to start :) any specific Relays?

2024-11-25 10:06:05 UTC

- reply

Big quality of life success!!

2024-11-20 22:03:37 UTC

- reply

it's too odd, can't be simulation xD

2024-11-19 16:54:53 UTC

- reply

Very cool!
Great to see innovative ways to engage with content.
Flipping around the relationship
Users can get paid to listen,
attention is value
#nevent1q…zn43

2024-11-11 10:36:09 UTC

- reply

it might be more like giving someone your sperm,
to sign things with

2024-10-19 12:19:04 UTC

- reply

this is very interesting I'd love to know more about it! Also keen on doing academic work related to Nostr.

2024-10-15 19:15:38 UTC

- reply

this sounds cool

2024-10-09 17:50:20 UTC

- reply

I would agree it is quite nuanced and reasonable

2024-10-06 18:24:16 UTC

- reply

but hey, at least it's censorship resistant 😆

2024-10-06 18:20:50 UTC

- reply

it's definitely getting increasingly less interesting to read the same daily digest of nostr enthusiasm ...
the digital innards of a ruminating cow

2024-10-06 18:15:31 UTC

- reply

we could see bitcoin as measuring the experiment

2024-10-05 15:19:07 UTC

- reply

besides social media like experiences,
I imagine honest and efficient use cases of relays that are location dependent.
e.g. "airbnb-like" or marketplace listings stored on relays in the city of interest

2024-10-05 15:14:07 UTC

- reply

I don't see why that would be shitcoinery, or better, anti-ethos.
but open to change my mind!

2024-10-04 14:51:35 UTC

- reply

I found the link in the event added a weird "[Code" suffix, from the [Code of Canon] title ...

2024-10-04 14:48:49 UTC

- reply

I see, the wikifreedia link works. I saw your event on Amethyst.

2024-10-03 07:19:11 UTC

- reply

I get a 404 page not found on the Vatican link

2024-09-25 16:13:35 UTC

- reply

silly question, what's the purpose of Nostur? What do you guys use it for?
Love your memes btw <3

2024-09-25 07:33:39 UTC

- reply

might it have been open by the time you got there, taking travel time into account?
indeed, any such change is likely intentional...

2024-09-22 15:37:29 UTC

- reply

A great project! Thank you for your work.
#nevent1q…3vx8

2024-09-19 12:04:34 UTC

- reply

definitely, anonymity in voting is essential, so it needs to be figured out how we can create such anonymous votes. Even in much simpler applications polls are very useful and could easily be integrated into NOSTR. I think thed be particularly interesting for the interoperability of the protocol.
Curious you mention Peer review because I'm in academia now and actually think it would be a really cool use case for nostr: to set up a peer review system.
A required feature would be "reputation", and I think this is something we haven't quite cracked yet. But please correct me if I'm wrong.

2024-09-19 11:21:49 UTC

- reply

I like the way you think, and it sounds like you've had some substantial experiences.
I kind if feel like many of the tools from those ecosystems, like NFTs and DAOs are solutions in search of a problem. They have no clear use cases yet. The proposed use cases rest on invalid assumptions about the ways that we govern our social systems.
I'd be interested to hear more about your perspective.

2024-09-19 10:58:41 UTC

- reply

I'll have to look into his vision, but I think NOSTR is very well suited to democrating voting. It can even be made permissioned or not accordingly to the use case.

2024-09-19 10:56:45 UTC

- reply

Voting however is super useful, and essential if we want to create democratic digital communities. So we should figure out how we can bridge these features to the NOSTR ecosystem. A strength of NOSTR is that it can not be bought. What do you think?

2024-09-18 12:56:55 UTC

- reply

bountiful pills of purple 💜

2024-09-18 11:23:20 UTC

- reply

good luck, I'll keep an eye out

2024-09-17 13:51:48 UTC

- reply

I have started engaging with the academic community on NOSTR related themes. A slow steady grind, but I think there is great potential and synergy.

2024-09-17 13:48:24 UTC

- reply

I'd be interested to read your posts. Where can, or will I, find them?

2024-09-17 13:47:44 UTC

- reply

nice to meet you as well, glad to get some engagement

2024-09-17 13:46:54 UTC

- reply

nice to meet you! I'm a PhD student in my final year. I've been focusing on Game Theory and Reinforcement Learning.

2024-09-14 08:41:15 UTC

I'm looking to connect with fellow researchers, academics, PhD students and Post Grads on NOSTR.
Don't you think this would a great ecosystem to grow a scientific network?
Do know anybody that fits the bill?

2024-09-08 14:10:30 UTC

Hey Nostriches,
I'm familiar with browser extensions, and the notion of am nsec bunker, buy in terms or workflow,
what are the best ways you've found to manage your keys?
and on the phone?
multiple accounts?

2024-09-04 13:47:41 UTC

- reply

of course, how could I miss it xD

2024-09-04 13:03:25 UTC

- reply

the piece of building?

2024-09-04 13:02:45 UTC

- reply

cool ;)
what would you say the ninja is holding.
A tile?
A letter?

2024-08-19 15:12:22 UTC

What's the plan: How will Relays be incentivized to keep running?
this seems a legitimate challenge.
bitcoin incentivizes miners clearly.
how will we incentivise the beating heart of nostr infrastructure?

2024-08-15 21:49:05 UTC

- reply

How would you describe the difference between NOSTR and Mastodon? Or the fediverse, as you called it.

2024-08-15 09:12:06 UTC

- reply

Do we have a good understanding of the difference and efficiency of using social graphs as a filters? Otherwise, I'd be willing to dedicate time to research, proof and demonstration.

2024-08-14 12:36:17 UTC

- reply

blew my mind, awesome visualization

2024-08-08 08:33:12 UTC

- reply

ciao belli

2024-08-08 08:31:02 UTC

- reply

exciting stuff! Looking forward to seeing couchsurfing on NOSTR 🌊🛋

2024-08-05 18:46:43 UTC

- reply

Philip K. Dick, Do androids dream of electric sleep