in reply to eshep

I'm afraid that's the only choice, yes 👍️

Edith says: Oh mastodon.social/@Belledonne_Co… 👀

Guess I was sleeping under a rock. That looks almost… usable.

This entry was edited (Friday, July 31, 2026, 9:48 AM)
in reply to Beko Pharm

@eshep oh ffs, it sure looks good but you do not want to know how much time I'm spending on getting this connected to a gorram Nextcloud CardDAV.

The problem seems to be - after a lot of debugging - that Nextcloud only speaks BASIC AUTH on the DAV endpoint and LinPhone wants DIGEST AUTH.

I'd have to cram a translation proxy inbetween.

FFS. Fancy new UI and the user experience is still like back in 2000 when adding a SIP account. And you do not want to know how often I failed setting this up.

in reply to Beko Pharm

@eshep okay this is rather odd. Turns out it does BASIC AUTH. It just never reached it because it stumbled over the realm we use on the Nextcloud.

This is… I have never seen anything like this. It fails on this specific case with only ASCII characters and a whitespace in the middle - and ONLY for this realm.

"NEXT Cloud" e.g. works. Our 4 characters branding name instead of NEXT failed. Without " Cloud" it worked again.

This is so weird. Wonder what this is doing under the hood.

#linphone

in reply to Beko Pharm

@eshep and to add insult to injury: The auth realm is set in NextCloud under Admin => Design.

Yes that's right. The *name* set under *design* changes the auth realm in #nextcloud

> Auth.php: $this->realm = $defaults->getName() ?: 'Nextcloud';

I swear I'll become a sheep/pony/goat farmer eventually. I just can't do this any more…