pull down to refresh
195 sats \ 1 reply \ @ibz 16 Mar \ on: Alternative vehicles – Cars that last far more than 200,000 miles... for cheap alter_native
I don't think I ever bought a car with < 200k km... To me, it just doesn't make sense. I mostly buy VW or Audi, because these are what is preferred here in Eastern Europe. Toyotas are lovely, but every mechanic here knows how to deal with German cars and spare parts are very easy to get - either aftermarket parts (new) or just original parts from retired cars.
I currently have a VW T4 and and an Audi A4, both have hit 300k km and are in good shape. One was 5k EUR, the other one was 1400 EUR. So yeah, buying new cars just doesn't make sense...
For those who haven't been to Eastern Europe: check out Salo [1]. We literally eat raw pork fat over here. And it is delicious!
Re-reading my comment, I see how it could be misunderstood. I didn't mean to say nostr failed. But that it failed to achieve the level of decentralization that Bluesky did. You can still build self-sovereign apps on nostr, but it is certainly harder than it should be and 99% of the nostr apps completely miss the point of nostr.
Amazing news!
I hadn't looked much at Bluesky before, but now I just did, and I am very impressed.
It seems like what Nostr should have been, but failed.
You hold your data in a safe place - a place you have 100% control over. Not inside Twitter, not inside the cloud, not on a VPS. This might mean your data is on your node running in your closet. Which means it is not accessible from the outside world. Nostr clients cannot connect to your node, since it doesn't have a public IP. Plus you don't even want random strangers to know your node's IP address.
So what do you do?
You talk to these random dudes that sit on the street all day long and answer questions to anyone passing by.
You tell them ... "if anyone asks about me, tell them I said this and that." That's it. These dudes might come and go. Nobody needs to know who they are. The whole point is that they don't need to be trusted, because the messages are signed, so these shady dudes cannot alter the messages. Also, nobody needs to know where exactly you live, all they need to find is some random dude knowing something about you.
Didn't know about this term, but yes. This was the whole point of nostr: to 1) put you in control of your data and 2) make your data easily accessible and hard to censor.
How would you achieve 1) if you would not hold your data in the first place, anyway? How are you self-sovereign if you trust some random relays to hold your data forever?
The issue you raise is valid and I think it comes from the misunderstanding that even most nostr app developers have about the protocol which leads to them writing "nostr apps" in a way that - indeed - makes no sense, causes confusion, and ultimately does not solve anything.
In one short sentence: people mistake nostr for IPFS. They think relays are there to somehow store the events, to provide persistence. They are not! They are there to relay the data. Remember, the T in nostr stays for transmitted.
Most "nostr apps" do this: want to publish an event? Let's blast it to a list of relays and say done! Want to see other people's events - or even my events? Ask the same list of relays. Maybe have a DB locally used as a cache for better performance. This is the wrong approach in my opinion, and leads to nostr being misunderstood - at best - and will lead to data loss and pain and disappointment in the long run.
To better explain: I think relays should be thought as ephemeral entities. Every client should store the data locally first. After storing the data locally, it should blast it to a bunch of relays that happen to be active at that particular moment, and other clients will receive these events from those relays. But these relays might disappear an hour later. They are not there to stay. Having the data locally means that IF the user decides that the events are important enough (for example the events represent profile metadata or long-form blog posts), it can periodically send them to new relays. If the events are not considered important - like a short status update - it is perfectly fine to just stop caring and assume that whoever got it, got it, but other clients that come online later might not get it anymore.
I don't understand the question. Leftovers from eating out?
Because at home we always cook amounts that we will eat for 2-3 days. Isn't that what everybody does? It just saves time, plus you can't know the exact amount you will eat while cooking!
Sure, after 2-3 days we would give the "leftovers" to the dogs and cats and cook something else...
It is certainly very much possible. I did it a few times, for long periods (1 year). Sure it was less convenient, but nowhere near impossible.
Seems that all the meaningful discussions from Twitter have moved to SN, not to Nostr. So I don't see much point in using yet another social client.
However, I have used Nostr the protocol quite a bit, since over the past year we have built a marketplace on top of Nostr.
So yeah, good protocol, but pretty useless as a social network IMO.
I thought so, otherwise you would not be on SN. ;)
Sounds good, but certainly outside the reach of normies. I think separate unconnected devices are a much simpler way to ensure privacy, otherwise... "Next" "Next "Sure I want Apple Cloud" is the path most will take, which is sad, because this really leads to The Matrix - humans end up essentially providing data to train AIs for the exchange of some convenience.
Disagree with SD cards being an issue though. That's like saying a physical photo album in my closet is "insecure". Except it is actually the best way to opt out - even if unencrypted - because it exists purely in an offline form.
Have fun being constantly spied on and mined for behavior data to train AIs.
Have fun being in the matrix, basically.
A smartphone is the last thing I need. I prefer separate devices that do one job and do it well and are not connected to the internet nor to other sensors that are not absolutely necessary for them to function.
I prefer a camera to take pictures, a recorder to record sounds, a musical instrument to make music, CASH TO PAY FOR STUFF, etc etc. And yes, a phone also, to make calls.
Indeed, was about to write this. Why is this not an option? 1960-present? The OP must be kidding... Those are the worst... probably because WTF 1971...
It is most certainly a new coin. If their marketing department was clever enough to call it a "sidechain" that is a very different story.
Indeed it is. A Proof of Stake shitcoin. I cannot see any difference between the Liquid Federation and the Ethereum staking nodes or the EOS validators. If anyone can explain it to me, I am very curious!