Dear Nostr, On the 7th of October, there will be a Open Source Conference in Luxembourg. I suspect the target audience will be the semi-normie public/private sphere, but mostly public sector, education etc. Also i suspect this is very much intended as fediverse party. The whole fediverse thing got some traction ever since the EU decided it needs to become more independend from US "Big Tech". I am pretty sure most of not all of these people are not even aware Nostr exists, it is simply not part of the conversation. Lets see if we can change that. Ideally we hit them from all angles, demonstrating how Nostr already managed to eclypse in a few short years what this fediverse has been struggeling to acomplish in a decade. Their theme this year is ''Leading by example in Digital Sovereignty'', and we are, so lets make them aware of it. At the very least we can shoot our shot; if they happen to be so biased towards the fediverse that we are not even welcome, so be it, only one way to find out. There are 2 weeks left to submit. Lets see if we can coordinate a bit such that we are not in eachothers way. Hopefully if we can manage to get all the type of talks/workshops/training established among all their main tracks, and throw these people a curveball. https://conference.opensource.lu/ Tag anyone relevant below, these were just the first 4 names that came up with and figured i would not make the list too long.

Who is aware of the bias though

You have to understand that this assumes a cultural strategy. What if my cultural strategy is to actively undermine the outgroup? I don't disagree with you, but there is an assumption of universalism there, and that is not a universal mode of operation. So....better gear up brother, we have a crusade or 2 to go on...oh and a whole lot of hanging, because that is how those norms got established in the first place🤷‍♂

This shit riped like a fine ass wine https://www.youtube.com/watch?v=pXPKHuPVxTA

404 grass not found

The proof! It may take a while before a cool fancy app results from this. But i wanted to get this part done and tested (the price is i have 3 hours of sleep time left for what will probably be a 13 hour work day tomorrow but it is what it is).

Btw, tip for everyone that got their Bitcoin stolen: I bought a forest in order to deal with the potential consequences of keypair-based-systems, so at the end of the day, i always have a place of my own to go to and cry. Luckily for me my funds are safu....today atleast. Here are some more forest pictures of today

For some reason, every time i pick this thing up, Mick Gorden starts playing in the background

So i had this issue: Dead fallen oak, stuck in another tree. This has been the situation for about 2 years, because its this whole thing and blablabla. So this week i decided i was just going fix it.

I will point out that Alex did state that his remark in the context of it being decentralized. So in that sense he is right. The point is that decentralization and scaling/efficieny don't mix well in this regard, so we can't expect that method to do everything for everyone all the time.

I think it important to point out here that the crucial factor here is scale and efficiency. Grimmoire was/is a client that demonstraded more fancy queries, and you can do all sorts of things that way. But insofar every-day use concerning large sets of people and a lot of events etc etc, the day to day way to do this is to rely on relay-feeds (that may or may not have done all the heavy lifting for you, leveriging those fancy queries themselves). What is boils down to, is that 'location' is still important, but that identity (by extension social graph) and content/data is not strickly bound to a location/server/relay. So whenever for whatever reason, one of these relays you have been leveraging (for what they are good for) starts acting up, you have means/alternatives such that you don't instantly become marginalized down to your own website or some alt-platform neither of which anyone will ever visit ever....you probably won't even have to leave your app to 'reconnect' with someone

I understand, but you run into the same issue the moment your master key is compromised. You buy a rotation scheme and allowing for 1 key in cold storage, by paying for intepertation complexity/demands. Im not saying that is a bad thing per se; one could argue that for high profile ID's, like a president or something, this is warrented; those that want to run this extra type of verification know that they should irt this ID, and can be bothered to do so (perhaps, assuming). But as a 'general' scheme, i: 1: don't believe there will be one scheme that manages universal addoption. 2: think that should not even be the case to begin with, regardless of whether that is manageable/possible/achievable. To expand on 2 (i deem 1 to be self-explanatory): all (rigid formal) defenses like this that you implement turn against you and benefit the attacker the moment an attacker succeeds in penetrating them. If the running assumption is 'this master key is truth/my guiding star the moment there is appearent chaos', and that assumption is invalid, you just increased the problem. Frankly, i suspect i think that all rotation schemes should be abandoned, but like i said i leave the door somewhat open that they could be valid in certain instances (though i am almost convinced they are not....almost). Ive written an article on this, but in short: If all you can do is extend what is ultimately the same problem, i much rather just deal with it head-on, and accept that the only way to fix this is 'social recovery', i.e. leveraging 'side-channels' to re-establish the same 'identity' under a different keypair via the 'social' context of the old keypair. The more significant an ID is, the easier this probably is to achieve, so the risk is mitigated in that sense. Where we find eachother is our love for OTS haha, because i think OTS can be used to preserve your post-history under an old key, by stating under the new key until what date the posts are valid, and outside observers can, using OTS, determine what is part of that history/the validity of it, after the fact. Anyway, you will probably always going to find me countersignalling any (formalized) rotation scheme, but don't let me discourage you :)

You know what is nice about NIP-29? That it is not rocket science crypto voodoo magic. Ergo: What is the solution to data-loss? Back-ups elsewhere. What is the solution against an unresponsive relay (for whatever reason)? Another relay. Are these things clearly described inside the NIP? As it so happens, yes, they are, go read it. https://nips.nostr.com/29 Perhaps decent clients and a sense of responsibility towards a community among just a single participant of those 1000 users (not so) magically addresses these concerns.