Maybe. Clients seem to be finding my current server list easily. I've changed those & relays a lot over the last month while troubleshooting, so that part feels like a win. 😅
Thanks again 🫂 I really do appreciate the help. This has been a process of elimination & the conversation in this thread has supercharged that.
the error probably isnt your blossom list, the 400 invalid content type was coming from blossom.build, and from satellite in your screenshots. it's something with the apps encoding the wrong (unmatched format) or something along these lines. it also isnt likely relay related. are you using a mobile device or desktop or both? just curious. might shed some light. i dont know much about how apps encode but i would guess amethyst has the most control over this and since you get the error there, it may just be some overlooked thing about blossom specs either on the clients or blossom servers.
With Yakbak, I've tried on both mobile browser and my laptop, with this profile. Same with Flotilla for images, though I'm not so sure that's even related anymore.
I tried replying to a nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqppemhxue69uhkummn9ekx7mp0qy0hwumn8ghj7mn0wd68yttjv4kxz7fwv3jhyettwfhhxuewd4jj7qg3waehxw309ahx7um5wgh8w6twv5hsleq7kw voice note via Amethyst yesterday. When that failed with this profile, I tried with my nostr:nprofile1qqsrcwyu3ax5dj5px9n58glr8nkmr5rpn7rh3mn563ex2a670gh07lcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qfqwaehxw309ashqmrpvdjkjmn5dpjhxatw9ehx7um5wgcjucm0d5hs9r2qae profile and that worked. Twice. Both profiles on the same phone, same app, same server (being blossom .band), 1 different relay. I tried changing relays to match and it still failed with this profile. I am running out of combos to try. 😅
I have to restate, everything worked great with this profile prior to 6 weeks ago.
I just introduced another workaround just for you, please test
Holy shit, that worked! Thank you!! Is there a semi-layman's explanation so that I may understand what the problem was?
Thank you! From my investigation I see that the client that send the file is misrepresenting the mime type. Basically it tells that it sent video, but we detect audio, or visa versa
I've been beating myself up over this for a month and a half! 🤣 Thank you so so so much!
nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hsvlnggv nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqppemhxue69uhkummn9ekx7mp0qy0hwumn8ghj7mn0wd68yttjv4kxz7fwv3jhyettwfhhxuewd4jj7qg3waehxw309ahx7um5wgh8w6twv5hsleq7kw
Fishcake fixed it! I can leave you guys alone about it now! Thanks for helping me figure this out and for putting up with me in my state of despair 💜💜💜🫠
Thank you for being patient and explaining the situation, it’s always good to help a pleb in need. Please never hesitate to raise issues in the future 🫂🫡
Will do 🫂💜
yay! 🐳🎉😎
i knew nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w would come through! 😁 these clients may still be broken for other blossom implementations or those implementations just ignore mime.. either way, now we know and nostr:npub1cgcwm56v5hyrrzl5ty4vq4kdud63n5u4czgycdl2r3jshzk55ufqe52ndy can get back to yakkin' 🦖 haha
