Cameron / Cameron is on Nostr

"60eeed57f1248fc764f44bb5dca807d3788f55f7e6a884fe99872af5c2792fe1356d1a4abf1ffcfe1869939ed45d523a135399f01159ef905e8ea1664835fd94"

Last Notes

2025-04-04 12:59:23

- reply

Strange. There must be something wrong with that other channel.
Maybe you can get in on a ring or fire to open channels with more people. @nprofile…e598 seems to know when they're happening.

2025-04-04 03:01:53

- reply

BOLT12 is confusing for me (I still love keysend).
Since transactions are cheap right now, I opened a channel to your node. Not sure if it will help. Maybe something to do with liquidity or fees on your other channel(?).
Can test more tomorrow if you like. I'm curious if a standard BOLT11 invoice works compared to a reusable BOLT12 offer.
Maybe try a regular one-time invoice, then a reusable invoice.

2025-04-03 16:51:59

- reply

Did you try opening port 80 & 443 (in addition to 9735)?
Does an "open ended" invoice need 80/443 to negotiate the actual/final invoice?

2025-04-03 15:15:54

- reply

Just sent 22 sats via keysend (11:16 EDT). Looks like it worked.

2025-03-28 21:38:37

- reply

Just listened. I think your albyhub problems are related to private channels.
The channel you open to their provider should be public "for podcasting".
https://guides.getalby.com/user-guide/alby-account-and-browser-extension/alby-hub/faq-alby-hub/should-i-open-a-private-or-public-channel
Also verify your node is visible on the network. Is this it? (1 year old, 0 channels?)
https://amboss.space/node/026fee5ebbf2334f045808ed50182a7578facf29894d27038e6f5fb8123f75f87a
And of course that LND is configured to receive keysend payments.

2025-03-20 20:49:14

- reply

You can run a node over tor but it's not recommended because your node will be harder to find (by other nodes).
Haven't heard of arwave either. Something like qortal?
Podcasters want to be found by nature : ) Untracability isn't much of a concern in podcasting (IMO).

2025-03-02 20:32:48

- reply

No problem. You discovered a hidden feature to always pin an episode to the top of ipfspodcasting.

2025-03-02 18:10:30

- reply

Since I can't do a screenshot, here's some xml of the error.
</description>
<link>https://fountain.fm/show/wCAbpGSaWSGna8fz9hNc</link>
<pubDate>15 Febuary 2025 18:30 -0700</pubDate>
<podcast:chapters url="https://filedn.com/l0rngxCNDKAhHBs9WFEP7Dj/p4v/38/p4v-chapters-38.json" type="application/json+chapters"/>
<itunes:image href="https://filedn.com/l0rngxCNDKAhHBs9WFEP7Dj/p4v/38/cover-art-38.jpg"/>

2025-03-02 18:03:38

- reply

Was scratching my head for quite a while. You typo'd the pubDate as "Febuary". (For some reason amethyst won't upload a screenshot)
When I can't figure out the date I use the current date instead of 12/31/1969. Which is always today (everytime I scan).
If you fix the typo and "Scan Now" from https://ipfspodcasting.net/Feed/53/Podcasting4Value it should fix on the next scan.

2025-03-02 16:51:37

- reply

Strange, I'll take a look...

2025-03-01 16:13:29

- reply

Thank you, thank you.
Running the IPFS Podcasting app on a Start9 or Umbrel is easy.
Linking your node via an email address to ipfspodcasting.net lets you "favorite" your favorite podcasts to be stored and shared from your node.
Decentralized hosting by fans of the podcast!

2025-01-19 20:55:25

- reply

Thank for the help (I'm the one who wrote down an 8-word seed phrase with my npub). Have no idea how I did that.
Created a new ID (and made sure I have my keys this time).
Will my old account eventually be purged from relays, or will there always be two of me?