Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FAQ] Question Rustodon vs Plume #325

Open
cypherbits opened this issue Feb 15, 2020 · 3 comments
Open

[FAQ] Question Rustodon vs Plume #325

cypherbits opened this issue Feb 15, 2020 · 3 comments

Comments

@cypherbits
Copy link

I have a question: Rustodon vs Plume (https://github.com/Plume-org/Plume) ?
Different features? Why not join projects?

@ITwrx
Copy link

ITwrx commented Mar 16, 2020

You may know all of this already, but...Plume is a blogging application. Rustodon is a micro blogging application. Long form posts vs short, tweet/toot-like posts. Different use case. Different consumer of the product output by the applications. IOW, if i connect to a mastodon/pleroma instance/client i'm expecting short posts, not long blog posts. If i connect to plume or someone's blog, i'm not expecting to read only a tweet/toot.

It could be argued that the whole ecosystem should merge the two and have a filter or settings for long vs short, but that's not how things currently are. I suppose some app could start the trend. I don't think there's any restriction in activitypub itself.

@drequivalent
Copy link

drequivalent commented May 13, 2020

I thought this was planned as a drop-in replacement for Mastodon's huge and clumsy backend. I thought wrong, did I?

@ITwrx
Copy link

ITwrx commented May 13, 2020

@drequivalent i hadn't thought about it being backend/server only, but it looks like you may be correct. I was really just trying to address the blogging vs microblogging issue in my previous comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants