So, how are our australians Nostriches doing on shilling Nostr to the youths over there now that the new law is in effect? I was on some australian podcast last week, but it wont be till the end of jan till it comes out so🤷‍♂️

But but but, vitalk says we should not be mean towards to EU 🥺👉👈

I can share if i log in...but where/how can i log in? 🤔

Even if your understanding of how it is supposed to work is correct, you still trust the fact that that is actually how it works. I.e. you already trust the operator a priory the calculation.

The - tag should prevent trivial republishing; the rest is just good old pirating which will always exist. Personally i think the zapbox relay model would work best: follow = get free feed; Pay = instantly just get the free+paid content aswell in the feed. Most frictionless, client independent experience for the user. Publishers need to make sure they use the right relays that will comply with their chosen witholding scheme/metrics.

On a different note: relays are gatekeepers, the point is that you are flexible among the gatekeepers you use, including your own.

Well, im just wondering why for me the thing claims dec2 is day 2, whilst it indeed should be day 3🧐

Fyi, for me its 'day 2', and you have been consistently spoiling the calender since the start

1: maybe it was indeed only made for me, maybe. 2: maybe vnak exists because of me in the first place, maybe. 3: i have probably installed various linux distros a bazillion times on various systems, and every time i came to the conclusion i'd rather use the OS i only installed a hand full of times, mostly only once per system. Though Windows is getting terrible in a whole bunch of ways for a while now, it never gave me shit about python versions and allows me to play broodwar without any fuzz, so there is that.

The explicit investment thesis behind the mayor platforms was that by subsidizing its growth, it would undermine competition and eventually result in the capture of network-effect, at which point the masses of users would not have a viable alternative and could be fleeced for the return on investment. "Enshittification" was baked in from the start, and to a large extend the investment thesis was correct. Nevertheless its evil. I have no other word, its deliberate baiting into hazard, and they spend a lot of time and effort into making the bait outmost enticing, conciously. It was the plan to capture us; they have captured us; people finaly seem to feel they have been captured. Time to free ourselves. Nostr

Sinterklaas in Luxemburg

These are fighting words

I think we have identified why Nostr sucks; its not Starcraft

I am not a morning person😠

I know there are other projects in the fitness app domain, but can't recall who was involved or what they were called. Perhaps remembers. Having a brief look at your kinds, is POWR also an app of yours? Because it appears to generate the 1301-events a bit differently. See: https://nostr.com/ It just dumps a bunch of values under ''exercise'', whilst what i gather from that spec thats not supposed to be how it works no? https://github.com/RUNSTR-LLC/RUNSTR/blob/main/docs/KIND_1301_SPEC.md

In that case, get a browser extension, although if you have an android phone laying around amber is still great regardless. Have a look at jumble in the browser. As far as desktop clients go, i kinda gave up because i did not really like any of them last i checked. Maybe notedeck (damus) improved in the meantime. Whatever, just check nostrapps.com . Also, when you are using jumble, maybe this little vid helps to wrap your mind around things: Lastly again my question, how did you end up at my profile🧐

Maybe the point of the idea is that we shouldn't 🤔 what could possibly go wrong🙃

This is straight up Nostr pr0n.

What do the wise sages of Nostr think of the following terrible grugbrain idea: What if you create an ncryptsec and just put it in an event and on some relay somewhere. Then you could go to lets say a fresh amber install, fetch that event, decrypt it and just set up your new system while only needing a password. The hash of the password could be included in the same event as the ncryptsec, and then u could use that to query your ncryptsec-event. This allows you to sign the ncryptsec-event with some random throwaway keypair. This way it is not appearent who's ncryptsec is tied to. Other than 'what if the password is too weak' and 'QuAntUm' and 'how do you fix spam': why would this be a bad idea?

No simple curves here friend, all pretence in that direction is a lie, suck it up and bite that bullet, and you will find the curve was never that hard to begin with. Also, , available for browser, iOS and Android. If you are on Android, get zapstore first. https://zapstore.dev/ Once you got zapstore installed, congrats you are now liberated from the google playstore; Then install amber, you will find it in the zapstore, its a signing app, that allows you to put your key in 1 place and then connect with (most of) all other apps; be that on your phone or browser or your toaster or your mom. Just be sure to give everything full permissions (trust me, makes live just easier, you can always revoke permissions anyway). After that you can find yakihonne in the zapstore as well. Thats a decent set-up that should get you going. If you have an iphone...sorry i have no clue how to deal with such a terrible life choice...but you can still install yakihonne 🤷‍♂️. Question, how on earth did you end up on my profile?

why dont you use musig and simplefy the entire thing to just single events (outside of the draft events perhaps). Current flow had a bunch of holes simply because at no point is there actually an atomic mutual action, which would be the case with musig, and it would still allow for an arbitrary number of participants. I.e. leverage the crypto/schnorr https://attestr.app/about

Well, it is not a place, Nostr is more like a method to interact on various places; permissionless in all its glory and horror. If you need any pointers, just ask

Well, it seems you took very little time reflecting. My 2 cents: The transscripts should be seperate events, that reference whatever event it is they are transscribing. This has a couple of benefits; 1: transscripts can be produced after the fact; 2: transscripts can be produced by anyone; 3: transscripts can apply to all sorts of events. It would allow your client to provide transscripts for voice events that appearently did not have any. This way your usecase can leverage stuff that is already out there, and other clients can ignore transscripts if they want to. This set-up will benefit clients that would want to provide a good experience for deaf people for example, that can now addopt this broader transscript standard. All a clients has to do, is also query for transscript events related to the stuff it wants transscripts for.

I understand this part from a convention standpoint but it ultimately does not really matter (tags or content is completely arbitrary at the end of the day). I agree with the people here that there would have been multiple sollutions to this situation, and plenty of room for coordination, that will also allow you to easily filter events that dont include a transcript. They might have come out a bit hostile out of the gate, but understand its mostly dissapointment. Also understand that Nostr only has 1 commons, which is not that of the servers/relays, something other protocols try and fail because its stupid. Nostr's commons is that of the immaterial (loose) coordination on standards. And we don't have a police, and technically you can do whatever you want, but commons only thrife when participants forgo immediate opportunity for the sake of long term accrued benefits. People see you taking immediate opportunity and see the opportunity cost of that action, which explains why they are not happy. I hope you can reflect and can come back to the table at some later moment in time.

Disagree, a follow does not imply association, i can follow someone or something for a wide variety of reasons, all the way up to it being an accident and therefor completely meaningless (because someone was included in a followpack for example). Two mortal enemies might 'follow' eachother, but that in no way means they associate with eachother, on the contrary. Next mutual follows are asychronous, whereas establishing a 'friend'ship is a synchronous occurance. Lastly the point of musig2 is efficiency compressing it into a single event, instead of two. So the difference is that a 'friend'ship is one deliberate concious action between two (or more, how cool is that, gotta love the cryptomagic) in a moment of time.

Need i remind you that the tornado cash guy was arrested and sentenced in the Netherlands