Feature request: send snapchat messages to other users

Question

Feature request: send snapchat messages to other users

Opened this issue 11 years ago · 9 comments

Right now sfs can only send snapchat message to your own account. It would be nice to be able to send them to other users.

Answer 1 · 2013-12-24T07:03:06.000Z

How would one go about integrating this into a filesystem? Dropbox, for example, allows you to share a link but only via context menu (not included in the filesystem).

Answer 2 · 2013-12-24T09:01:47.000Z

I think this is sort of an interesting file. A normal upload gives you implicit ownership of the file, but there's no reason this has to be true all the time. You could, for example, encrypt a file, upload it to SFS, and then hand someone else the key, and point them at the ID so that they can download it and decrypt it. The command could take a form like sfs upload --to-user doomrobo file.txt.

So, where a normal upload procedure looks like:

generate an id for the file, and upload it to Snapchat using a POST request to the /bq/upload resource
send a POST request to /bq/send with the file id, which tells Snapchat where to send the file.

And the modified procedure would look like:

generate an id for the file and upload to snapchat as normal.
send a POST to /bq/send for both you and the other user.

Tacking this on is like 5 minutes of work. What do you all think?

Answer 3 · 2013-12-24T17:22:47.000Z

I'm not too familiar with the API. Is it possible to send a snap again after it's already been sent to a user?

Answer 4 · 2013-12-24T21:43:17.000Z

Once you send it off with /bq/send, the media is removed (in the sense that you can't refer to it by media_id alone anymore). If you're really fast you have a few precious seconds because they don't remove it instantly, but aside from making a bot, that's not really useful.

Answer 5 · 2013-12-24T22:58:52.000Z

Interesting. It used to be only the case that /ph/ rather than /bq/ cause deletion.

Will look at it when I get off this infernal plane.
—
Alex (from mobile)

Theory is the first term in the Taylor series of practice. -- Thomas M Cover (1992)

On Tue, Dec 24, 2013 at 2:43 PM, Chris Hansen notifications@github.com
wrote:

Once you send it off with /bq/send, the media is removed (in the sense that you can't refer to it by media_id alone anymore). If you're really fast you have a few precious seconds because they don't remove it instantly, but aside from making a bot, that's not really useful.

Reply to this email directly or view it on GitHub:
#5 (comment)

Answer 6 · 2013-12-24T23:08:20.000Z

I'm unable to resend the same snap by using the same media_id at /bq/send. Normal 200 OK reply with no body content, but there's no side-effect (i.e. I don't get the snap again).
Looks like they've been standardizing /ph/ and /bq/ anyway, and moving slowly away from /ph/, so this makes sense I suppose.

Answer 7 · 2013-12-27T09:36:58.000Z

Huh, weird. Interestingly, I do not have this issue at all. I just tried, and it all works.

Answer 8 · 2013-12-27T09:37:30.000Z

Anyway, @doomrobo why don't we just upload the file twice in that case?

Answer 9 · 2013-12-28T00:56:46.000Z

That's certainly a possibility. It would be inefficient but there doesn't seem to be a way around it.

Once you send it off with /bq/send, the media is removed (in the sense that you can't refer to it by media_id alone anymore). If you're really fast you have a few precious seconds because they don't remove it instantly, but aside from making a bot, that's not really useful.

Once you send it off with `/bq/send`, the media is removed (in the sense that you can't refer to it by media_id alone anymore). If you're really fast you have a few precious seconds because they don't remove it instantly, but aside from making a bot, that's not really useful.