I don't know anything directly about the devs, but grapheneOS works better for me than stock Android and the amount of stuff I am not currently "sharing" with google lets me sleep better.
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c and I re-wrote NIP-65 to make it easier to implement. Amethyst will be moving to the "Gossip model" as soon as we finish this Private DM/Group workstream.
Then we say goodbye to the old infrastructure that centralizes in large relays.
Together with nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 's new relaying.io service, we can finally start claiming a healthier decentralization in Nostr.
This is great news. I think if widely well-implemented in relays and clients the gossip model can fix some fundamental issues in nostr that would eventually (under higher adoption) become show-stoppers.
If nostr's functioning becomes critically dependent on some low number of popular relays (which is arguably the case already), it loses its single most important characteristic: DECENTRALIZATION. And those popular relays inevitably become targets of all kinds of interference (hacks, DDOS's, court orders, etc, etc, etc).
If nostr is going to work as a large-scale social media platform (there are plenty of other use-cases that don't depend on this), there have to be LOTS of independent, commodity relays all over the place that are fairly dumb and follow a relatively simple set of common rules.
Live and let die. Also Roger Moore.
GOSSIP LMDB progress:
Things are going well. I'm about 2/3rds through the work.
As for performance (I know this is what people want to know about) I just ran a test by searching for the string "uploaded" in events. There are about 75,000 feed-displayable events in my local store. The SQL code took about 3 seconds to load the matching events. The LMDB code took about 1 second to load the matching events. So it is about 300% faster. Not mind-blowing, but worthwhile especially as it is cleaning up the code so much.
The LMDB search method is using speedy (de)serialization from my rusty Event type (long ago convered from JSON) on EVERY event so it can apply filters to it to determine if it matches (that's a lot of allocation/deserialization and there is room for improvement here if I did something like what nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s has started) rust Regex (case insensitive and unicode) against content and four human-readable tags, and rust stdldb sort_unstable_by() to put them in descending date order. I didnt check that the results are identical in the two cases but they are designed to be.
I have not pushed the branch because I keep rewriting the commits to keep the complex progress organized enough that I don't confuse myself, and I don't want people stranded on commits that disappear.
The code that imports from SQLite was done quite a while ago. The majority of the work is replacing the functions that did SQL calls. As a first pass, some of these replacements are dumb. They scan every record. From there I will create more structures to optimize.
I've replaced settings, local_settings, event_seen_on_relay, event_viewed, hashtags, relays, and event_tags tables. I'm in the middle of replacing the events table. Finally I will have to do person and person_relay tables.
I'm retiring a lot of code that is no longer needed or that I discovered was a bad idea anyways. The number of lines of code will be quite a lot shorter after this is done.
To paraphrase a toy story character: "To LMDB and beyond!"
Original code is a rush when you get it working. Refactoring gives you the satisfaction of craft. Looking forward to when you push this new code to main.
Thanks. I'm following a handful of AP accounts through the mostr.pub bridge and whether their posts make it to my nostr client seems kind of hit and miss. It's fantastic that it exists at all but I'm wondering if nostr federation is not still a bit alpha.
Also, for people on the AP side, nostr user names are so opaque.
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6
Sorry to use you as a chatGPT substitute but I don't like talking with algorithms.
Do you happen to know what the simplest (smallest resource requirements), cleanest, docker-based solution is to stand up a small activity pub server that can federate with mastodon? It would be used just to host one or a small handful of related accounts - not for the purpose of creating its own sub-community.
Some years ago when I was looking into the same, I put up an eexperimental pleroma instance. Is that still the way, or something better since then?
All you need is an infinite number of elifs and an infinite number of print statements and you have AI.
Sorry, but until people understand what decentralized means and why it is important to them and to a functioning society... until they DO care about that... we
Disintermediated, p2p value transfer is important no doubt.
Disintermediated, uncensorable p2e (everyone) speech is (at the present time) a bigger innovation.
You could take a look at my personal strfry repo here: https://github.com/pjv/strfry_personal_docker - would be easy to modify it to suit your use-case.
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 has published a bunch of excellent strfry policy code here: https://gitlab.com/soapbox-pub/strfry-policies/
I use Gboard on graphene and it works perfectly. Only keyboard I can tolerate and I've used a bunch.
The way I have it configured on my phone, Google services is installed but it has zero network permissions. Same with Gboard. Nothing Google on my phone is allowed to network at all.
If it's like it is here (in the US), it will feel pretty damn fast compared with 4G. It varies quite a lot from minute to minute but it's not unusual to see peaks of close to 300 mbit down.
It is very assymetrical though - I don't get near the DL speeds in the UL direction.
Well... there are definitely a few people using it and giving me feedback which is helping me fix bugs. But mainly in answer to your question, yeah, I'm using it for exactly the reason that I built it - to send out announcements of WordPress posts to nostr.
I think building more general purpose tools that would take an RSS feed as an input and generate nostr posts as an output is also a great idea. Not exactly what I wanted, so I built nostrtium to scratch my own itch.
Problem is... if you went far enough with hardware and software it would be far too threatening for the networks to allow such devices and so they would not. So then you'd also have to somehow launch and maintain an alternative global mobile wireless network.
Gotta say that I am extremely happy with a Pixel device (6a) running Graphene OS. I was expecting to have to make a lot of awkward compromises but I have not had to do that. My use-cases are probably atypical but I've been able to set up this phone to do anything and everything that I want and need to do with it and altogether it honestly works better - a lot better in every way that matters to me - than my prior Samsung-on-Android phone that it replaced.
I have starlink in rural usa. I've had it for about a year now and it has been much better than the long distance wifi (WISP) service it replaced.
The customer service has been good when I've had to use it which hasn't been often.
The only negative thing I've experienced so far is already 2 price hikes since I got it. I started at $99/mo and soon after it got bumped to $110 and just recently up to $120.
Still worth it to me given I have no current alternatives that have good bandwidth. That may change soon with expansion of local 5g service providers.
nostr:npub16dmvfhm7uwkxnhxg30k6aczw23wxhgvs62n3puzl5tykpa4aa8esja83yd
If this was really a true statement by you, you'd at the very least be mirroring all of your twitter posts here on nostr (or somewhere that they cannot be censored or interfered with). You have a large following on Twitter and most of those people are not here on nostr. Clearly what's more important to you than freedom from interference is reaching your audience. Which is understandable. It's a chicken / egg thing and you are the chicken. Lay eggs here.
There is a new version now (0.7.1) both at Github and also in the WP plugin repository. You can install nostrtium from the WordPress repo like any other plugin. Please let me know what you find. Maybe post an issue on github (https://github.com/pjv/nostrtium/issues).
Also try deactivating and reactivating the plugin