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

standalone web service #1

Open
npdoty opened this Issue Jun 22, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@npdoty
Owner

npdoty commented Jun 22, 2016

For people who can't easily install extra code on their domain, we should set up a standalone service at its own domain that will create ephemerurls for any URL on the Web. (h/t @sbenthall)

While the primary use case is not to allow people to make ephemeral links to content they don't have any control over, that doesn't seem like a serious abuse, and it would have the benefit of letting people make ephemeral links to content they authored but where they don't have the access to or don't to install code on the server itself.

@sbenthall

This comment has been minimized.

Show comment
Hide comment
@sbenthall

sbenthall Jun 22, 2016

Expanding on the use case, there are pastebins with 'secret' but permanent URLs that you could share ephemerally with your service.

https://gist.github.com/

sbenthall commented Jun 22, 2016

Expanding on the use case, there are pastebins with 'secret' but permanent URLs that you could share ephemerally with your service.

https://gist.github.com/

@npdoty

This comment has been minimized.

Show comment
Hide comment
@npdoty

npdoty Jun 22, 2016

Owner

it's like perma.cc, except the opposite

Owner

npdoty commented Jun 22, 2016

it's like perma.cc, except the opposite

@elsehow

This comment has been minimized.

Show comment
Hide comment
@elsehow

elsehow Jul 5, 2016

This could be done pretty simply with a persistent kv store. Keys represent the shortened URLs, and values represent the real URLs. Then we just need some service that deletes things from the kv store at the right times.

As an added bonus, it wouldn't require any client-side JS.

elsehow commented Jul 5, 2016

This could be done pretty simply with a persistent kv store. Keys represent the shortened URLs, and values represent the real URLs. Then we just need some service that deletes things from the kv store at the right times.

As an added bonus, it wouldn't require any client-side JS.

@npdoty

This comment has been minimized.

Show comment
Hide comment
@npdoty

npdoty Jul 5, 2016

Owner

Yeah, for the current self-hosted version, you just set up a sqlite database with the url, the random short string and an expiration. Client-side JavaScript is just an optional value at the target URL which reminds the user to please share only the ephemeral URL.

@elsehow, did you have a particular key-value store in mind that's better than sqlite-on-a-server-somewhere?

Owner

npdoty commented Jul 5, 2016

Yeah, for the current self-hosted version, you just set up a sqlite database with the url, the random short string and an expiration. Client-side JavaScript is just an optional value at the target URL which reminds the user to please share only the ephemeral URL.

@elsehow, did you have a particular key-value store in mind that's better than sqlite-on-a-server-somewhere?

@elsehow

This comment has been minimized.

Show comment
Hide comment
@elsehow

elsehow Jul 5, 2016

I use leveldb and cousins, but I'm sure any KV store will do.

elsehow commented Jul 5, 2016

I use leveldb and cousins, but I'm sure any KV store will do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment