3 ms·

Incidentally, I launched a pastebin (https://ghostbin.com/ https://ghostbin.com/) some time ago, used Persona for authentication, and absolutely loved it. Past

by DHowett 11y ago

Incidentally, I launched a pastebin (https://ghostbin.com/ https://ghostbin.com/) some time ago, used Persona for authentication, and absolutely loved it. Pastery looks awesome. It appears that you're using Pygments server-side?

rsync 11y ago
Serious question for you and your parent: Why would a pastebin site need auth/login/userids ? All I can think of is editing pastes, but isn't it easier to just create a new (anonymous) paste instead of editing ?
- lotyrin 11y ago
  Deletion. Modification of pastes and maintaining the same id (URL). Though, these can be solved with tokens per post, it's tough to remember/maintain multiple tokens, doesn't work out in practice.
- DHowett 11y ago
  They're primarily for content ownership management. I'd prefer not to have accounts, and Ghostbin tries to avoid keeping identifiable information around, but they do come in fairly handy for maintaining control of the things you've pasted and the right to revoke them. Session cookies aren't quite up to the task, since they can't stick around forever and are difficult to bring with you between workspaces. (edit to elaborate on "avoid keeping identifiable information": account names are hashed, the account never stores user identification, and a paste doesn't track which account created it. For most intents and many purposes, the creator of a paste is anonymous. We could get into drawing correlations between all the pastes owned by an account, but I'm not particularly interested in sitting around and doing that.)
- r-w 11y ago
  Preventing inundation with pastes. This is less of a problem for a small project like this compared to one of the major sites, whose server architecture is probably more robust.
StavrosK 11y ago
That looks fantastic! I love what you've done with the UI. We do use Pygments, yep, same as you, looks like :) I don't think I'd have started Pastery if I'd seen Ghostbin, as I was looking for a pastebin that wasn't ugly, and I hadn't found any that qualified. Have you had any abuse problems at all?

by DHowett 11y ago

rsync 11y ago

Serious question for you and your parent: Why would a pastebin site need auth/login/userids ? All I can think of is editing pastes, but isn't it easier to just create a new (anonymous) paste instead of editing ?

lotyrin 11y ago
Deletion. Modification of pastes and maintaining the same id (URL). Though, these can be solved with tokens per post, it's tough to remember/maintain multiple tokens, doesn't work out in practice.
DHowett 11y ago
They're primarily for content ownership management. I'd prefer not to have accounts, and Ghostbin tries to avoid keeping identifiable information around, but they do come in fairly handy for maintaining control of the things you've pasted and the right to revoke them. Session cookies aren't quite up to the task, since they can't stick around forever and are difficult to bring with you between workspaces. (edit to elaborate on "avoid keeping identifiable information": account names are hashed, the account never stores user identification, and a paste doesn't track which account created it. For most intents and many purposes, the creator of a paste is anonymous. We could get into drawing correlations between all the pastes owned by an account, but I'm not particularly interested in sitting around and doing that.)
r-w 11y ago
Preventing inundation with pastes. This is less of a problem for a small project like this compared to one of the major sites, whose server architecture is probably more robust.

StavrosK 11y ago

That looks fantastic! I love what you've done with the UI. We do use Pygments, yep, same as you, looks like :) I don't think I'd have started Pastery if I'd seen Ghostbin, as I was looking for a pastebin that wasn't ugly, and I hadn't found any that qualified. Have you had any abuse problems at all?