Fedilab AppsWhat is the most frustrating thing for you with #Fedilab?
PS: We don't talk about current bugs as they will be fixed ASAP.
Der Marek@apps I want to have the timeline to always and directly show full context of a thread. I really don't like the Twitter / Mastodon Style to read text from unknown users and not knowing the context until I click on the message.
In fact I am not using fedilab for this particular reason even if very much appreciate the app and your efforts <3
♲ friendica.mbbit.de/display/b25…
In fact I am not using fedilab for this particular reason even if very much appreciate the app and your efforts <3
♲ friendica.mbbit.de/display/b25…
@[email protected]
As long as API don't bring that information, it will not be possible.
@[email protected]
As long as API don't bring that information, it will not be possible.
@[email protected]
Marek Bachmann@apps @marek Don't get me wrong there: It is not about seeing EVERYthing in the Thread (which is in fact not that simple) but to see the thread from my instance's perspective.
In other words: I just do not want to click on the message to see to whom it was a reply, but I want to see it root post directly with the reply beneath. :-)
In other words: I just do not want to click on the message to see to whom it was a reply, but I want to see it root post directly with the reply beneath. :-)
@apps @marek Here, let me show you what I mean:
This is an exampled of a post what I call "text from unknown users and not knowing the context"
When I click on the message, things start to make sense:
Now I see that this person just replied to that root post, and then AND ONLY THEN, the message makes sense to me. :-)
This is an exampled of a post what I call "text from unknown users and not knowing the context"
When I click on the message, things start to make sense:
Now I see that this person just replied to that root post, and then AND ONLY THEN, the message makes sense to me. :-)
@[email protected]
Yes, it could be done when api will return a "in_reply_message" (object) instead of a "in_reply_id" (String).
@[email protected]
Yes, it could be done when api will return a "in_reply_message" (object) instead of a "in_reply_id" (String).
@[email protected]
@[email protected]
Yes, but as I said, it's a limitation of the API.
The api only returns the reply id and not the reply object.
Such feature cannot be built as for each reply message, the app will have to fetch the message and display it. That would create excessive amount of calls with also jumps when inserted asynchronously.
@[email protected]
Yes, but as I said, it's a limitation of the API.
The api only returns the reply id and not the reply object.
Such feature cannot be built as for each reply message, the app will have to fetch the message and display it. That would create excessive amount of calls with also jumps when inserted asynchronously.
@[email protected]
@apps @marek Okay, thank you for clarification. I will point @developers to this discussion:
kassel.social/display/2c2a1430…
Perhaps we can work out a solution eventually.
All the best
kassel.social/display/2c2a1430…
Perhaps we can work out a solution eventually.
All the best
@[email protected]
Sure, if Friendica implements such feature, it will be implemented immediately with Fedilab.
@developers @[email protected]
Sure, if Friendica implements such feature, it will be implemented immediately with Fedilab.
@developers @[email protected]