pedja

i'm sorry for late reply. i was going through body detoxification.
only primal clients should use wss://cache2.primal.net/v1 for number of reasons. your local cache instance is available at ws://127.0.0.1:8801 (this is default address on which server is listening which can be changed). if you want to expose the cache instance to public you should use nginx or some other webserver which can do reverse proxy and provides TLS for security.

2023-09-21 02:04:32 CEST

- reply

congratulations! clients of primal cache instance are using websocket connections to send API request messages and get back API response messages. available API requests are defined in file called app.jl but i would suggest, beside looking at that code, you take a look at live communication between primal webapp (at primal.net) and primal server. in your web browser you should be able to open devtools/network tab, and select websocket connection to wss://cache2.primal.net/v1and look at the messages that are being sent and received. there you will be able to see common structure of each API request/response that the webapp is using which is almost everything currently available from our cache instance. webapp usually is the first to use new features and then i tell the same suggestion to our mobile app developers when i want to explain new API requests. ofc sometimes i have to additionally clarify some aspects of new API requests since nobody knows all the details which are sometimes important to mention. that's it. and feel free to ask again.

2023-09-09 18:49:33 CEST

#artist learning to make #art #painting
boosted by #rakija #artstr
https://m.primal.net/HKvy.jpg

2023-09-05 20:41:32 CEST

- reply

this is the oldest result i get
https://m.primal.net/HKgn.png

2023-09-05 20:39:53 CEST

- reply

i see that note in results when i search for those terms
https://primal.net/search/%23maths%20OR%20%23math%20OR%20%23Mathematics%20OR%20%23CategoryTheory%20OR%20%23Logic%20OR%20%23RDF%20OR%20%23SemWeb%20OR%20%23scala%20OR%20%23Agda%20OR%20%23FP%20OR%20%23SemanticWeb%20OR%20%23topos%20OR%20%23ScalaJS%20OR%20%23Java%20OR%20%23www%20OR%20%23W3C%20OR%20%23WebScience%20OR%20%23hyperApp%20OR%20%23Cognitive%20OR%20%23CognitiveScience%20OR%20%23Psychology

2023-09-04 12:03:48 CEST

- reply

our search engine supports disjunction (OR) operator in query string. you can use something like this to search for multiple terms or tags:
#scala OR #math
OR has to be upper-case. here is the link to search example:
https://primal.net/search/%23scala%20OR%20%23math

2023-08-12 00:55:48 CEST

Artificial General Intelligence — A gentle introduction
https://cis.temple.edu/~pwang/AGI-Intro.html

2023-08-09 03:30:27 CEST

- reply

well, it's fun experiment for sure 🙂 but i can already see what would be next step, probably personal caching service (for notes from users i personally follow) and some sort of nostr client, running on phone locally. to be able to browse my feed and other stuff.
OTOH lets imagine the future where everybody has local personal relay. i would connect to relays of people in my contact list, people i follow. and that's great for smaller social circles. but not so much for someone who has 100K+ followers (or even less than that). because his phone would melt to service queries from his followers. i think we need a solution where we get notes from highly popular users via our social graph neighbourhood. if my app knows that you are also follower of that highly popular user, i can query your self-hosted caching service, running on your phone, integrated into app or more modular like on android, instead of going directly to his relay. his relay will need to limit how much and to whom his notes are initially seeded. starts to look like bittorrent..

2023-08-08 23:03:07 CEST

- reply

great idea. in the meanwhile i'm running my personal nostr_rs_relay instance accessible as #tor hidden service on my #android phone in #nix-on-droid. @npub12vk…pugg webapp works in tor browser and with small about:config tweak can connect to it.

2023-08-05 19:56:23 CEST

- reply

we are contemplating support for all major geographical regions.

2023-08-05 05:49:46 CEST

https://m.primal.net/HHpE.png

2023-08-03 12:30:09 CEST

- reply

number of cores depends on how many users you want to service at the same time and if you want to do media caching. try it with at least 4 cores. as for memory, with 16GB RAM it should work fine, 32GB is what i usually suggest as it will have more opportunity to use disk I/O cache and since you probably have some other processes running on the server. for storage, after 6 months and 125mil events, our database is around 330GB. but i could prune older events and reduce storage requirements if you dont want to archive everything forever.

2023-07-27 19:13:49 CEST

- reply

yeah!

2023-07-20 04:30:09 CEST

- reply

woohoo!

2023-07-20 04:14:23 CEST

- reply

can you try it now? it should be fixed.

2023-07-20 00:27:06 CEST

- reply

can you send me the link that you got after uploading the file? maybe i can figure out what's happening.

2023-07-19 22:53:26 CEST

- reply

perfect opportunity for blues.. "walking hard, to fiat mines.."
🎶

2023-07-19 22:34:06 CEST

- reply

notes and other stuff will be transmitted by various means by then.

2023-07-19 21:38:24 CEST

- reply

this list of relays is the most interesting lately:
https://github.com/PrimalHQ/primal-caching-service/blob/main/relays-mined-from-contact-lists.txt
periodically i run a script to mine relays from all collected contact list events.
https://github.com/PrimalHQ/primal-server/blob/main/collect-relays-from-contact-lists.jl

2023-07-18 00:22:03 CEST

- reply

you probably want to search for notes where either of these two hashtags is mentioned.
to do that you can use search query like this:
#nostrrelay OR #nostrdev
here is the link to it:
https://primal.net/search/%23nostrrelay%20OR%20%23nostrdev

2023-07-18 00:05:04 CEST

- reply

@npub1j7u…8lvw just told me that upload when writing posts is not supported yet. but it's planned feature for sure. stay tuned!

2023-07-17 23:06:47 CEST

- reply

hi, is it still not working? if so, i would like to reproduce the issue to fix it. can you send me the file you are trying to upload? or link to it if you already uploaded it to some other web host. maybe it's something about the format of the file.

2023-07-17 07:30:00 CEST

- reply

p2p like communication over nostr could be implemented using ephemeral events (NIP-16, kinds 20000-29999). for file sharing it would be actually more like peer to multiple other peers, and since it's going through relay, pRp (peer-relay-peers). bandwith cost could be covered by zapping relay operator. single file transfer could be executed over multiple relays.
there is a reason why internet became centralized. the main cause was inability to assign IP address to every user which prevented direct communication between users and created need for big tech intermediaries. #nostr is a step in the right direction, but it's not complete solution.
if relay operator doesn't want to allow file sharing (s)he can block certain event kinds. although it would be excellent test of survivability of the protocol and nostr network in the long run.
CC: @npub1qqq…n47m

2023-07-17 04:21:32 CEST

- reply

very cool proposal. structured approach to code management is the future. like what we can see with unison language.
there are some worries about sandboxing and isolation but that's something that can be improved later on after initial experiments.
i would also prefer capability to distribute wasm module which is interpreter for other higher level language that will be able to execute code from events containing that higher level language. but the composition is the key even if you use multiple different languages for different aspects the system.
expressive power of javascript/typescript type of language is very limiting when compared to, for example, prolog where the same code can be re-used in many more ways which is valuable if you want far and wide reuse. meta-interpreters and program synthesis are easy in languages like prolog.
also as it looks rn it's very web tech specific (DOM elements etc) but what's beautiful is that rendering is optional. execution environment doesn't have to render anything just execute code-carrying events enough for various other purposes.
if all tools to develop this core-carrying events are also published and distributed via nostr in the same form (after initial boostrapping process) this will enable more axiomatic and broad self-improvement process to emerge with ports to different execution environments and rapid exploration of new application domains.
can't wait to see where this goes..

2023-07-13 13:53:37 CEST

@npub12vk…pugg open-sourced software tech stack for Nostr (server, web app, iOS app, Android app). Find links to repos here: https://primal.net/downloads

2023-07-11 23:36:35 CEST

- reply

nixos ftw 💪

2023-05-31 02:56:08 CEST

- reply

We are fortunate that when compared to alternatives it's relatively easy to start implementing nostr protocol. It's great to have mini-specs (NIPs) which are explaining the most important aspects of certain topic. And you can implement subset of them and still get something useful. But we are still using primitive tools to do this development, as Bret's video shows.
Two weeks ago I started to watch again Alan Kay's presentations. He also doesn't like APIs. It's too rigid for the scale he is interested in like we are too. You need some sort of auto-negotiation between communicating parties which are complex and getting more and more autonomous (not just automated as we humans are making them rn). His thinking is inspired by biological systems. Encapsulation of internal state of the cell (we're already ok here). Its interaction with environment (message passing, good too). DNK - so far I didn't see any executable code (like wasm? or even better something higher level) transported by nostr events (somebody pls correct me). Simulation within cell of some subset of external environment (could be other cells or more complex structures). And use of simulation results for reasoning and adaptation. I don't see evidence for last two.
Microapps idea is fine but is there something better? He was thinking a lot about the ways to empower users to do custom programing. I think that's important for the future. As long as we have this division between developers and users, it's asymmetry which could impact decentralisation. Things could be better in the long run. Store for microapps or repository of composable bloat-free building blocks with cryptographically proven ancestry stored on relays accessed from mega app which is combination of OS and IDE?
Protocols are like APIs. Can we grow them automatically or at least more efficiently, for now with humans in the loop guiding their development..

2023-05-12 23:58:20 CEST

- reply

haha bas shou :) otoh naj glumica svih vremena <3