this post was submitted on 10 Jul 2023
64 points (95.7% liked)

Selfhosted

61578 readers
269 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] BrikoX@lemmy.zip 7 points 3 years ago (2 children)
[–] Edo78@feddit.it 5 points 3 years ago (1 children)

I just copy&pasted their README in chatgpt asking for a comparison (so there may be allucinations)

Both PrivateBin and Paaster are "pastebin" tools that allow users to share snippets of text or code online. Both emphasize privacy and security, encrypting data at the local level in the user's browser before sending it to the server. However, there are several key differences between the two services:

  1. Design and User Interface: While PrivateBin self-identifies as a minimalist pastebin, Paaster seems to put an emphasis on user experience, offering features like file drag & drop and a paste history.

  2. Features: Both offer basic features like password protection and the option to delete data after reading, but PrivateBin also offers features like the ability to have anonymous or nicknamed discussions, Markdown formatting support, code syntax highlighting, and the ability to upload files. On the other hand, Paaster offers a paste history feature, PWA support, and i18n.

  3. Trust: PrivateBin warns users not to blindly trust the server administrator, whereas Paaster advises users to either host their service or use a trusted hosting service.

  4. Implementation and Maintenance: Paaster seems more developer-oriented, with API documentation, a CLI tool, and support for Vercel and Docker. PrivateBin, however, also has a developer and installation guide.

  5. Hosting Options: Paaster seems more geared towards self-hosting, with detailed instructions for use with Docker and options for use with external storage services like Amazon S3 and Google Cloud Storage. PrivateBin does not provide specific hosting details in the provided text.

  6. Security: Both use end-to-end encryption, but they use different encryption algorithms. Paaster uses XChaCha20-Poly1305, while PrivateBin uses 256-bit AES in Galois Counter mode.

These are just some of the key differences between the two services. Both have their strengths and unique points, and the choice between the two will depend on the specific needs of the user or organization.

[–] Ward 2 points 3 years ago (1 children)

Surprising good comparison from ChatGPT. Some key points is Paaster does support syntax highlighting & Markdown.

PrivateBin's conversation system isn't encrypted.

[–] Edo78@feddit.it 1 points 3 years ago (1 children)
[–] Ward 1 points 3 years ago (1 children)

Aaah true, yea I was more meaning syntax highlighting for Markdown & not Markdown rendering. Thank you for the correction!

[–] Edo78@feddit.it 2 points 3 years ago

It wasn't meant to be a correction ... I just learned about this project so I'd just want to know more

[–] Ward 3 points 3 years ago

Actually I did a Pros/Cons for Paaster compared to PrivateBin awhile ago here

https://github.com/privacyguides/privacyguides.org/issues/2015

Basically the TL;DR Modern encryption, doesn't expose metadata, modern design (svelte + asyncio python), pwa support, frontend / backend code separation & paste history.