decentralization

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

On my phone, when I open a reading progress modal from a menu, the menu stays open and on top of the modal.

Smartphone (please complete the following information):
- Device: Android
- Browser Chromium

Sorry for only getting around to looking at this after it was merged, but I think we should remove the NodeID from the ATX. It was only there when we needed to maintain an identity database - now that we don't, we should derive the public key from the signature and do all validations on that (e.g. that the PoST proof validates with this key and that the key we derived from the previous ATX match

To have the same behaviour as other browsers.

https://github.com/paritytech/sub-flood

And more... What might you add? 😁

This project should contain a Dockerfile that can be run by anyone who's not keen running it natively. Since it's a TUI, it should be possible to run it attached.

Running it in a container also has the benefit that it allows people to restrict IPFS' resource use even further and more strict.

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