Is your feature request related to a problem? Please describe.

It may be hard to understand why a post is in one of our timelines, especially in the case of someone boosting/linking someone else you don't follow, or when the same post appears multiple times because it got boosted.

Describe the solution you'd like

Adding a little "X boosted/liked" indicator to each concerned card

Is your feature request related to a problem? Please describe.
Not related to a problem, but I am curious about the distribution of the books I read wrt to their publishing dates. Other chart could be pages read per month, books read per month etc.

Describe the solution you'd like
A stats page like that in goodreads.
![image](https://user-images.githubusercontent.com/22823026/1152656

In #2299 we patched the API to return the current (tip) layer rather than statically returning the first layer of the third epoch as the current layer. But this still isn't really accurate. What we really want is for the API to instead return the latest synced layer. This information is currently not exposed to the API, but it could be, and it definitely lives in the sync code somewhere, since s

I kinda miss knowing what I'm about to open by hovering over it.

Maybe we could have it display in the URL bar temporarily over top of the input when hovering?

Are there events we can listen on for this?

This will need new RPC events sent to and handled by windows. Maybe link-hover and link-blur with the URL of the link?

Expected Behaviour

Github Actions should run existing integration tests successfully on windows-latest machine

Actual Behaviour

Integrations tests run on the windows-latest operating systems are failing.

Extra Information

Here is a CI run that failed: https://github.com/FleekHQ/space-daemon/runs/1524767049?check_suite_focus=true

The issue appears to be with a wrong `Ipfsnode

Right now it's uploads/<item>/<username slug> with the username slug being prefixed with remote_ if remote user.

That might cause an issue because foo@instance1 and foo@instance will have the same folder name.

Solution: uses the user flake id instead of slug for everybody, but keep the remote_ part