@heluecht
Yes sure, thank you!
@marek@friendica.mbbit.de @marek@kassel.social
Notices by Fedilab Apps (apps@toot.fedilab.app)
-
Fedilab Apps (apps@toot.fedilab.app)'s status on Tuesday, 24-Jan-2023 00:14:27 CET Fedilab Apps -
Fedilab Apps (apps@toot.fedilab.app)'s status on Monday, 23-Jan-2023 19:54:30 CET Fedilab Apps @heluecht
Could this be limited to first sibling?
@marek@friendica.mbbit.de @marek@kassel.social -
Fedilab Apps (apps@toot.fedilab.app)'s status on Monday, 23-Jan-2023 19:53:56 CET Fedilab Apps @heluecht
Currently, in_reply_to_id is just a string targeting a message by its ID.
Instead of this ID, attaching the whole object message would avoid the extra call from client side to get the message.
@marek@friendica.mbbit.de @marek@kassel.social -
Fedilab Apps (apps@toot.fedilab.app)'s status on Monday, 23-Jan-2023 19:45:49 CET Fedilab Apps @marek
What do you mean? -
Fedilab Apps (apps@toot.fedilab.app)'s status on Monday, 23-Jan-2023 19:45:49 CET Fedilab Apps What is the most frustrating thing for you with #Fedilab?
PS: We don't talk about current bugs as they will be fixed ASAP.
-
Fedilab Apps (apps@toot.fedilab.app)'s status on Monday, 23-Jan-2023 19:45:47 CET Fedilab Apps @marek@friendica.mbbit.de
Yes, it could be done when api will return a "in_reply_message" (object) instead of a "in_reply_id" (String).
@marek@kassel.social -
Fedilab Apps (apps@toot.fedilab.app)'s status on Monday, 23-Jan-2023 19:45:47 CET Fedilab Apps @marek@kassel.social
As long as API don't bring that information, it will not be possible.
@marek@friendica.mbbit.de