plume-org / plume Goto Github PK

It has been requested many times, and it would be great to have one.

this is what I see on https://baptiste.gelez.xyz/ :

Making Plume Nicer

<p>I started working on a nicer interface for Plume. I'm not designer so it is not perfect, and there is a lot to do (I don't even know if it behaves correctly on mobile for example), ……

it is a preview for the following post: https://baptiste.gelez.xyz/~/PlumeDevelopment/making-plume-nicer/

When a page is not available because the user is not logged in, Rocket sends a 404 page. We should instead redirect to the login page with an explanation.

What we should find on it:

• short description (that may also appear on the homepage)
• longer description
• a link to the admin's profile
• some statistics (number of accounts, posts, connected instances)
• why not the version number

Blog can be created multiple time, by one or multiple persons.
Also even if blog name is slighlty different, one can create a blog with the same in-url name (by using certain chars such as dots or slashes in blog name).
Using the same set of chars it is possible to create a blog which have no in-url name and is thus not accessible (but which is still shown in the dashboard, with an invalid link)

Put post-related methods in PostController.

Using my Plume account, @[email protected], I created a blog here:
https://baptiste.gelez.xyz/~/FederationTesting/.

As you can see at that link, @[email protected] was able to write an article in that blog. I think this might not be what users expect. A blog should probably be private to a user, by default, and the blog owner can allow others to write to the blog.

On error pages, you always have the links to login or create an account, even if you are already logged in.

When redirecting to a url using Redirect::to, if url have a trailing slash, it is striped away. This happen after creating/liking/resharing an article (and maybe somewhere else), and it break links on the page as we use relative links

On page /@/ , the link to followers is pointing to /@/followers instead of /@//followers

We should receive notifications when:

• Someone commented one of our posts
• Someone liked one of our posts
• Someone reshared one of our posts
• Someone started following us

I'm thinking of Facebook, Twitter, Mastodon and Diaspora (and by email?) at least, but there could be others to be included.

It should use the Note object for federation.

• Add a model for reshares
• Add an endpoint to reshare posts
• Add a button to this endpoint
• Handle reshares from other instances
• Send a notification when someone reshares your post
• Display rehsares on the profile

Both at blog and instance level ideally.

I don't know if we should just ask for some CSS, or allow to customize some properties with a form. The former solution would allow more, but it also mean we should remove all url() to avoid any kind of tracking, and that themes could break if we change the HTML markup. The later would let less possibilities, but would also probably mean more coherence and safety (this is what Pleroma does).

Just like in title, it might be challenging, because I haven’t seen any good i18n crate for web, but it’s definitely possible. My Rust knowledge is not enough to start working on it. I will translate the project to Polish when it’s done.

We should allow Markdown to be used when writing posts (and maybe comments?). In the future, it will probably be replaced by a custom format allowing us to style things as we want (for instance positioning images differently), but yet Markdown would allow formatting without having to write HTML directly.

It would be nice if the server software didn't have to make a DB call when someone went to a post's page, but instead rendered as much as possible to static HTML. Having the advantages of static-site generators like Jekyll and friends with the nice-ness of web publishing and federation would be… potentially awesome.

For instance, nothing is displayed here: https://baptiste.gelez.xyz/~/MonBlog/plume-development-comments-are-coming/#comment-54

Reshares may be cancelled, but currently they are not deleted, so you may reshare the same article multiple times (for instance https://baptiste.gelez.xyz/@/[email protected]/)

/configure is currently publicly accessible. This could be a security issue.

I don't even know if Plume behaves correctly on smaller screens…

This crate looks amazing, and I'm sure we would benefit from using it: https://github.com/asonix/activitystreams

The navigation system could really use links for "my blog" and "new post" or something similar. This would really make testing and experimenting with Plume easier!

We should add the possibility to tag an article

See https://github.com/jhass/nodeinfo/blob/master/PROTOCOL.md

I'm thinking about hashtags in text, not tags for articles.

• Parse mentions in Markdown
• Replace them to a link to the corresponding profile
• Fetch this profile if needed
• Add it to the corresponding ActivityPub property
• Send a notification to the mentioned user

For the moment, many informations are not federated, like the summary or the display name.

When responding to a comment, we should display this comment above the text entry.

Else, some links in the templates are broken (the "Comment" one for instance)

Add a page to manage your blogs, and see recent activity on them.

Thanks @JosephKiranBabu for reporting it.

The author is only shown in post lists, not in posts themselves; it could be useful to have their name at the end, at least to remember who wrote it.

• Posts
  • Details
  • List
  • Create
  • Update
  • Delete
• Comments
  • Details
  • List
  • Create
  • Update
  • Delete
• Users
  • Details
  • List
  • Create
  • Update
  • Delete
• Likes
  • Details
  • List
  • Create
  • Update
  • Delete
• Boost
  • Details
  • List
  • Create
  • Update
  • Delete

Naming a post 'new' make it show on recent article list, but it is not accessible as 'new' is also the keyword used to create new articles

Is it really necessary to rely on a nightly build of Rust? I'm afraid this will put many people off.
Please consider making it work with the latest released version instead. Thank you!

It will allow to see them on Mastodon and to comment from there.

I've released my activitypub crate, which re-exports all the needed activitystreams types and traits, while also providing full ActivityPub compatible types.

This means Actors have Inboxes and Outboxes and such.

I think we are unwraping too often, when we could show actual error pages, with a description of the message.

And why not invite only too

from what I see, I think there is currently no mitigation against CSRF (ability to post from another website with a specialy crafted link, without secret cookie knoledge), nor against XSS (run js from untrusted input, maybe even from other instances sending comments)

Especially for the ActivityPub part, but Rocket makes it quite easy to the test the website too: https://github.com/SergioBenitez/Rocket/tree/master/examples/testing

When writing a comment in response to someone, we should make sure they is automatically mentioned at the beginning of the response.