-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined array key 2 #5
Comments
Today I removed all but a few relays from the Nostrtium list and although Front-Page posting is slower , it works and there are no errors in the error log. |
Back from travel and will try to get to this as soon as i get caught up on other pressing things. Yeah, I hadn’t really thought through all of the implications of doing the auto-posting thing. When you post to nostr from the post page the way the plugin was originally designed (before adding the auto-post feature), it throws up a modal that lets you see that it’s doing something that takes some time. But when it is auto-posting, it has to do all that stuff in the background and I hadn’t thought about that enough. I’m going to have to implement an asynchronous process for looping through and posting to each relay so that it doesn’t hold up the whole WP posting action. |
@markwaters I've spent some time over the last couple days working on setting up background, asynchronous sending for nostrtium. I think that’s the way to go for both auto-publish and posting from the metabox in the post editor too. i found a nice framework for queuing up background operations but it’s a little complicated pulling it into nostrtium as a dependency in a clean way and I'm trying to work that out. very unfortunately though, as i was looking around at all of the plugin’s dependencies, i discovered that the author of the main php-nostr library that the plugin depends on has recently determined that he doesn’t have time to maintain the project and is looking for someone else to take it over. If nobody does (i can’t - also not enough time), that’s going to be a blow to nostrtium that might make me re-think how it works altogether. an alternative way to do all the nostr plumbing stuff would be to pull in javascript libraries (instead of php) and do all the nostr note construction and sending in the browser with js instead of on the server with php. I thought about doing it that way in the first place but preferred to use php if possible to be more wordpress-ish (and also because i am more experienced with php than with javascript). I’m afraid if i have to pivot to using js libraries and doing everything in the browser that one likely side-effect of that is that the background auto-post functionality may have to go because the way that is happening is (and i think has to be) independent of a browser and that means no javascript environment for any code to run in. no conclusions about any of this yet. But this is where things are with resolving this issue at the moment. |
The ActivityPub plugin sends out using the wordpress cron functionality , could that be used by Nostrtium too ? |
@coding what is difference between code security and code quality in order to align with code of universe rather than user interface to mitigate the frequency of bug fixing? |
I am still seeing errors in the error log.
I use another plugin , WP User Frontend , to enable posting simple status messages from the site front-end , usually this happens instantly , since installing the NOSTR plugin this now takes a long time , sometimes failing.
The text was updated successfully, but these errors were encountered: