| 8 Mar 2024 |
 Alain | * Federation already handles cases where the profile url is a Link object. I'm not too worried about this platform. Looks like their use case is to identify all URIs that redirect to the actual profile uri. | 21:31:23 |
| Alain | While we're talking about profiles, what was your initial motivation not too include summaries and images (not icons) to the remote profile objects? | 21:34:57 |
 jaywink | No motivation at all, just never implemented. Would be nice to get more profile data synced. It would also require of course Socialhome users being able to set some more profile data, which currently isn't possible. I suppose one possibility would be to define a particular content item to be a "profile summary" or whatever it is called. | 22:36:20 |
| 9 Mar 2024 |
| Alain | I was thinking of simply adding a summary field to the db. Maybe we are saying the same thing? | 19:18:08 |
| jaywink | yep that's probably best 👍️
where would it render in the socialhome UI, in the top bar or as something that looks like a content item? | 19:29:10 |
| Alain | Right, of course some UI changes are required. | 19:46:02 |
| Alain | For the new UI, I'm trying to follow what lostinlight (https://jasonrobinson.me/content/2992034/socialhome-design-concept-long-overdue-but/) suggested a while ago. | 20:02:40 |
| 10 Mar 2024 |
| jaywink | yep so the top bar basically. feel free to go at redesigning where and how the following/followers looks, currently icons in the far right. | 13:06:16 |
| jaywink | for long summaries, potentially a "expand" / "show more" may be better than making the top bar endlessly expand vertically | 13:06:38 |
| jaywink | depends also a lot whether AP platforms allow html in the summary | 13:07:06 |
| jaywink | profile urls like on mastodon would also be nice to have, are they an extension? 🤔 wouldn't probably be too difficult to accommodate either | 13:08:03 |
| jaywink | diaspora btw also has a profile summary, so it should also come in nicely via the federation for those too | 13:08:29 |
| jaywink | it's called bio and is a 65K markdown field: https://diaspora.github.io/diaspora_federation/entities/profile.html
suggest taking that as minimum and if AP platforms support something less, the federation layer should strip things when sending outgoing rather than limit ourselves to pure text or shorter summaries
| 13:09:48 |
| 11 Mar 2024 |
| Alain | 👍️ I'll look into it. | 14:17:57 |
| Alain | In reply to @jaywink:federator.dev
profile urls like on mastodon would also be nice to have, are they an extension? 🤔 wouldn't probably be too difficult to accommodate either They are using schema.org PropertyValue objects which federation currently throws away. | 14:19:04 |
| 12 Mar 2024 |
| Alain | While we're looking at adding some properties to profiles, any suggestions on how to replace image_url_[small,medium,large] with something else? | 22:00:03 |
| Alain | I see this definitely is a Diaspora legacy. For this protocol, maybe keeping only the large image would be workable? | 22:02:13 |
| Alain | * I see this definitely is a Diaspora legacy. For this protocol, maybe keeping only the large image as the profile icon and let the UI resize it when necessary would be workable? | 22:03:54 |
| Alain | That's a lot of changes all over the place. The good news is the current UI doesn't use the medium image. 😉 | 22:05:34 |
| 13 Mar 2024 |
| jaywink | In reply to @alain:zenfolie.org
I see this definitely is a Diaspora legacy. For this protocol, maybe keeping only the large image as the profile icon and let the UI resize it when necessary would be workable? sounds fine to me 👍️ | 20:51:11 |
| 23 Mar 2024 |
| Alain | jaywink: Hey. I've just figured out where the json_context was coming from. Now, I'm scratching my head as to what should replace this (or is it needed) when everything but /index.html is routed through the SPA UI and there are no Django views involved at all. Thoughts? | 22:20:38 |
| jaywink | hmm so afaicr the idea was to provide some initial context for the SPA, to make showing some initial content faster etc. not sure what it is actually used for anymore tho | 23:20:27 |
| jaywink | possibly it used to have the first set of content in it, before it was refactored into just using the API - but not entirely sure | 23:21:05 |
| 25 Mar 2024 |
| Alainchanged room power levels. | 11:40:22 |
| Alainchanged room power levels. | 11:40:22 |
| Alainchanged room power levels. | 11:40:22 |
| Alainchanged room power levels. | 11:40:22 |
| Alainchanged room power levels. | 11:40:22 |
| Alainchanged room power levels. | 11:40:22 |
| Alain | One thing it sends is the stream name, which is then used to derive the API and websocket endpoints. In a case where the UI does all the routing, it's kind of a chicken and egg situation... Since any route URL can be used to derive its corresponding API endpoint, I think the the stream name (which would actually be the channel name) could be included in API serialized responses. | 12:22:05 |
