Error when encountering relative URLs, after logging in

[vadorovsky]

I'm seeing this error every time I'm trying to access the main "Home" view, after I logged in to my Mastodon instance (infosec.exchange). I've never managed to load the "Home" view successfully after logging in.

timeline-0-https://infosec.exchange

thread 'tokio-runtime-worker' panicked at src/subscriptions/home.rs:18:22:
called `Result::unwrap()` on an `Err` value: Serde(Error("invalid value: string \"/autor/Dirk-Knop-3629568\", expected a URL string or the empty string", line: 1, column: 34255))
stack backtrace:
   0: __rustc::rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: <futures_util::stream::once::Once<Fut> as futures_core::stream::Stream>::poll_next
   4: <futures_util::stream::select::Select<St1,St2> as futures_core::stream::Stream>::poll_next
   5: <futures_util::stream::stream::map::Map<St,F> as futures_core::stream::Stream>::poll_next
   6: <futures_util::stream::stream::map::Map<St,F> as futures_core::stream::Stream>::poll_next
   7: <futures_util::stream::stream::map::Map<St,F> as futures_core::stream::Stream>::poll_next
   8: <futures_util::future::select::Select<A,B> as core::future::future::Future>::poll
   9: iced_futures::subscription::tracker::Tracker::update::{{closure}}
  10: tokio::runtime::task::raw::poll
  11: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  12: tokio::runtime::scheduler::multi_thread::worker::Context::run
  13: tokio::runtime::context::scoped::Scoped<T>::set
  14: tokio::runtime::context::runtime::enter_runtime
  15: tokio::runtime::scheduler::multi_thread::worker::run
  16: tokio::runtime::task::core::Core<T,S>::poll
  17: tokio::runtime::task::harness::Harness<T,S>::poll
  18: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

It seems like there are some relative URLs (e.g. /autor/Dirk-Knop-3629568) in local toots and toot expects full URLs there. I will dig deeper and try to come up with a fix.