Hey all,

Today I’ve been working on implementing the inbox. This is still a work in progress, and I have been primarily focused on logic over UI today for this, so I know there’s some issues with it right now. Here is what I know is meh:

  • Only replies are operational right now. You cannot view messages or mentions yet
  • Some comment chains don’t show up when you press on the comment. I’ll work on this tomorrow
  • You are not automatically scrolled to the comment. I’ll work on this tomorrow
  • UI is not optimal. Like I said, this is still a work in progress
  • Some other issues

Also, these fixes are included:

  • Replying to a Kbin message should no longer cause a crash
  • Memory leak that resulted from getting into deeply nested views is fixed
  • Other crashes are fixed

In addition to:

  • A makeshift “fix” in search. If you enter something@something.com, you’ll be presented with the option to either go to that community or go to that user. I’ll make this more friendly in the future.

I also know about one crash that is happening right now as a result of pressing some external links (deep links from what it looks like, i.e. links that should take you to another app). I’ll look into this.

Like I said, this is still a work in progress and I’ll make a lot of changes tomorrow. For now though, you can at least see what’s going on in your inbox. Your “badge” count of replies will refresh every minute, so you can just pull-to-refresh on the inbox screen.

Thanks for all the feedback and support so far.

Happy scrolling!

  • gkd@lemmy.mlOPM
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Users are /u/user (at least on Lemmy, I believe it is the same on Kbin). I am going to implement something where a simple /c/community or /m/community will just link to that community, regardless of whether or not it’s been properly wrapped in markdown.

    And yea, it was not a full implementation. I’m going to handle setting them as read if you visit them. Lemmy itself handles changing the status if you reply to the message, so just need to handle it if you view the message. The button will probably be replaced with a swipe gesture similar to the iOS mail app for making them as read/unread. That was just a placeholder for now.