I've been working on foursquare photo sharing recently. I've got a version of the site ready to test.
The functionality is very basic: 1. Login/logout 2. Upload photo 3. Send shout with custom text and link to photo url. 4. Add/Remove from favorites 5. Delete photo etc
In the same way you can not checkin to a venue via foursquare's website (checkins via mobile only) I decided against venue checkins on Fspic also. Noone wil be using the website to checkin to a venue, so Fspic.com lets you shout and include a url to the photo you've uploaded (no venue id).
I hope for foursquare mobile applications to integrate with the API (will be complete by friday).
The API is one of the most important features of fspic. The uploadPhoto API method will accept venue_ids and be able to perform venue checkins aswell as text shouts. This makes for a great feature whereby you can see all the photos of a certain venue, and all photos of venues within a certain city. I'll roll these features out once the API sees some integration and we get some photos uploaded that have venue info posted to the API.
I've encountered a problem when it comes to photo comments. Currently, as far as I know, Foursquare uses twitter usernames as their foursquare usernames. If a user hasnt integrated Foursquare the only identifier is their user_id. There is no way to reference a user in a shout. ie. "@Dave cool photo" that goes directly to the user. This whole idea is very twitterish so I don't know really. Interested in your ideas as to how the site should handle photo comments. How will the photographer be notified of the comments?
Note: Commenting on fspic.com isn't properly implemented (as I encountered the problem above). Best to avoid it, but feel free to test the photo upload functionality. upload a photo and give it a test shout.
Interested in feedback, ideas, suggestions! Thanks
(Design subject to change. I know the logo is very similar Foursquare's)
Looks like a good idea, but have you thought about integrating with Foursquare's OAuth login, rather than asking people for their username/password? Also, the 'login' button in your header doesn't work.
> I've been working on foursquare photo sharing recently. I've got a > version of the site ready to test.
> The functionality is very basic: > 1. Login/logout > 2. Upload photo > 3. Send shout with custom text and link to photo url. > 4. Add/Remove from favorites > 5. Delete photo etc
> In the same way you can not checkin to a venue via foursquare's > website (checkins via mobile only) I decided against venue checkins on > Fspic also. Noone wil be using the website to checkin to a venue, so > Fspic.com lets you shout and include a url to the photo you've > uploaded (no venue id).
> I hope for foursquare mobile applications to integrate with the API > (will be complete by friday).
> The API is one of the most important features of fspic. The > uploadPhoto API method will accept venue_ids and be able to perform > venue checkins aswell as text shouts. This makes for a great feature > whereby you can see all the photos of a certain venue, and all photos > of venues within a certain city. I'll roll these features out once the > API sees some integration and we get some photos uploaded that have > venue info posted to the API.
> I've encountered a problem when it comes to photo comments. Currently, > as far as I know, Foursquare uses twitter usernames as their > foursquare usernames. If a user hasnt integrated Foursquare the only > identifier is their user_id. There is no way to reference a user in a > shout. ie. "@Dave cool photo" that goes directly to the user. This > whole idea is very twitterish so I don't know really. > Interested in your ideas as to how the site should handle photo > comments. How will the photographer be notified of the comments?
> Note: Commenting on fspic.com isn't properly implemented (as I > encountered the problem above). Best to avoid it, but feel free to > test the photo upload functionality. upload a photo and give it a test > shout.
> Interested in feedback, ideas, suggestions! Thanks
> (Design subject to change. I know the logo is very similar > Foursquare's) > -- > To post to this group, send email to foursquare-api@googlegroups.com
> Looks like a good idea, but have you thought about integrating with Foursquare's OAuth login, rather than asking people for their username/password? Also, the 'login' button in your header doesn't work.
> ~bck
> On 11/01/2010, at 5:54 AM, Sam wrote:
> > Hi all,
> > I've been working on foursquare photo sharing recently. I've got a > > version of the site ready to test.
> > The functionality is very basic: > > 1. Login/logout > > 2. Upload photo > > 3. Send shout with custom text and link to photo url. > > 4. Add/Remove from favorites > > 5. Delete photo etc
> > In the same way you can not checkin to a venue via foursquare's > > website (checkins via mobile only) I decided against venue checkins on > > Fspic also. Noone wil be using the website to checkin to a venue, so > > Fspic.com lets you shout and include a url to the photo you've > > uploaded (no venue id).
> > I hope for foursquare mobile applications to integrate with the API > > (will be complete by friday).
> > The API is one of the most important features of fspic. The > > uploadPhoto API method will accept venue_ids and be able to perform > > venue checkins aswell as text shouts. This makes for a great feature > > whereby you can see all the photos of a certain venue, and all photos > > of venues within a certain city. I'll roll these features out once the > > API sees some integration and we get some photos uploaded that have > > venue info posted to the API.
> > I've encountered a problem when it comes to photo comments. Currently, > > as far as I know, Foursquare uses twitter usernames as their > > foursquare usernames. If a user hasnt integrated Foursquare the only > > identifier is their user_id. There is no way to reference a user in a > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > whole idea is very twitterish so I don't know really. > > Interested in your ideas as to how the site should handle photo > > comments. How will the photographer be notified of the comments?
> > Note: Commenting on fspic.com isn't properly implemented (as I > > encountered the problem above). Best to avoid it, but feel free to > > test the photo upload functionality. upload a photo and give it a test > > shout.
> > Interested in feedback, ideas, suggestions! Thanks
> > (Design subject to change. I know the logo is very similar > > Foursquare's) > > -- > > To post to this group, send email to foursquare-api@googlegroups.com
> Yeah the OAuth implementation would be much better. I will be doing > this in the future.
> Whole login is borked (my problem - nothing to do with the API), > fixing now.
> -sam
> On Jan 10, 11:36 pm, Brad Kellett <b...@bradkellett.com> wrote:
> > Looks like a good idea, but have you thought about integrating with Foursquare's OAuth login, rather than asking people for their username/password? Also, the 'login' button in your header doesn't work.
> > ~bck
> > On 11/01/2010, at 5:54 AM, Sam wrote:
> > > Hi all,
> > > I've been working on foursquare photo sharing recently. I've got a > > > version of the site ready to test.
> > > The functionality is very basic: > > > 1. Login/logout > > > 2. Upload photo > > > 3. Send shout with custom text and link to photo url. > > > 4. Add/Remove from favorites > > > 5. Delete photo etc
> > > In the same way you can not checkin to a venue via foursquare's > > > website (checkins via mobile only) I decided against venue checkins on > > > Fspic also. Noone wil be using the website to checkin to a venue, so > > > Fspic.com lets you shout and include a url to the photo you've > > > uploaded (no venue id).
> > > I hope for foursquare mobile applications to integrate with the API > > > (will be complete by friday).
> > > The API is one of the most important features of fspic. The > > > uploadPhoto API method will accept venue_ids and be able to perform > > > venue checkins aswell as text shouts. This makes for a great feature > > > whereby you can see all the photos of a certain venue, and all photos > > > of venues within a certain city. I'll roll these features out once the > > > API sees some integration and we get some photos uploaded that have > > > venue info posted to the API.
> > > I've encountered a problem when it comes to photo comments. Currently, > > > as far as I know, Foursquare uses twitter usernames as their > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > identifier is their user_id. There is no way to reference a user in a > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > whole idea is very twitterish so I don't know really. > > > Interested in your ideas as to how the site should handle photo > > > comments. How will the photographer be notified of the comments?
> > > Note: Commenting on fspic.com isn't properly implemented (as I > > > encountered the problem above). Best to avoid it, but feel free to > > > test the photo upload functionality. upload a photo and give it a test > > > shout.
> > > Interested in feedback, ideas, suggestions! Thanks
> > > (Design subject to change. I know the logo is very similar > > > Foursquare's) > > > -- > > > To post to this group, send email to foursquare-api@googlegroups.com
> Yeah the OAuth implementation would be much better. I will be doing > this in the future.
> Whole login is borked (my problem - nothing to do with the API), > fixing now.
> -sam
> On Jan 10, 11:36 pm, Brad Kellett <b...@bradkellett.com> wrote:
> > Looks like a good idea, but have you thought about integrating with Foursquare's OAuth login, rather than asking people for their username/password? Also, the 'login' button in your header doesn't work.
> > ~bck
> > On 11/01/2010, at 5:54 AM, Sam wrote:
> > > Hi all,
> > > I've been working on foursquare photo sharing recently. I've got a > > > version of the site ready to test.
> > > The functionality is very basic: > > > 1. Login/logout > > > 2. Upload photo > > > 3. Send shout with custom text and link to photo url. > > > 4. Add/Remove from favorites > > > 5. Delete photo etc
> > > In the same way you can not checkin to a venue via foursquare's > > > website (checkins via mobile only) I decided against venue checkins on > > > Fspic also. Noone wil be using the website to checkin to a venue, so > > > Fspic.com lets you shout and include a url to the photo you've > > > uploaded (no venue id).
> > > I hope for foursquare mobile applications to integrate with the API > > > (will be complete by friday).
> > > The API is one of the most important features of fspic. The > > > uploadPhoto API method will accept venue_ids and be able to perform > > > venue checkins aswell as text shouts. This makes for a great feature > > > whereby you can see all the photos of a certain venue, and all photos > > > of venues within a certain city. I'll roll these features out once the > > > API sees some integration and we get some photos uploaded that have > > > venue info posted to the API.
> > > I've encountered a problem when it comes to photo comments. Currently, > > > as far as I know, Foursquare uses twitter usernames as their > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > identifier is their user_id. There is no way to reference a user in a > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > whole idea is very twitterish so I don't know really. > > > Interested in your ideas as to how the site should handle photo > > > comments. How will the photographer be notified of the comments?
> > > Note: Commenting on fspic.com isn't properly implemented (as I > > > encountered the problem above). Best to avoid it, but feel free to > > > test the photo upload functionality. upload a photo and give it a test > > > shout.
> > > Interested in feedback, ideas, suggestions! Thanks
> > > (Design subject to change. I know the logo is very similar > > > Foursquare's) > > > -- > > > To post to this group, send email to foursquare-api@googlegroups.com
Looks like you were logging in while I was quickly updating the code. It should be fine now to login and upload a test photo.
The idea is still a bit confusing. Here's the 2 ways I expect the service will be used.
1. Users on the website itself. - They will be able to simply upload a photo and shout it to their friends. Currently doesn't support selecting a venue for the photo (need to research how best to populate fields, get venues etc) - I don't want enormous dropdowns but dont want to run out of API requests with auto-complete text fields. I don't even imagine many Foursquare users will upload photos via the frontend, its more a mobile thing.
2. Users using Foursquare applications on mobile devices (that have integrated fspic's API, once I finalise it this week) - The fspic API will allow venue details to be posted to it. I reckon it's best that photos be uploaded during a checkin. Foursquare is a real-time location service, we want to see where our friends are *right now* , so letting them upload photos of where they were a few days ago, perhaps, isn't really what we're trying to achieve. Users when they find/add their venue and are about to check in should be able to also upload a photo which is sent as a url inside the shout text.
I suppose there's no harm in letting users shout without checking in via mobile devices. People may want to send a few photos throughout the evening that contain venue details but don't trigger a check-in.
Hope this explains things better.
Definitely need to take into consideration the fact that if users can constantly upload photos and shout them, this could generate a lot of activity for their friends. I may want to see the pings from certain users but not the photos. Perhaps a way to: - [X] Show me check-ins - [ ] Show me shouts
... on Foursquare could help combat that potential annoyance.
Thx!
On Jan 11, 1:17 am, blaktivist <blaktiv...@gmail.com> wrote:
> So is the idea that you'd merely be able to tag photos you take at a > venue, irrespective of your checkin? Sort of a bonus to checking in?
> On Jan 10, 5:06 pm, Sam <sam...@gmail.com> wrote:
> > Yeah the OAuth implementation would be much better. I will be doing > > this in the future.
> > Whole login is borked (my problem - nothing to do with the API), > > fixing now.
> > -sam
> > On Jan 10, 11:36 pm, Brad Kellett <b...@bradkellett.com> wrote:
> > > Looks like a good idea, but have you thought about integrating with Foursquare's OAuth login, rather than asking people for their username/password? Also, the 'login' button in your header doesn't work.
> > > ~bck
> > > On 11/01/2010, at 5:54 AM, Sam wrote:
> > > > Hi all,
> > > > I've been working on foursquare photo sharing recently. I've got a > > > > version of the site ready to test.
> > > > The functionality is very basic: > > > > 1. Login/logout > > > > 2. Upload photo > > > > 3. Send shout with custom text and link to photo url. > > > > 4. Add/Remove from favorites > > > > 5. Delete photo etc
> > > > In the same way you can not checkin to a venue via foursquare's > > > > website (checkins via mobile only) I decided against venue checkins on > > > > Fspic also. Noone wil be using the website to checkin to a venue, so > > > > Fspic.com lets you shout and include a url to the photo you've > > > > uploaded (no venue id).
> > > > I hope for foursquare mobile applications to integrate with the API > > > > (will be complete by friday).
> > > > The API is one of the most important features of fspic. The > > > > uploadPhoto API method will accept venue_ids and be able to perform > > > > venue checkins aswell as text shouts. This makes for a great feature > > > > whereby you can see all the photos of a certain venue, and all photos > > > > of venues within a certain city. I'll roll these features out once the > > > > API sees some integration and we get some photos uploaded that have > > > > venue info posted to the API.
> > > > I've encountered a problem when it comes to photo comments. Currently, > > > > as far as I know, Foursquare uses twitter usernames as their > > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > > identifier is their user_id. There is no way to reference a user in a > > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > > whole idea is very twitterish so I don't know really. > > > > Interested in your ideas as to how the site should handle photo > > > > comments. How will the photographer be notified of the comments?
> > > > Note: Commenting on fspic.com isn't properly implemented (as I > > > > encountered the problem above). Best to avoid it, but feel free to > > > > test the photo upload functionality. upload a photo and give it a test > > > > shout.
> > > > Interested in feedback, ideas, suggestions! Thanks
> > > > (Design subject to change. I know the logo is very similar > > > > Foursquare's) > > > > -- > > > > To post to this group, send email to foursquare-api@googlegroups.com
Maybe the service should allow users to select their recent checkins on the site when uploading a photo.
This saves having to pull a list of venues based on autocomplete/long- lat via browser etc
I guess the user could: 1. checkin via official foursquare apps 2. when they visit fspic.com and upload a photo, their most recent checkin venue is listed at the top of a dropdown (of all venues theyve checked into, in order)
Sound good? Or is venue info via the website best to be left out
> Looks like you were logging in while I was quickly updating the code. > It should be fine now to login and upload a test photo.
> The idea is still a bit confusing. Here's the 2 ways I expect the > service will be used.
> 1. Users on the website itself. > - They will be able to simply upload a photo and shout it to their > friends. Currently doesn't support selecting a venue for the photo > (need to research how best to populate fields, get venues etc) - I > don't want enormous dropdowns but dont want to run out of API requests > with auto-complete text fields. > I don't even imagine many Foursquare users will upload photos via the > frontend, its more a mobile thing.
> 2. Users using Foursquare applications on mobile devices (that have > integrated fspic's API, once I finalise it this week) > - The fspic API will allow venue details to be posted to it. I reckon > it's best that photos be uploaded during a checkin. Foursquare is a > real-time location service, we want to see where our friends are > *right now* , so letting them upload photos of where they were a few > days ago, perhaps, isn't really what we're trying to achieve. > Users when they find/add their venue and are about to check in should > be able to also upload a photo which is sent as a url inside the shout > text.
> I suppose there's no harm in letting users shout without checking in > via mobile devices. People may want to send a few photos throughout > the evening that contain venue details but don't trigger a check-in.
> Hope this explains things better.
> Definitely need to take into consideration the fact that if users can > constantly upload photos and shout them, this could generate a lot of > activity for their friends. > I may want to see the pings from certain users but not the photos. > Perhaps a way to: > - [X] Show me check-ins > - [ ] Show me shouts
> ... on Foursquare could help combat that potential annoyance.
> Thx!
> On Jan 11, 1:17 am, blaktivist <blaktiv...@gmail.com> wrote:
> > So is the idea that you'd merely be able to tag photos you take at a > > venue, irrespective of your checkin? Sort of a bonus to checking in?
> > On Jan 10, 5:06 pm, Sam <sam...@gmail.com> wrote:
> > > Yeah the OAuth implementation would be much better. I will be doing > > > this in the future.
> > > Whole login is borked (my problem - nothing to do with the API), > > > fixing now.
> > > -sam
> > > On Jan 10, 11:36 pm, Brad Kellett <b...@bradkellett.com> wrote:
> > > > Looks like a good idea, but have you thought about integrating with Foursquare's OAuth login, rather than asking people for their username/password? Also, the 'login' button in your header doesn't work.
> > > > ~bck
> > > > On 11/01/2010, at 5:54 AM, Sam wrote:
> > > > > Hi all,
> > > > > I've been working on foursquare photo sharing recently. I've got a > > > > > version of the site ready to test.
> > > > > The functionality is very basic: > > > > > 1. Login/logout > > > > > 2. Upload photo > > > > > 3. Send shout with custom text and link to photo url. > > > > > 4. Add/Remove from favorites > > > > > 5. Delete photo etc
> > > > > In the same way you can not checkin to a venue via foursquare's > > > > > website (checkins via mobile only) I decided against venue checkins on > > > > > Fspic also. Noone wil be using the website to checkin to a venue, so > > > > > Fspic.com lets you shout and include a url to the photo you've > > > > > uploaded (no venue id).
> > > > > I hope for foursquare mobile applications to integrate with the API > > > > > (will be complete by friday).
> > > > > The API is one of the most important features of fspic. The > > > > > uploadPhoto API method will accept venue_ids and be able to perform > > > > > venue checkins aswell as text shouts. This makes for a great feature > > > > > whereby you can see all the photos of a certain venue, and all photos > > > > > of venues within a certain city. I'll roll these features out once the > > > > > API sees some integration and we get some photos uploaded that have > > > > > venue info posted to the API.
> > > > > I've encountered a problem when it comes to photo comments. Currently, > > > > > as far as I know, Foursquare uses twitter usernames as their > > > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > > > identifier is their user_id. There is no way to reference a user in a > > > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > > > whole idea is very twitterish so I don't know really. > > > > > Interested in your ideas as to how the site should handle photo > > > > > comments. How will the photographer be notified of the comments?
> > > > > Note: Commenting on fspic.com isn't properly implemented (as I > > > > > encountered the problem above). Best to avoid it, but feel free to > > > > > test the photo upload functionality. upload a photo and give it a test > > > > > shout.
> > > > > (Design subject to change. I know the logo is very similar > > > > > Foursquare's) > > > > > -- > > > > > To post to this group, send email to foursquare-api@googlegroups.com
> Maybe the service should allow users to select their recent checkins > on the site when uploading a photo.
> This saves having to pull a list of venues based on autocomplete/long- > lat via browser etc
> I guess the user could: > 1. checkin via official foursquare apps > 2. when they visit fspic.com and upload a photo, their most recent > checkin venue is listed at the top of a dropdown (of all venues theyve > checked into, in order)
> Sound good? Or is venue info via the website best to be left out
> -Sam
> On Jan 11, 1:41 am, Sam <sam...@gmail.com> wrote:
> > Hi blacktivist,
> > Looks like you were logging in while I was quickly updating the code. > > It should be fine now to login and upload a test photo.
> > The idea is still a bit confusing. Here's the 2 ways I expect the > > service will be used.
> > 1. Users on the website itself. > > - They will be able to simply upload a photo and shout it to their > > friends. Currently doesn't support selecting a venue for the photo > > (need to research how best to populate fields, get venues etc) - I > > don't want enormous dropdowns but dont want to run out of API requests > > with auto-complete text fields. > > I don't even imagine many Foursquare users will upload photos via the > > frontend, its more a mobile thing.
> > 2. Users using Foursquare applications on mobile devices (that have > > integrated fspic's API, once I finalise it this week) > > - The fspic API will allow venue details to be posted to it. I reckon > > it's best that photos be uploaded during a checkin. Foursquare is a > > real-time location service, we want to see where our friends are > > *right now* , so letting them upload photos of where they were a few > > days ago, perhaps, isn't really what we're trying to achieve. > > Users when they find/add their venue and are about to check in should > > be able to also upload a photo which is sent as a url inside the shout > > text.
> > I suppose there's no harm in letting users shout without checking in > > via mobile devices. People may want to send a few photos throughout > > the evening that contain venue details but don't trigger a check-in.
> > Hope this explains things better.
> > Definitely need to take into consideration the fact that if users can > > constantly upload photos and shout them, this could generate a lot of > > activity for their friends. > > I may want to see the pings from certain users but not the photos. > > Perhaps a way to: > > - [X] Show me check-ins > > - [ ] Show me shouts
> > ... on Foursquare could help combat that potential annoyance.
> > Thx!
> > On Jan 11, 1:17 am, blaktivist <blaktiv...@gmail.com> wrote:
> > > So is the idea that you'd merely be able to tag photos you take at a > > > venue, irrespective of your checkin? Sort of a bonus to checking in?
> > > On Jan 10, 5:06 pm, Sam <sam...@gmail.com> wrote:
> > > > Yeah the OAuth implementation would be much better. I will be doing > > > > this in the future.
> > > > Whole login is borked (my problem - nothing to do with the API), > > > > fixing now.
> > > > -sam
> > > > On Jan 10, 11:36 pm, Brad Kellett <b...@bradkellett.com> wrote:
> > > > > Looks like a good idea, but have you thought about integrating with Foursquare's OAuth login, rather than asking people for their username/password? Also, the 'login' button in your header doesn't work.
> > > > > ~bck
> > > > > On 11/01/2010, at 5:54 AM, Sam wrote:
> > > > > > Hi all,
> > > > > > I've been working on foursquare photo sharing recently. I've got a > > > > > > version of the site ready to test.
> > > > > > The functionality is very basic: > > > > > > 1. Login/logout > > > > > > 2. Upload photo > > > > > > 3. Send shout with custom text and link to photo url. > > > > > > 4. Add/Remove from favorites > > > > > > 5. Delete photo etc
> > > > > > In the same way you can not checkin to a venue via foursquare's > > > > > > website (checkins via mobile only) I decided against venue checkins on > > > > > > Fspic also. Noone wil be using the website to checkin to a venue, so > > > > > > Fspic.com lets you shout and include a url to the photo you've > > > > > > uploaded (no venue id).
> > > > > > I hope for foursquare mobile applications to integrate with the API > > > > > > (will be complete by friday).
> > > > > > The API is one of the most important features of fspic. The > > > > > > uploadPhoto API method will accept venue_ids and be able to perform > > > > > > venue checkins aswell as text shouts. This makes for a great feature > > > > > > whereby you can see all the photos of a certain venue, and all photos > > > > > > of venues within a certain city. I'll roll these features out once the > > > > > > API sees some integration and we get some photos uploaded that have > > > > > > venue info posted to the API.
> > > > > > I've encountered a problem when it comes to photo comments. Currently, > > > > > > as far as I know, Foursquare uses twitter usernames as their > > > > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > > > > identifier is their user_id. There is no way to reference a user in a > > > > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > > > > whole idea is very twitterish so I don't know really. > > > > > > Interested in your ideas as to how the site should handle photo > > > > > > comments. How will the photographer be notified of the comments?
> > > > > > Note: Commenting on fspic.com isn't properly implemented (as I > > > > > > encountered the problem above). Best to avoid it, but feel free to > > > > > > test the photo upload functionality. upload a photo and give it a test > > > > > > shout.
> > > > > > (Design subject to change. I know the logo is very similar > > > > > > Foursquare's) > > > > > > -- > > > > > > To post to this group, send email to foursquare-api@googlegroups.com
> I need to investigate an issue with photo resizing - but feel free to > continue testing :)
> -Sam
> On Jan 11, 8:21 am, Sam <sam...@gmail.com> wrote:
> > Maybe the service should allow users to select their recent checkins > > on the site when uploading a photo.
> > This saves having to pull a list of venues based on autocomplete/long- > > lat via browser etc
> > I guess the user could: > > 1. checkin via official foursquare apps > > 2. when they visit fspic.com and upload a photo, their most recent > > checkin venue is listed at the top of a dropdown (of all venues theyve > > checked into, in order)
> > Sound good? Or is venue info via the website best to be left out
> > -Sam
> > On Jan 11, 1:41 am, Sam <sam...@gmail.com> wrote:
> > > Hi blacktivist,
> > > Looks like you were logging in while I was quickly updating the code. > > > It should be fine now to login and upload a test photo.
> > > The idea is still a bit confusing. Here's the 2 ways I expect the > > > service will be used.
> > > 1. Users on the website itself. > > > - They will be able to simply upload a photo and shout it to their > > > friends. Currently doesn't support selecting a venue for the photo > > > (need to research how best to populate fields, get venues etc) - I > > > don't want enormous dropdowns but dont want to run out of API requests > > > with auto-complete text fields. > > > I don't even imagine many Foursquare users will upload photos via the > > > frontend, its more a mobile thing.
> > > 2. Users using Foursquare applications on mobile devices (that have > > > integrated fspic's API, once I finalise it this week) > > > - The fspic API will allow venue details to be posted to it. I reckon > > > it's best that photos be uploaded during a checkin. Foursquare is a > > > real-time location service, we want to see where our friends are > > > *right now* , so letting them upload photos of where they were a few > > > days ago, perhaps, isn't really what we're trying to achieve. > > > Users when they find/add their venue and are about to check in should > > > be able to also upload a photo which is sent as a url inside the shout > > > text.
> > > I suppose there's no harm in letting users shout without checking in > > > via mobile devices. People may want to send a few photos throughout > > > the evening that contain venue details but don't trigger a check-in.
> > > Hope this explains things better.
> > > Definitely need to take into consideration the fact that if users can > > > constantly upload photos and shout them, this could generate a lot of > > > activity for their friends. > > > I may want to see the pings from certain users but not the photos. > > > Perhaps a way to: > > > - [X] Show me check-ins > > > - [ ] Show me shouts
> > > ... on Foursquare could help combat that potential annoyance.
> > > Thx!
> > > On Jan 11, 1:17 am, blaktivist <blaktiv...@gmail.com> wrote:
> > > > So is the idea that you'd merely be able to tag photos you take at a > > > > venue, irrespective of your checkin? Sort of a bonus to checking in?
> > > > On Jan 10, 5:06 pm, Sam <sam...@gmail.com> wrote:
> > > > > Yeah the OAuth implementation would be much better. I will be doing > > > > > this in the future.
> > > > > Whole login is borked (my problem - nothing to do with the API), > > > > > fixing now.
> > > > > -sam
> > > > > On Jan 10, 11:36 pm, Brad Kellett <b...@bradkellett.com> wrote:
> > > > > > Looks like a good idea, but have you thought about integrating with Foursquare's OAuth login, rather than asking people for their username/password? Also, the 'login' button in your header doesn't work.
> > > > > > ~bck
> > > > > > On 11/01/2010, at 5:54 AM, Sam wrote:
> > > > > > > Hi all,
> > > > > > > I've been working on foursquare photo sharing recently. I've got a > > > > > > > version of the site ready to test.
> > > > > > > The functionality is very basic: > > > > > > > 1. Login/logout > > > > > > > 2. Upload photo > > > > > > > 3. Send shout with custom text and link to photo url. > > > > > > > 4. Add/Remove from favorites > > > > > > > 5. Delete photo etc
> > > > > > > In the same way you can not checkin to a venue via foursquare's > > > > > > > website (checkins via mobile only) I decided against venue checkins on > > > > > > > Fspic also. Noone wil be using the website to checkin to a venue, so > > > > > > > Fspic.com lets you shout and include a url to the photo you've > > > > > > > uploaded (no venue id).
> > > > > > > I hope for foursquare mobile applications to integrate with the API > > > > > > > (will be complete by friday).
> > > > > > > The API is one of the most important features of fspic. The > > > > > > > uploadPhoto API method will accept venue_ids and be able to perform > > > > > > > venue checkins aswell as text shouts. This makes for a great feature > > > > > > > whereby you can see all the photos of a certain venue, and all photos > > > > > > > of venues within a certain city. I'll roll these features out once the > > > > > > > API sees some integration and we get some photos uploaded that have > > > > > > > venue info posted to the API.
> > > > > > > I've encountered a problem when it comes to photo comments. Currently, > > > > > > > as far as I know, Foursquare uses twitter usernames as their > > > > > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > > > > > identifier is their user_id. There is no way to reference a user in a > > > > > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > > > > > whole idea is very twitterish so I don't know really. > > > > > > > Interested in your ideas as to how the site should handle photo > > > > > > > comments. How will the photographer be notified of the comments?
> > > > > > > Note: Commenting on fspic.com isn't properly implemented (as I > > > > > > > encountered the problem above). Best to avoid it, but feel free to > > > > > > > test the photo upload functionality. upload a photo and give it a test > > > > > > > shout.
> > > > > > > (Design subject to change. I know the logo is very similar > > > > > > > Foursquare's) > > > > > > > -- > > > > > > > To post to this group, send email to foursquare-api@googlegroups.com
FWIW: It took me a couple of minutes to figure out how someone might be offended by the domain name (I honestly just didn't "get it."). It seems super-obvious to me what the domain actually means. Kinda sucks that there's an undesireable rendering.
- Dan
On Jan 13, 2010, at 11:35 AM, sabernar <sha...@gmail.com> wrote:
>> I need to investigate an issue with photo resizing - but feel free to >> continue testing :)
>> -Sam
>> On Jan 11, 8:21 am, Sam <sam...@gmail.com> wrote:
>>> Maybe the service should allow users to select their recent checkins >>> on the site when uploading a photo.
>>> This saves having to pull a list of venues based on autocomplete/ >>> long- >>> lat via browser etc
>>> I guess the user could: >>> 1. checkin via official foursquare apps >>> 2. when they visit fspic.com and upload a photo, their most recent >>> checkin venue is listed at the top of a dropdown (of all venues >>> theyve >>> checked into, in order)
>>> Sound good? Or is venue info via the website best to be left out
>>> -Sam
>>> On Jan 11, 1:41 am, Sam <sam...@gmail.com> wrote:
>>>> Hi blacktivist,
>>>> Looks like you were logging in while I was quickly updating the >>>> code. >>>> It should be fine now to login and upload a test photo.
>>>> The idea is still a bit confusing. Here's the 2 ways I expect the >>>> service will be used.
>>>> 1. Users on the website itself. >>>> - They will be able to simply upload a photo and shout it to their >>>> friends. Currently doesn't support selecting a venue for the photo >>>> (need to research how best to populate fields, get venues etc) - I >>>> don't want enormous dropdowns but dont want to run out of API >>>> requests >>>> with auto-complete text fields. >>>> I don't even imagine many Foursquare users will upload photos via >>>> the >>>> frontend, its more a mobile thing.
>>>> 2. Users using Foursquare applications on mobile devices (that have >>>> integrated fspic's API, once I finalise it this week) >>>> - The fspic API will allow venue details to be posted to it. I >>>> reckon >>>> it's best that photos be uploaded during a checkin. Foursquare is a >>>> real-time location service, we want to see where our friends are >>>> *right now* , so letting them upload photos of where they were a >>>> few >>>> days ago, perhaps, isn't really what we're trying to achieve. >>>> Users when they find/add their venue and are about to check in >>>> should >>>> be able to also upload a photo which is sent as a url inside the >>>> shout >>>> text.
>>>> I suppose there's no harm in letting users shout without checking >>>> in >>>> via mobile devices. People may want to send a few photos throughout >>>> the evening that contain venue details but don't trigger a check- >>>> in.
>>>> Hope this explains things better.
>>>> Definitely need to take into consideration the fact that if users >>>> can >>>> constantly upload photos and shout them, this could generate a >>>> lot of >>>> activity for their friends. >>>> I may want to see the pings from certain users but not the photos. >>>> Perhaps a way to: >>>> - [X] Show me check-ins >>>> - [ ] Show me shouts
>>>> ... on Foursquare could help combat that potential annoyance.
>>>> Thx!
>>>> On Jan 11, 1:17 am, blaktivist <blaktiv...@gmail.com> wrote:
>>>>> So is the idea that you'd merely be able to tag photos you take >>>>> at a >>>>> venue, irrespective of your checkin? Sort of a bonus to >>>>> checking in?
>>>>> On Jan 10, 5:06 pm, Sam <sam...@gmail.com> wrote:
>>>>>> Yeah the OAuth implementation would be much better. I will be >>>>>> doing >>>>>> this in the future.
>>>>>> Whole login is borked (my problem - nothing to do with the API), >>>>>> fixing now.
>>>>>> -sam
>>>>>> On Jan 10, 11:36 pm, Brad Kellett <b...@bradkellett.com> wrote:
>>>>>>> Looks like a good idea, but have you thought about integrating >>>>>>> with Foursquare's OAuth login, rather than asking people for >>>>>>> their username/password? Also, the 'login' button in your >>>>>>> header doesn't work.
>>>>>>> ~bck
>>>>>>> On 11/01/2010, at 5:54 AM, Sam wrote:
>>>>>>>> Hi all,
>>>>>>>> I've been working on foursquare photo sharing recently. I've >>>>>>>> got a >>>>>>>> version of the site ready to test.
>>>>>>>> The functionality is very basic: >>>>>>>> 1. Login/logout >>>>>>>> 2. Upload photo >>>>>>>> 3. Send shout with custom text and link to photo url. >>>>>>>> 4. Add/Remove from favorites >>>>>>>> 5. Delete photo etc
>>>>>>>> In the same way you can not checkin to a venue via foursquare's >>>>>>>> website (checkins via mobile only) I decided against venue >>>>>>>> checkins on >>>>>>>> Fspic also. Noone wil be using the website to checkin to a >>>>>>>> venue, so >>>>>>>> Fspic.com lets you shout and include a url to the photo you've >>>>>>>> uploaded (no venue id).
>>>>>>>> I hope for foursquare mobile applications to integrate with >>>>>>>> the API >>>>>>>> (will be complete by friday).
>>>>>>>> The API is one of the most important features of fspic. The >>>>>>>> uploadPhoto API method will accept venue_ids and be able to >>>>>>>> perform >>>>>>>> venue checkins aswell as text shouts. This makes for a great >>>>>>>> feature >>>>>>>> whereby you can see all the photos of a certain venue, and >>>>>>>> all photos >>>>>>>> of venues within a certain city. I'll roll these features out >>>>>>>> once the >>>>>>>> API sees some integration and we get some photos uploaded >>>>>>>> that have >>>>>>>> venue info posted to the API.
>>>>>>>> I've encountered a problem when it comes to photo comments. >>>>>>>> Currently, >>>>>>>> as far as I know, Foursquare uses twitter usernames as their >>>>>>>> foursquare usernames. If a user hasnt integrated Foursquare >>>>>>>> the only >>>>>>>> identifier is their user_id. There is no way to reference a >>>>>>>> user in a >>>>>>>> shout. ie. "@Dave cool photo" that goes directly to the user. >>>>>>>> This >>>>>>>> whole idea is very twitterish so I don't know really. >>>>>>>> Interested in your ideas as to how the site should handle photo >>>>>>>> comments. How will the photographer be notified of the >>>>>>>> comments?
>>>>>>>> Note: Commenting on fspic.com isn't properly implemented (as I >>>>>>>> encountered the problem above). Best to avoid it, but feel >>>>>>>> free to >>>>>>>> test the photo upload functionality. upload a photo and give >>>>>>>> it a test >>>>>>>> shout.
>>>>>>>> Interested in feedback, ideas, suggestions! Thanks
>>>>>>>> (Design subject to change. I know the logo is very similar >>>>>>>> Foursquare's) >>>>>>>> -- >>>>>>>> To post to this group, send email to foursquare-api@googlegroups.com
> I've been working on foursquare photo sharing recently. I've got a > version of the site ready to test.
> The functionality is very basic: > 1. Login/logout > 2. Upload photo > 3. Send shout with custom text and link to photo url. > 4. Add/Remove from favorites > 5. Delete photo etc
> In the same way you can not checkin to a venue via foursquare's > website (checkins via mobile only) I decided against venue checkins on > Fspic also. Noone wil be using the website to checkin to a venue, so > Fspic.com lets you shout and include a url to the photo you've > uploaded (no venue id).
> I hope for foursquare mobile applications to integrate with the API > (will be complete by friday).
> The API is one of the most important features of fspic. The > uploadPhoto API method will accept venue_ids and be able to perform > venue checkins aswell as text shouts. This makes for a great feature > whereby you can see all the photos of a certain venue, and all photos > of venues within a certain city. I'll roll these features out once the > API sees some integration and we get some photos uploaded that have > venue info posted to the API.
> I've encountered a problem when it comes to photo comments. Currently, > as far as I know, Foursquare uses twitter usernames as their > foursquare usernames. If a user hasnt integrated Foursquare the only > identifier is their user_id. There is no way to reference a user in a > shout. ie. "@Dave cool photo" that goes directly to the user. This > whole idea is very twitterish so I don't know really. > Interested in your ideas as to how the site should handle photo > comments. How will the photographer be notified of the comments?
> Note: Commenting on fspic.com isn't properly implemented (as I > encountered the problem above). Best to avoid it, but feel free to > test the photo upload functionality. upload a photo and give it a test > shout.
> Interested in feedback, ideas, suggestions! Thanks
> (Design subject to change. I know the logo is very similar > Foursquare's)
I'll be building the /contentByVenueId API method for you ASAP and I'll email the 32x32 icon ASAP. Should I round corners or add a gloss, or do you just want the flat image so you can do what you want with it?
The Fspic iPhone app will be ready within a month so we should start seeing some nice content :)
Thx dude
-Sam
On Feb 22, 4:50 pm, Geoff <fro...@gmail.com> wrote:
> Sam -- I'm ready to integrate this into the webOS client -- just need > 2 things from you:
> - Ability to search all images by venue ID > - a 32x32 icon (simple, similar to other social media icons people use > on blogs)
> On Jan 10, 1:54 pm, Sam <sam...@gmail.com> wrote:
> > Hi all,
> > I've been working on foursquare photo sharing recently. I've got a > > version of the site ready to test.
> > The functionality is very basic: > > 1. Login/logout > > 2. Upload photo > > 3. Send shout with custom text and link to photo url. > > 4. Add/Remove from favorites > > 5. Delete photo etc
> > In the same way you can not checkin to a venue via foursquare's > > website (checkins via mobile only) I decided against venue checkins on > > Fspic also. Noone wil be using the website to checkin to a venue, so > > Fspic.com lets you shout and include a url to the photo you've > > uploaded (no venue id).
> > I hope for foursquare mobile applications to integrate with the API > > (will be complete by friday).
> > The API is one of the most important features of fspic. The > > uploadPhoto API method will accept venue_ids and be able to perform > > venue checkins aswell as text shouts. This makes for a great feature > > whereby you can see all the photos of a certain venue, and all photos > > of venues within a certain city. I'll roll these features out once the > > API sees some integration and we get some photos uploaded that have > > venue info posted to the API.
> > I've encountered a problem when it comes to photo comments. Currently, > > as far as I know, Foursquare uses twitter usernames as their > > foursquare usernames. If a user hasnt integrated Foursquare the only > > identifier is their user_id. There is no way to reference a user in a > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > whole idea is very twitterish so I don't know really. > > Interested in your ideas as to how the site should handle photo > > comments. How will the photographer be notified of the comments?
> > Note: Commenting on fspic.com isn't properly implemented (as I > > encountered the problem above). Best to avoid it, but feel free to > > test the photo upload functionality. upload a photo and give it a test > > shout.
> > Interested in feedback, ideas, suggestions! Thanks
> > (Design subject to change. I know the logo is very similar > > Foursquare's)
You can do the same thing with TweetPhoto and our API. TweetPhoto works with Foursquare OAuth and allows checkins and shoutouts with a photo. You can also search photos by venue ID. We even offer thumbnails for you to embed in your app. Our API has lots more functionality like commenting, favoriting and voting in addition to much much more. Check it out here and let me know if you have any questions.
> I'll be building the /contentByVenueId API method for you ASAP and > I'll email the 32x32 icon ASAP. > Should I round corners or add a gloss, or do you just want the flat > image so you can do what you want with it?
> The Fspic iPhone app will be ready within a month so we should start > seeing some nice content :)
> Thx dude
> -Sam
> On Feb 22, 4:50 pm, Geoff <fro...@gmail.com> wrote:
> > Sam -- I'm ready to integrate this into the webOS client -- just need > > 2 things from you:
> > - Ability to search all images by venue ID > > - a 32x32 icon (simple, similar to other social media icons people use > > on blogs)
> > On Jan 10, 1:54 pm, Sam <sam...@gmail.com> wrote:
> > > Hi all,
> > > I've been working on foursquare photo sharing recently. I've got a > > > version of the site ready to test.
> > > The functionality is very basic: > > > 1. Login/logout > > > 2. Upload photo > > > 3. Send shout with custom text and link to photo url. > > > 4. Add/Remove from favorites > > > 5. Delete photo etc
> > > In the same way you can not checkin to a venue via foursquare's > > > website (checkins via mobile only) I decided against venue checkins on > > > Fspic also. Noone wil be using the website to checkin to a venue, so > > > Fspic.com lets you shout and include a url to the photo you've > > > uploaded (no venue id).
> > > I hope for foursquare mobile applications to integrate with the API > > > (will be complete by friday).
> > > The API is one of the most important features of fspic. The > > > uploadPhoto API method will accept venue_ids and be able to perform > > > venue checkins aswell as text shouts. This makes for a great feature > > > whereby you can see all the photos of a certain venue, and all photos > > > of venues within a certain city. I'll roll these features out once the > > > API sees some integration and we get some photos uploaded that have > > > venue info posted to the API.
> > > I've encountered a problem when it comes to photo comments. Currently, > > > as far as I know, Foursquare uses twitter usernames as their > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > identifier is their user_id. There is no way to reference a user in a > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > whole idea is very twitterish so I don't know really. > > > Interested in your ideas as to how the site should handle photo > > > comments. How will the photographer be notified of the comments?
> > > Note: Commenting on fspic.com isn't properly implemented (as I > > > encountered the problem above). Best to avoid it, but feel free to > > > test the photo upload functionality. upload a photo and give it a test > > > shout.
> > > Interested in feedback, ideas, suggestions! Thanks
> > > (Design subject to change. I know the logo is very similar > > > Foursquare's)
Cool, excited about getting by venueid. Rounded corners are good.
I do need a favor, though.
I do not store usernames and passwords in the webOS app for security reasons. I do store a base64 encoded string of "username:password" (no quotes). Any way I can get support for authorization this way? i.e., instead of passing phone_or_email and password, I would just pass encoded_auth and the other params you normally would. The reason I store it base 64 is it's better than plaintext and it's ready to go in the HTTP headers ("Authorization: Basic jh23jkl4hj34gf434f3g2k4l=").
> I'll be building the /contentByVenueId API method for you ASAP and > I'll email the 32x32 icon ASAP. > Should I round corners or add a gloss, or do you just want the flat > image so you can do what you want with it?
> TheFspiciPhone app will be ready within a month so we should start > seeing some nice content :)
> Thx dude
> -Sam
> On Feb 22, 4:50 pm, Geoff <fro...@gmail.com> wrote:
> > Sam -- I'm ready to integrate this into the webOS client -- just need > > 2 things from you:
> > - Ability to search all images by venue ID > > - a 32x32 icon (simple, similar to other social media icons people use > > on blogs)
> > On Jan 10, 1:54 pm, Sam <sam...@gmail.com> wrote:
> > > Hi all,
> > > I've been working on foursquare photo sharing recently. I've got a > > > version of the site ready to test.
> > > The functionality is very basic: > > > 1. Login/logout > > > 2. Upload photo > > > 3. Send shout with custom text and link to photo url. > > > 4. Add/Remove from favorites > > > 5. Delete photo etc
> > > In the same way you can not checkin to a venue via foursquare's > > > website (checkins via mobile only) I decided against venue checkins on > > >Fspicalso. Noone wil be using the website to checkin to a venue, so > > >Fspic.com lets you shout and include a url to the photo you've > > > uploaded (no venue id).
> > > I hope for foursquare mobile applications to integrate with the API > > > (will be complete by friday).
> > > The API is one of the most important features offspic. The > > > uploadPhoto API method will accept venue_ids and be able to perform > > > venue checkins aswell as text shouts. This makes for a great feature > > > whereby you can see all the photos of a certain venue, and all photos > > > of venues within a certain city. I'll roll these features out once the > > > API sees some integration and we get some photos uploaded that have > > > venue info posted to the API.
> > > I've encountered a problem when it comes to photo comments. Currently, > > > as far as I know, Foursquare uses twitter usernames as their > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > identifier is their user_id. There is no way to reference a user in a > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > whole idea is very twitterish so I don't know really. > > > Interested in your ideas as to how the site should handle photo > > > comments. How will the photographer be notified of the comments?
> > > Note: Commenting onfspic.com isn't properly implemented (as I > > > encountered the problem above). Best to avoid it, but feel free to > > > test the photo upload functionality. upload a photo and give it a test > > > shout.
> > > Interested in feedback, ideas, suggestions! Thanks
> > > (Design subject to change. I know the logo is very similar > > > Foursquare's)
Geoff, check out the foursquare OAuth method, that is the way we are authenticating foursquare users. To use Foursquare OAuth with the TweetPhoto API you will need to share with us your foursquare consumer key and secret. Check this post here to see how it works. It is exactly the same how we are doing it with atwitter OAuth and Facebook Connect.
> Cool, excited about getting by venueid. > Rounded corners are good.
> I do need a favor, though.
> I do not store usernames and passwords in the webOS app for security > reasons. I do store a base64 encoded string of "username:password" (no > quotes). Any way I can get support for authorization this way? i.e., > instead of passing phone_or_email and password, I would just pass > encoded_auth and the other params you normally would. The reason I > store it base 64 is it's better than plaintext and it's ready to go in > the HTTP headers ("Authorization: Basic jh23jkl4hj34gf434f3g2k4l=").
> On Feb 23, 2:33 am, Sam <sam...@gmail.com> wrote:
> > Hi Geoff,
> > I'll be building the /contentByVenueId API method for you ASAP and > > I'll email the 32x32 icon ASAP. > > Should I round corners or add a gloss, or do you just want the flat > > image so you can do what you want with it?
> > TheFspiciPhone app will be ready within a month so we should start > > seeing some nice content :)
> > Thx dude
> > -Sam
> > On Feb 22, 4:50 pm, Geoff <fro...@gmail.com> wrote:
> > > Sam -- I'm ready to integrate this into the webOS client -- just need > > > 2 things from you:
> > > - Ability to search all images by venue ID > > > - a 32x32 icon (simple, similar to other social media icons people use > > > on blogs)
> > > On Jan 10, 1:54 pm, Sam <sam...@gmail.com> wrote:
> > > > Hi all,
> > > > I've been working on foursquare photo sharing recently. I've got a > > > > version of the site ready to test.
> > > > The functionality is very basic: > > > > 1. Login/logout > > > > 2. Upload photo > > > > 3. Send shout with custom text and link to photo url. > > > > 4. Add/Remove from favorites > > > > 5. Delete photo etc
> > > > In the same way you can not checkin to a venue via foursquare's > > > > website (checkins via mobile only) I decided against venue checkins on > > > >Fspicalso. Noone wil be using the website to checkin to a venue, so > > > >Fspic.com lets you shout and include a url to the photo you've > > > > uploaded (no venue id).
> > > > I hope for foursquare mobile applications to integrate with the API > > > > (will be complete by friday).
> > > > The API is one of the most important features offspic. The > > > > uploadPhoto API method will accept venue_ids and be able to perform > > > > venue checkins aswell as text shouts. This makes for a great feature > > > > whereby you can see all the photos of a certain venue, and all photos > > > > of venues within a certain city. I'll roll these features out once the > > > > API sees some integration and we get some photos uploaded that have > > > > venue info posted to the API.
> > > > I've encountered a problem when it comes to photo comments. Currently, > > > > as far as I know, Foursquare uses twitter usernames as their > > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > > identifier is their user_id. There is no way to reference a user in a > > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > > whole idea is very twitterish so I don't know really. > > > > Interested in your ideas as to how the site should handle photo > > > > comments. How will the photographer be notified of the comments?
> > > > Note: Commenting onfspic.com isn't properly implemented (as I > > > > encountered the problem above). Best to avoid it, but feel free to > > > > test the photo upload functionality. upload a photo and give it a test > > > > shout.
> > > > Interested in feedback, ideas, suggestions! Thanks
> > > > (Design subject to change. I know the logo is very similar > > > > Foursquare's)
> Geoff, check out the foursquare OAuth method, that is the way we are > authenticating foursquare users. To use Foursquare OAuth with the > TweetPhoto API you will need to share with us your foursquare consumer > key and secret. Check this post here to see how it works. It is > exactly the same how we are doing it with atwitter OAuth and Facebook > Connect.
> Let me know if you have questions. Feel free to write us directly at > develo...@tweetphoto.com
> Sean
> On Feb 24, 11:39 pm, Geoff <fro...@gmail.com> wrote:
> > Cool, excited about getting by venueid. > > Rounded corners are good.
> > I do need a favor, though.
> > I do not store usernames and passwords in the webOS app for security > > reasons. I do store a base64 encoded string of "username:password" (no > > quotes). Any way I can get support for authorization this way? i.e., > > instead of passing phone_or_email and password, I would just pass > > encoded_auth and the other params you normally would. The reason I > > store it base 64 is it's better than plaintext and it's ready to go in > > the HTTP headers ("Authorization: Basic jh23jkl4hj34gf434f3g2k4l=").
> > On Feb 23, 2:33 am, Sam <sam...@gmail.com> wrote:
> > > Hi Geoff,
> > > I'll be building the /contentByVenueId API method for you ASAP and > > > I'll email the 32x32 icon ASAP. > > > Should I round corners or add a gloss, or do you just want the flat > > > image so you can do what you want with it?
> > > TheFspiciPhone app will be ready within a month so we should start > > > seeing some nice content :)
> > > Thx dude
> > > -Sam
> > > On Feb 22, 4:50 pm, Geoff <fro...@gmail.com> wrote:
> > > > Sam -- I'm ready to integrate this into the webOS client -- just need > > > > 2 things from you:
> > > > - Ability to search all images by venue ID > > > > - a 32x32 icon (simple, similar to other social media icons people use > > > > on blogs)
> > > > On Jan 10, 1:54 pm, Sam <sam...@gmail.com> wrote:
> > > > > Hi all,
> > > > > I've been working on foursquare photo sharing recently. I've got a > > > > > version of the site ready to test.
> > > > > The functionality is very basic: > > > > > 1. Login/logout > > > > > 2. Upload photo > > > > > 3. Send shout with custom text and link to photo url. > > > > > 4. Add/Remove from favorites > > > > > 5. Delete photo etc
> > > > > In the same way you can not checkin to a venue via foursquare's > > > > > website (checkins via mobile only) I decided against venue checkins on > > > > >Fspicalso. Noone wil be using the website to checkin to a venue, so > > > > >Fspic.com lets you shout and include a url to the photo you've > > > > > uploaded (no venue id).
> > > > > I hope for foursquare mobile applications to integrate with the API > > > > > (will be complete by friday).
> > > > > The API is one of the most important features offspic. The > > > > > uploadPhoto API method will accept venue_ids and be able to perform > > > > > venue checkins aswell as text shouts. This makes for a great feature > > > > > whereby you can see all the photos of a certain venue, and all photos > > > > > of venues within a certain city. I'll roll these features out once the > > > > > API sees some integration and we get some photos uploaded that have > > > > > venue info posted to the API.
> > > > > I've encountered a problem when it comes to photo comments. Currently, > > > > > as far as I know, Foursquare uses twitter usernames as their > > > > > foursquare usernames. If a user hasnt integrated Foursquare the only > > > > > identifier is their user_id. There is no way to reference a user in a > > > > > shout. ie. "@Dave cool photo" that goes directly to the user. This > > > > > whole idea is very twitterish so I don't know really. > > > > > Interested in your ideas as to how the site should handle photo > > > > > comments. How will the photographer be notified of the comments?
> > > > > Note: Commenting onfspic.com isn't properly implemented (as I > > > > > encountered the problem above). Best to avoid it, but feel free to > > > > > test the photo upload functionality. upload a photo and give it a test > > > > > shout.
