Since I had to perform the same action for my clients, I went ahead and broadcasted the kind events associated with your sites back to the Primal relay. This may not be a permanent solution if they are to be cleared again, but it should at least act as an immediate one.

Greetings! For the current iteration of Shakespeare (Act I), that is the current flow for working between a remote got host and Shakespeare. In the next iteration of Shakespeare, this will become a bit easier to manage using ngit projects that can be fed more easily between Shakespeare and the repository. For the latter inquiry, I haven't set something up like that personally, but possibly multiple file parts that must be decrypted via a key (provided after zapping/purchasing the media). Here is a similar inquiry fed to ChatGPT that provides a few more ideas: https://chatgpt.com/share/68a4d1cf-a428-8007-9bda-6e27b9ea421d

Sold! 😎

Happy international #geocaching day! Today's a perfect day for hiding and finding #treasures. Where shall the adventure take you today? 😎 https://nationaltoday.com/international-geocaching-day/ https://treasures.to

I re-forked your repository and ran through the same process, which seems to have worked for this example: https://chadcurtis.github.io/nostrpop/ Aside from setting the page deployment source as 'GitHub Actions', the only other action that may be required is starting the pipeline once more. Specifically: 1) Going to the 'Deploy to GitHub Pages' pipeline - https://github.com/bitpopart/nostrpop/actions/workflows/deploy.yml 2) Clicking the 'Run workflow' button to the right of the page, followed by clicking the second green 'Run workflow' button in the popup that appears:

There are a couple of items here needed to make this work, the first as noted is the root domain setting needing to be updated - I opened a pull request with this change here: https://github.com/bitpopart/traveltelly/pull/1 The second is that you'll need to ensure that 'GitHub Actions' is the selected page deployment strategy under your repository > Settings > Pages:

No further action needed at this time! 🙂

Greetings! There was an upstream provider issue that I've just cleared out, thank you for the quick report. You should be able to prompt once more (after a refresh) - let me know if you have any issues, though!

Probably some of the most fun I've had in a while, thank you friends. 🙂 Thank you for being right there with us and killing it as well, !

I believe what you're seeing is the outcome of a ton of custom events being purged from the Primal relay. I noticed there are quite a few listings from https://treasures.to and https://surveil.cards missing there as well. If I switch to the 'Damus' relay (under the profile icon menu), I see your more recent reviews. The same issue appears to be present with both your sites. The immediate solution for both would be setting Damus as the default relay instead of Primal - this can be prompted or modified directly in the App.tsx file of your projects: https://github.com/bitpopart/traveltelly/blob/1da824d0475d35986874bbe213be3cebe305741d/src/App.tsx#L35

For now! (I might still be working on things. 😗)

I like the way you think. 😎

I think we managed to squeeze a few work weeks into 2 days. A rather miraculous feat!

#treasures in Sardinia! Who shall be the first to find it?

That is a good insight, hah. Sometimes trying again is enough for these processes.

I simply couldn't pass a deal like that up.

After taking a moment to investigate, I think you would likely need to go into the opposite direction now that you're using traveltelly.com as the domain for the GitHub Pages site. In this case, the '/traveltelly' base path configuration would need to be changed to '/'. I opened this pull request to achieve just that: https://github.com/bitpopart/traveltelly/pull/2 It's difficult to verify without using a custom domain myself, but I believe this will remove at least one immediate issue. Otherwise, your DNS configuration seems correct for this domain:

I believe there might be an issue with the GitHub Pages site, or the base path - depending on where the domain is pointing. I shall take a look once I'm home, though!