defnull / fediwall Goto Github PK

Add config options to change the filter behavior.

• Show boosts (on by default)
• Show posts from bots (on by default)
• Show sensitive content (off by default)
• Show public replies (off by default)

Did I miss anything?

I was wondering if it would be possible to convert post links to one that is local to a defined instance. If I'm running a wall for use by members of my instance, it would ease interactions with posts if posts on the wall would open on our local instance. Ideally this config would be separate from the "servers" entry in the config file, as it can be helpful to pull the wall from a larger instance than one's own.

It would be a good idea to add a simple User-Agent header on the fetch requests sent by this app so that instance owners can identify the app if required.

Add an option to show all treding, local or federated posts from a server. This might help populating an otherwise empty wall.

Longer display names will be cut off - here a scrolling text would be better, so that the name can be displayed completely.

Example: https://jugendforum-nrw.de/fediwall:

A few ideas:

• make the top box customisable e.g. as well as "Show top box" (or hide it), enable the contents to be specified by the administrator / config file
  • I would imagine this could be used to advertise a short URL to reach the web page, for example
• some custom CSS snippets and/or font overrides

There is a link labelled "privacy policy" in the footer of the Fediwall page.

This appears to redirect to the privacy policy page for the first Mastodon instance from the configuration, but there could be several.

I'm not certain how to suggest to resolve this. The implication of having the link is (to me) that this would be the privacy policy for the site in use, i.e. Fediwall; but that site is aggregating public timelines from elsewhere, and content may not be appearing from all of the instances in the configuration list (if there is nothing to show). Worth thinking about.

Allow to configure multiple servers and merge all results (removing duplicates).

Currently, if the config cannot be loaded from a remote source via the ?load parameter, the app falls back to default config, but the user is not told what has happened.

In addition, I don't think that specific instances that may be invalid, reject a connection, or be otherwise badly specified, are called out to the user / marked as bad.