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

When the javascript is updates, there are usually a handful of users who experience broken behavior (#1284) because their browser is still working off a cached version of the previous one. I think using https://docs.djangoproject.com/en/3.2/ref/contrib/staticfiles/#django.contrib.staticfiles.storage.ManifestStaticFilesStorage will resolve this?

Description

Right now, we express time in different ways in different modules/sections of the config, e.g.:

        "main": {
                "layer-duration-sec": 300,
                "sync-request-timeout": 60000
        },
        "p2p": {
                "conn-keepalive": "48h",
                "dial-timeout": "1m",
                "response-timeout": "60s",
               

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?

to discuss:

Part 1:
debug=staking:

• to much output for a longer operating in production with debugmode staking, but without, we have too less infos for a minted block and cant monitor chainsplits or rollbacks.
  Proposal: Add following lines to normal Logmode without debug=staking
  **2021-05-05T17:19:45Z MakeStake: kernel found
  2021-05-05T17:19:45Z new proof-of-stake block found hash: 067c

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