19
Vierundachtzig (84)
19debccaec9fa26499ae733a6120b11adf4db889cb206354f49e5aa2dac1c065
Dev account of @derRichi Aspiring Freedom-Tech-Dev && Problem-Solver

Well, then Motorola is not a good choice if you want to unlock your bootloader.

But I still stand with my take (related to unconfigured hardware and software).

A nostr-client version of dwitter would be really cool.

https://www.dwitter.net/about

WoT takes advantage of this by using a quality rating matrix instead of a quantity one (quoting Arkinnox's post, "1 Out of 5 Stars - Why the Five ...").

By the design of the WoT system, content can be objectively evaluated (part 2 of Arkinnox's post), allowing the value of the post to be better perceived.

Furthermore, WoT is different for each person (npub) because everyone has a unique social graph proximity and objective profile validations. And every user can choose for themselves the balance between these two metrics. https://www.relatr.xyz/about

nostr:nevent1qvzqqqr4gupzp68dx7vvdlltl7sg2qdv8838ze3tl5tq76y0jnz966fdsana6dz6qyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3jamnwvaz7tmxv9hxvctjv4ejumn0wd68yvfwvdhk6qpqgne99tk0uqde9usthn4zpe36l6zau2hfdjnwmjtewmgnhd92q3vqnqv7z5

From my perspective, WoT will be the healthy alternative on Nostr compared to the algorithms used by legacy social media platforms. Instead of "serving" an algorithm, you will "serve" your social graph.

How do you achieve this? By embracing low-time preference and providing genuine value to your network.

Is anybody reading or has read the book "Hypermedia Systems"?

https://hypermedia.systems/

Replying to Avatar Spatia Nostra

I'm seeing a lot of follow list questions on asknostr amd elsewhere today, so i thought I'd share a blanket answer:

Every time you follow or unfollow someone, a new version of your follow list is created, meant to replace the old one. Some relays may not get the memo because there's lots of relays.

When you sign into a new client, it asks whatever relays it connects with, for your follow list. The relays send what they have, which may not be the current version. If you follow/unfollow from the new client, it triggers the follow list update, editing whatever copy of your list that it has, which is then broadcast to many relays. That's how you lose some of your follows.

If the relay being asked doesn't have a copy of your list, it says "this user doesn't have one" and the client creates a new, empty list. Again, the follow/unfollow action triggers publishing & that is how you lose your whole follow list.

In short, it's a client issue because it's not making requests about you to the relays that you have in your "write" relays list, but instead to some other relay(s) that you've never sent data to before or that have old data. Avoiding the follow/unfollow actions when trying out new clients will mostly mitigate the problem. If you start using that new client regularly, eventually your follow list will make it to the appropriate relays and/or the client will get updated and start making requests to the appropriate relays.

Visit metadata.nostr.com or follows.nostr.com on occassion to back up your follow list. You can then rebroadcast the correct version, if you experience this unintended follow list fiasco. Alternatively, you can add wss://hist.nostr.land to your write/outbox relays. It will keep the latest previous version of your follow list. You can then visit the homepage to restore.

Some clients offer in-app follow list restoration, both as a paid and free feature, as well.

https://metadata.nostr.com/ works perfectly for me. https://follows.nostr.com/ does not.