I'll start walking there now.

You've got hypemen, I've got Heather and #shakespeare.

I'll just start using this instead of a resume in the future. Thank you. 🙏

I never go to my mailbox. #sovereignty

Does this version of the site work for you using the same login method? https://traveltelly.shakespeare.wtf/ If so, here is how I managed to add this function: 1) I cloned my Treasures project into Shakespeare. You can do the same via the following URL: https://shakespeare.diy/clone?url=https%3A%2F%2Fgitlab.com%2Fchad.curtis%2Ftreasures.git 2) I went back to the traveltelly project, and then provided Shakespeare the following prompt: "Study ../treasures, make sure the login functions are the same in behavior, especially for the nip-46/connect option." Let me know if that works!

It's great for artistic pursuits, though.

It's technically on GitHub's side, but due to a compilation issue in the code that doesn't block functionality for Shakespeare. If you go to this page, you can see all the deployments for the traveltelly site: https://github.com/bitpopart/traveltelly/actions/workflows/deploy.yml From here, you can click on any run with a red X to see why the run failed. You'll be taken to a page for the run, in which you'll need to click on the 'deploy' box with a red X on it as well, which should take you to a page with logs specific to that build. Here is an example of an earlier failure log: https://github.com/bitpopart/traveltelly/actions/runs/21310108470/job/61345062222 To resolve the issue, you can copy the log text as you see it here and paste it to Shakespeare with a request to fix the errors. With this level of detail, Shakespeare should be able to figure out where the issue is and fix it accordingly. It looks like your builds are going through successfully at the moment, so no further investigation is required. Hopefully this information helps, though!

Here is another follow-up merge request: https://github.com/bitpopart/traveltelly/pull/4 This one attempts to fix the type checking, but more importantly, makes it non-blocking for deploying to GitHub Pages. Shakespeare is a bit more forgiving in this area, so this change should bring the GitHub deployment onto the same level.

Check once more (while logged in as your traveltelly npub on Shakespeare)! You should now have a total balance of $30 in credits.

Fair point, I see more type-checking errors post-merge - looking!

There was an issue with Stripe we believe should now be resolved. The credits you purchased should appear soon​ - let us know if you encounter any problems, though!

Greetings! I managed to fix the error in question and have submitted a merge request with the fix here: https://github.com/bitpopart/traveltelly/pull/3 I've attached an image of how I directed Shakespeare to fix this as well using the prompt "run the build tool and fix the failure".

It's never been easier to touch grass (or rocks). Go hide your first #treasures today!

Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos. Lorem ipsum dolor sit amet co adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

My daily reading from https://nostrdamus.me #nostrdamus #daily • Past: The Magician (Reversed) - Your past is marked by a time of manipulation and poor planning. You may have used your power for selfish reasons, leading to negative consequences. It is important to reflect on these past actions and make amends. • Present: Judgement - In the present, you are being called to listen to your inner calling and to forgive yourself for past mistakes. The Judgement card is guiding you to be reborn into a new way of life. This is a time of absolution and a new beginning, so don't be afraid to start over. • Future: The Chariot - The future holds the promise of a great triumph, a time when you will achieve your goals and be recognized for your accomplishments. The Chariot's energy will be with you, bringing you victory and success. Embrace your power and you will conquer all obstacles. #past_the_magician_reversed #present_judgement_upright #future_the_chariot_upright

Indeed, sounds like it was momentary network issues. Thank you for reporting though, and glad things are up for you once more!

Ah, that behavior is likely due to relay.primal.net routinely purging non-standard, custom kind events from their relay. I know that the Ditto relay (wss://relay.ditto.pub) and Damus (wss://relay.damus.io) retain such events based on my own experience. P.S. Make sure to instruct Shakespeare to remove wss://relay.nostr.band from your sites, it hasn't been responsive as of late and might also cause issues.