It's strange, I was running it fine at the beginning of the year. I switched to a new device, and it still ran fine. I was using a Pixel 4a before with no issues with immersive scrolling. I have never cleared my cache once since buying this phone in like March. Never cleared on the Pixel either. It was soon after I got this phone that my experience became terrible, which I'm thinking now could have been cache-related. Nonetheless, I am still issue free since disabling, and am curious about this issue and it's frequency.
Do either of you have immersive scrolling enabled? I found disabling this took my performance from a 3 to a 9. It was night and day, on a modern device that doesn't really lag in other apps.
*nervous laughter* 😅 When is the next webinar session for Alexandria? Or like dev call? I crave knowledge, and you have a library. Let me meet your people. I'm free until I perish. Life is Nostr. Nostr is life.
I want to say, I have tried running isolated relays and had poor luck until now. I immediately realized a few things:
A) My users may not know how to use Amethyst
B) I also may not know how to use Amethyst
Funny enough, before realizing these things, I had already (recently) drafted a feature request for Amethyst to expand upon its relay management options. I talked a bit with Vitor about this and overall I can see how this is difficult to approach for any client dev. You can view that here:
https://github.com/vitorpamplona/amethyst/issues/1251
In any case, I am looking to pioneer forward with basically a re-design of NoteDeck using bun.sh (for browser) and/or buntralino (for standalone) to hopefully encourage people to work on the same client together. Queue the xkcd competing standards meme.
The reason I'm somewhere between "a nostr client" and "LogSeq" is because my first priority is explicitly relay management. Jumble.social seems to have nailed this, so I will probably be getting comfortable with it this week,. So far I am only interfacing with this relay using Jumble. I don't think I can remove posts, so please note that some boosts in Amethyst may be coming through on these relays.
Back to Amethyst. I don't know how anyone else is using it, but I'm completely embarrassed to admit that I did not fully grasp the control schema. It seems simple at first, then complicated, and back and forth.. But overall it is designed to be useful. I'll break it down just in case anyone is struggling with it still, and I may go on to republish this later for others:
R/W matters. If you choose to write to a relay, it is going to be enabled as a default option when you go to post any note. If you choose not to read from the relay, obviously you will not see the notes that are only posted there. To sum this up, you should probably disable "write" on all of your 'general relays'. This means you will no longer blast the network with each post, but also means you will still have to select each relay you wish to publish to (at time of posting).
The secondary issue that arises from this is that boosting content will no longer "blast" to a bunch of relays. You will need to quote or fork a note to proliferate it across other relays. The only things that WILL work- is dm's and draft. This is the apparent "bug" with Amethyst's relay pooling. There is not a specified way for the app to discern a difference otherwise, except what the user has laid out in their configuration.
Lastly, I don't use the other features of Amethyst myself. I'm a kind-1 maxi for now, until a client can prove to offer a better experience. Otherwise I try to use dm's sometimes, but that's pretty rough lately. So, I disable a lot of the other elements under general relays, leaving only one or two in global, and most have home enabled.
Where we're left with is Amethyst provides the best mobile experience, but can be a real bitch to isolate a relay on, because of how it toes the line with its functionality. Relays can easily clutter up with boosted content and become a nuisance within our home feeds. This is sub-optimal, so I'll just say, I hope for the best experience for everyone! :)
Lol the irony of this note going anywhere but where it was intended
I want to say, I have tried running isolated relays and had poor luck until now. I immediately realized a few things:
A) My users may not know how to use Amethyst
B) I also may not know how to use Amethyst
Funny enough, before realizing these things, I had already (recently) drafted a feature request for Amethyst to expand upon its relay management options. I talked a bit with Vitor about this and overall I can see how this is difficult to approach for any client dev. You can view that here:
https://github.com/vitorpamplona/amethyst/issues/1251
In any case, I am looking to pioneer forward with basically a re-design of NoteDeck using bun.sh (for browser) and/or buntralino (for standalone) to hopefully encourage people to work on the same client together. Queue the xkcd competing standards meme.
The reason I'm somewhere between "a nostr client" and "LogSeq" is because my first priority is explicitly relay management. Jumble.social seems to have nailed this, so I will probably be getting comfortable with it this week,. So far I am only interfacing with this relay using Jumble. I don't think I can remove posts, so please note that some boosts in Amethyst may be coming through on these relays.
Back to Amethyst. I don't know how anyone else is using it, but I'm completely embarrassed to admit that I did not fully grasp the control schema. It seems simple at first, then complicated, and back and forth.. But overall it is designed to be useful. I'll break it down just in case anyone is struggling with it still, and I may go on to republish this later for others:
R/W matters. If you choose to write to a relay, it is going to be enabled as a default option when you go to post any note. If you choose not to read from the relay, obviously you will not see the notes that are only posted there. To sum this up, you should probably disable "write" on all of your 'general relays'. This means you will no longer blast the network with each post, but also means you will still have to select each relay you wish to publish to (at time of posting).
The secondary issue that arises from this is that boosting content will no longer "blast" to a bunch of relays. You will need to quote or fork a note to proliferate it across other relays. The only things that WILL work- is dm's and draft. This is the apparent "bug" with Amethyst's relay pooling. There is not a specified way for the app to discern a difference otherwise, except what the user has laid out in their configuration.
Lastly, I don't use the other features of Amethyst myself. I'm a kind-1 maxi for now, until a client can prove to offer a better experience. Otherwise I try to use dm's sometimes, but that's pretty rough lately. So, I disable a lot of the other elements under general relays, leaving only one or two in global, and most have home enabled.
Where we're left with is Amethyst provides the best mobile experience, but can be a real bitch to isolate a relay on, because of how it toes the line with its functionality. Relays can easily clutter up with boosted content and become a nuisance within our home feeds. This is sub-optimal, so I'll just say, I hope for the best experience for everyone! :)
Lit is an understatement. I'm here to help. Especially with design because I fucking suck at coding. 😭 When I meet the right devs it's game over.
Worst case scenario, I'll become the right dev.
But seriously did I read kind 1A earlier? I'm deceased 😭 God why do I desire so much sovereignty
Curious if you might have thoughts on this article I wrote yesterday. I won't be approaching STEM like you mentioned but I do want to work with Alexandria and eventually that type of support would be addressable
Correct, yes. I tend to lose people when I break out the word transclusive 🤣 But you understand it just fine. In this way, Nostr is not truly transclusive except in the way GitCitadel is approaching event structuring.
Which, come to think of it, is why I get so damn confused when I read about it 💀
I once saw it described as the longest-running failed application 🤣 or something like that.. OpenXanadu is a weird little example of trying to build what Xanadu tried to make.. this is ancient internet stuff that is still floating around in the world.. it's all based on some old note-keeping system called the Memex, which you may have heard of instead.
In my mind, the Nostr protocol provides a wealth of transclusive information. The concept of transclusivity is not an exact science, I think. I see many examples of it in various things. I assume when a traditional web article embeds a Tweet- this is transclusive. The Tweet exists somewhere else, but has been embedded, and provides a source.
You and Citadel are very familiar with it, for sure. OpenXanadu is just a fun visualization of what the old attempts at (LogSeq) looked like.
xanadu.com/tech
open.xanadu.com (lol)
xanadu.com/xuDemoPage.html (kind of interesting actually)
I imagine they want to proceed slow and carefully, but at the same time the possibility of securing a grant creates a competitive environment. It's more capitalistic than it needs to be I think. We're all racing to be accepted, but the problem is it leaves the ecosystem work out and feeling undervalued. A bit like a carrot on a stick.
There's other Android clients?
Don't forget to allow me and nostr:nprofile1qqsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpspzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uf70yl9 and nostr:nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpz9mhxue69uhkummnw3ezuamfdejj7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsz9nhwden5te0dehhxarjv4kxjar9wvhx7un89uqaujaz on your relay. ☺️
Consider it done ✨
I heard someone donated a Bitcoin or something to fund OpenSats, maybe more? I'm not too informed on these matters.
There's always risk involved in any venture!
Codium? Like VSCodium? That's where I work for code.
I think for long-form articles and content, LogSeq doesn't really do anything spectacular, unless you're comfortable sorting segments up into a graph. I understand why overall LogSeq is less popular- because many users are "do'ers" more than "archivers". LogSeq as a package aims to serve do'ers who need to manage their notes in a graph type ecosystem. As well as archive them, or publish them in theory.
So generally Joplin/Obsidian are by far the most popular solutions. VSCodium for devs. And emacs and so on for really efficient devs. I have never gotten into emacs, but I actually do have an interest in trying it some day. I could never really get comfortable with Vim either. There is an insanely fleshed out terminal version of essentially LogSeq. I could dig it up some time. Never used it myself but certainly cool to see.