[Solved] Social graph/profile hidden using desktop clients

RedSnt

EDIT: This issue has been solved since it's posting

I'm, like many others, completely new to Mastodon, so there are things that stump me, like how I can't see my profile and anyone else's profile/social graph while using a desktop client like Sengi. I can easily see everyone else's profile and social graph that I see on the federated timeline except everyone on the social.vivaldi.net instance which is weird as I have "Hide yout social graph" option unticked in my profile settings.
So I'm curious to know if this is a Sengi problem or perhaps a social.vivaldi.net instance problem, or perhaps a setting I've overlooked somewhere?

Example of what I mean

Pathduck

@RedSnt Hi - you are discoverable from other instances:

Also from the rest API:

$ curl "https://mastodon.sdf.org/api/v2/search?q=@RedSnt&resolve=false&limit=5"
{"accounts":[{"id":"109363626927054564","username":"RedSnt","acct":"[email protected]","display_name":"RedSnt","locked":false,"bot":false,"discoverable":false,"group":false,"created_at":"2022-11-18T00:00:00.000Z","note":"\u003cp\u003eGen '83, ADD weirdo, recovering idiot. @RedSntDK on Twitter.  \u003c/p\u003e\u003cp\u003e\"None of the evils which totalitarianism claims to remedy is worse than totalitarianism itself.\" - Camus\u003c/p\u003e","url":"https://social.vivaldi.net/@RedSnt","avatar":"https://mastodon.sdf.org/system/cache/accounts/avatars/109/363/626/927/054/564/original/d6cbf91222479a7e.jpeg","avatar_static":"https://mastodon.sdf.org/system/cache/accounts/avatars/109/363/626/927/054/564/original/d6cbf91222479a7e.jpeg","header":"https://mastodon.sdf.org/headers/original/missing.png","header_static":"https://mastodon.sdf.org/headers/original/missing.png","followers_count":0,"following_count":6,"statuses_count":6,"last_status_at":"2022-11-18","emojis":[],"fields":[]}],"statuses":[],"hashtags":[]}

$ curl "https://social.vivaldi.net/api/v2/search?q=@RedSnt&resolve=false&limit=5"
{"accounts":[{"id":"109363181961545665","username":"RedSnt","acct":"RedSnt","display_name":"RedSnt","locked":false,"bot":false,"discoverable":false,"group":false,"created_at":"2022-11-18T00:00:00.000Z","note":"\u003cp\u003eGen \u0026#39;83, ADD weirdo, recovering idiot. @RedSntDK on Twitter.  \u003c/p\u003e\u003cp\u003e\u0026quot;None of the evils which totalitarianism claims to remedy is worse than totalitarianism itself.\u0026quot; - Camus\u003c/p\u003e","url":"https://social.vivaldi.net/@RedSnt","avatar":"https://social-cdn.vivaldi.net/system/accounts/avatars/109/363/181/961/545/665/original/015c0d57f4baee67.jpeg","avatar_static":"https://social-cdn.vivaldi.net/system/accounts/avatars/109/363/181/961/545/665/original/015c0d57f4baee67.jpeg","header":"https://social-cdn.vivaldi.net/headers/original/missing.png","header_static":"https://social-cdn.vivaldi.net/headers/original/missing.png","followers_count":0,"following_count":6,"statuses_count":6,"last_status_at":"2022-11-18","noindex":false,"emojis":[],"fields":[]}],"statuses":[],"hashtags":[]}

* Note: the "discoverable" flag is only for allowing browsing the profiles directory:
https://docs.joinmastodon.org/spec/activitypub/#discoverable
I believe this is a server setting.

I have "Hide yout social graph" option unticked in my profile settings.

I don't think this is related - it just hides followers/following from your profile.

So looks like might be a an issue in your client.

Pathduck

Testing a bit more (because running curl against APIs is fun!)

I signed into and authenticated the Sengi web client at:
https://sengi.nicolas-constant.com

I then searched my own Vivaldi Social account, same result as you.

When clicking the account, the Sengi client sends a search requests for:
@[email protected]
This fails with a 503 error response:
{"error":"Remote data could not be fetched"}

I'm assuming this is because VS uses @vivaldi.net and not the actual instance name which is social.vivaldi.net

Trying the API directly (needs to send auth header):

$ curl -H "authorization: Bearer xxx" "https://social.vivaldi.net/api/v2/search?q=@[email protected]&resolve=true"
{"error":"Remote data could not be fetched"}

$ curl -H "authorization: Bearer xxx" "https://social.vivaldi.net/api/v2/search?q=@[email protected]&resolve=true"
{"accounts":[{"id":"109348563552594074","username":"Pathduck","acct":"Pathduck","display_name":"Pathduck","locked":false,"bot":false,"discoverable":false,"group":false,"created_at":"2022-11-15T00:00:00.000Z","note":"","url":"https://social.vivaldi.net/@Pathduck","avatar":"https://social-cdn.vivaldi.net/system/accounts/avatars/109/348/563/552/594/074/original/f07c39c74d28ba8f.jpeg","avatar_static":"https://social-cdn.vivaldi.net/system/accounts/avatars/109/348/563/552/594/074/original/f07c39c74d28ba8f.jpeg","header":"https://social-cdn.vivaldi.net/system/accounts/headers/109/348/563/552/594/074/original/a22bb32f402d8c17.jpg","header_static":"https://social-cdn.vivaldi.net/system/accounts/headers/109/348/563/552/594/074/original/a22bb32f402d8c17.jpg","followers_count":5,"following_count":8,"statuses_count":7,"last_status_at":"2022-11-19","noindex":false,"emojis":[],"fields":[]}],"statuses":[],"hashtags":[]}

The client needs to get the account URL to display the timeline and this fails if using @social.vivaldi.net but works with @vivaldi.net.

Testing from another Mastodon instance (SDF):

$ curl -H "authorization: Bearer xxx" "https://mastodon.sdf.org/api/v2/search?q=@[email protected]&resolve=true"
{"accounts":[{"id":"109350279908438732","username":"Pathduck","acct":"[email protected]","display_name":"Pathduck","locked":false,"bot":false,"discoverable":false,"group":false,"created_at":"2022-11-15T00:00:00.000Z","note":"","url":"https://social.vivaldi.net/@Pathduck","avatar":"https://mastodon.sdf.org/system/cache/accounts/avatars/109/350/279/908/438/732/original/c6ce8495078da34a.jpeg","avatar_static":"https://mastodon.sdf.org/system/cache/accounts/avatars/109/350/279/908/438/732/original/c6ce8495078da34a.jpeg","header":"https://mastodon.sdf.org/system/cache/accounts/headers/109/350/279/908/438/732/original/ef77ebe597613842.jpg","header_static":"https://mastodon.sdf.org/system/cache/accounts/headers/109/350/279/908/438/732/original/ef77ebe597613842.jpg","followers_count":5,"following_count":8,"statuses_count":6,"last_status_at":null,"emojis":[],"fields":[]}],"statuses":[],"hashtags":[]}

$ curl -H "authorization: Bearer xxx" "https://mastodon.sdf.org/api/v2/search?q=@[email protected]&resolve=true"
{"accounts":[{"id":"109350279908438732","username":"Pathduck","acct":"[email protected]","display_name":"Pathduck","locked":false,"bot":false,"discoverable":false,"group":false,"created_at":"2022-11-15T00:00:00.000Z","note":"","url":"https://social.vivaldi.net/@Pathduck","avatar":"https://mastodon.sdf.org/system/cache/accounts/avatars/109/350/279/908/438/732/original/c6ce8495078da34a.jpeg","avatar_static":"https://mastodon.sdf.org/system/cache/accounts/avatars/109/350/279/908/438/732/original/c6ce8495078da34a.jpeg","header":"https://mastodon.sdf.org/system/cache/accounts/headers/109/350/279/908/438/732/original/ef77ebe597613842.jpg","header_static":"https://mastodon.sdf.org/system/cache/accounts/headers/109/350/279/908/438/732/original/ef77ebe597613842.jpg","followers_count":5,"following_count":8,"statuses_count":6,"last_status_at":null,"emojis":[],"fields":[]}],"statuses":[],"hashtags":[]}

So if it works from another Mastodon instance, looking more like a server misconfiguration here...

RedSnt

I appreciate you spending time on this @Pathduck! Using other apps like TheDesk and Hyperspace local timeline profiles are displayed correctly, so I'll forward this info to the Sengi github .

RedSnt

According to the dev of Sengi in this post on their github issue page, it pretty much confirms Pathduck's suspicions that API requests for looking up profiles checks the wrong subdomain which might be due to an instance configuration error somewhere.
I hope this is of use to the Vivaldi Social guys running the instance

Pathduck

@RedSnt Try reporting a bug with all relevant info:
https://vivaldi.com/bugreport/
(select vivaldi.net)

Not sure there's much they can do if they've already chosen to use the @vivaldi.net but possibly there's a server config they can change somewhere.

I think Mastodon is still kind of new to the Vivaldi team and issues are bound to pop up