jonstaab

5 ms·

31.
by jonstaab 8mo ago
In contrast with Roomy, Discord does provide for non-public community spaces. https://itsfoss.com/roomy-discord-alternative/
32.
Flotilla: A Discord Alternative Built on Nostr(flotilla.social)
4 points by jonstaab 8mo ago|1 comments
33.
Slopcraft and the LLM Society(habla.news)
7 points by jonstaab 8mo ago|0 comments
34.
Digital Tools for Conviviality(habla.news)
2 points by jonstaab 8mo ago|0 comments
35.
by jonstaab 11mo ago
> With our unique financial rewards model, scale matters. The more justice you unlock, the more monetary compensation you receive. > In fact, we pledge to distribute to tippers $200 million out of every $1 billion we collect. What? Do
36.
by jonstaab 1y ago
Couldn't agree more with this. Another way to describe this kind of honesty is as "integrity", or in other words the coherence of your inner and outer lives. Hypocrites are always in a contest against themselves, which is a k
37.
by jonstaab 1y ago
It was (and still is) deployed in a number of places, so it's a valid criticism in that context. That said, it's mostly dunk.
38.
by jonstaab 1y ago
Going back to the site, I see what you mean. Very fair criticism. The site appeals to a bunch of implicit ideals without defining its terms.
39.
by jonstaab 1y ago
My point is that question is sort of a category error. It's like asking what type of business the internet is for, or what the use case of smart phones is. Here are a few things built on nostr, with specific use cases: primal.net is a
40.
by jonstaab 1y ago
Nostr is essentially a compromise between p2p and traditional web architectures. It cuts with the grain of the internet by using web servers, while reducing the dependence users have on servers by using keys for identity and digital signatu
41.
by jonstaab 1y ago
The criticisms are either implementation dependent (not checking signatures, which defeats the entire purpose of the protocol), or based on a very early proof of concept encryption scheme which has since been superseded (by NIP 44, which wa
42.
by jonstaab 1y ago
The cryptography was thrown together in the very early days as a proof of concept, that reached some level of adoption because of how nostr suddenly grew at the end of 2022. The community has since largely switched to a new standard (NIP 44
43.
by jonstaab 1y ago
It's very unlike mastodon in that server operators have minimal control over user identities and content. Spam control is still a work in progress, but has come a long way through web of trust and more responsible relay operation. I in
44.
by jonstaab 1y ago
Very thoughtful points. One thing about nostr is that it does tend to balkanize due to the technical architecture, allowing for different groups of people to use it in different ways (different relay policies, client features, filtering, et
45.
by jonstaab 1y ago
Alternatively, you could use nostr, have your users pay for the database, and get access to rich content types, an existing social graph, and application interoperability.
46.
Keys and Sovereign Identity(habla.news)
2 points by jonstaab 2y ago|0 comments
47.
by jonstaab 2y ago
Not to mention that it's interoperable with other software, like https://chachi.chat
48.
by jonstaab 2y ago
OP and developer here, Flotilla's not quite primetime-ready, but I saw the Revolt post and decided to proffer my own alternative. Happy to answer any questions.
49.
Flotilla: Nostr-based Open Source alternative to Discord(flotilla.social)
5 points by jonstaab 2y ago|3 comments
50.
by jonstaab 2y ago
I'm also building a FOSS Discord alternative, but this one's based on nostr: https://flotilla.social
51.
by jonstaab 2y ago
It definitely has bearing on the indexeddb complaint. If I was sending proxies over fetch, I would never have noticed. But I would expect the callbacks/props thing to be pretty annoying for any app that uses portals.
52.
by jonstaab 2y ago
I wish I had stuck with clojurescript. I found clojure in 2013 or so but could never justify putting it in production. But that would have been a good 12 years of frontend development bliss. The clojure team has the right mindset.
53.
by jonstaab 2y ago
Yeah, I opted not to talk about that in my post, but runes do tend to infect all of your code if you use them as intended.
54.
by jonstaab 2y ago
This seems promising. I agree observables are probably the right way forward, although I haven't used them much beyond svelte stores. Observables via hooks might be a good way to eliminate the bad parts of hooks too.
55.
by jonstaab 2y ago
Funny, because I love svelte stores and use them as much as I can over the compiler magic. But that's probably because I've never taken the time to learn observables properly.
56.
by jonstaab 2y ago
Oops, you're right, here's the other issue: https://github.com/sveltejs/svelte/issues/15325 That should shed more light on my problem, which is not just due to proxies, but is also a result of props
57.
by jonstaab 2y ago
This is something I didn't cover in my post, but I feel that's a bug, not a feature. Using runes instead of stores (which did the same thing in svelte 4) implicates the svelte compiler in every source file. This is ok if you'
58.
Svelte 5 is not JavaScript(hodlbod.npub.pro)
194 points by jonstaab 2y ago|202 comments
59.
by jonstaab 2y ago
consider the nostr protocol
60.
by jonstaab 2y ago
My point is not the current size, it's the eventual size if bluesky succeeds. Facebook ingests 100TB/day. Self-hosting a bluesky relay isn't (won't be) a thing.

More ›