Thread - Nostr Hypermedia

Relays: 5

Replies: 1

Generated: 20:46:23

nostr:nprofile1qydhwumn8ghj7mnjv4kxz7fwvvkhxar9d3kxzu3wdejhgtcprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qqsgafy9ye4j9p2x8vfmlq6equtpcg4m8ks7v545g0d3f7wwueeq5scz9g5a6 trying maple's api proxy with codename goose and I consistently get a 404. I've restarted the proxy and changed api keys many times. is this a skill issue on my part or a known maple proxy issue? haven't faced it with any other configured goose provider

2025-10-13 05:05:09 from 1 relay(s) 1 replies ↓

Replies (1)

Marks marks@primal.net npub136jg...jnxf

My best luck with Goose has been with modifying the “OpenAI” provider with these settings. I also have to do a dance when i go in and out of the settings screen multiple times hitting save until the updated configs stick. We want to work with nostr:nprofile1qqsd0hut8c2pveuk4zkcws9sdap8465am9dh9cp8d2530yssuflcracprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqqyh5dl to get an official “Maple AI” provider in goose.

2025-10-14 00:51:00 from 1 relay(s) ↑ Parent Reply