Recent activity
Subscribe to this feed
Utils replied on October 01, 2009 20:57 to the problem "Unable to setup pages in Facebook for ping" in Ping.fm:
I'm not following this problem anymore. Every time someone new complains about it they come back later saying they solved it by following directions—INCLUDING MYSELF SEVERAL MONTHS AGO!
Good luck to the ping.fm staff getting people to follow directions. Frankly, Facebook is also to blame with their convoluted setup procedure.
Utils replied on September 18, 2009 20:57 to the question "Is it possible to upload photos to MySpace with the Title intact?" in Ping.fm:
A comment on the problem ""We couldn't parse this feed" for valid url / feed" in twitterfeed:
For a one-man team Mario's support is awesome and QUICK I might add. I tried hootsuite, for what I need twitterfeed is way ahead of it. – Utils, on September 18, 2009 20:55
Utils replied on September 18, 2009 20:51 to the problem "FlickrExport recompresses your photos. Choosing Maximum Quality will actually create a BIGGER photo than your original." in Connected Flow:
"Flickr Uploadr and the web form don't work this way because they're not iPhoto plugins."
No kidding! Really?
Ugh. My point in bringing that up was to exemplify that uploading files 1:1 is NOT an API restriction. I think you knew that and were trying to be funny or condescending. Perhaps both?
In any event, if you take a look at iP2F, you'll see that files are uploaded 1:1 with NO COMPRESSION. You can find it here: http://www.tagtraum.com/ip2f.html
It doesn't have the convenience features of your program (mostly tagging stuff) but what's the point of using it when it sends gimped versions of my photos to flickr?
I'll most likely be purchasing iP2F when the trial is over. I'm just really surprised this basic functionality is missing.
I'm even more shocked to find out the built-in iPhoto flickr plugin doesn't upload photos 1:1 but at least it doesn't make images BIGGER than the originals like your program. That's just insane!
Since finding out about this whole thing I don't think I'll be using the flickr photo sync in iPhoto anymore. Maybe there will be a way to work around this mess when iPhoto Library Manager ( http://www.fatcatsoftware.com/iplm/ ) finally adds support for flickr albums. Then I can upload with iP2F and sync with iPhoto Library Manager.
Flickery ( http://www.flickeryapp.com/ ) is another app I have my eye on my it's of no use to me since you can't export with meta data from iPhoto.
A comment on the question "Resizing to Flickr using Flickrexport" in Connected Flow:
Yeah, I encourage you to have a look at iP2F. Somehow they manage to export 1:1 identical files to flickr. Also the built-in file exporter (non flickr) supports exporting original files as well.
You've may have overlooked something somewhere.
Check it out: http://www.tagtraum.com/ip2f.html – Utils, on September 18, 2009 20:37
A comment on the problem "Snow Leopard Error" in Xmarks:
Aaron could I possibly ask you to address a problem in iPhoto that's gone unresolved? – Utils, on September 18, 2009 02:54
Utils reported a problem in Connected Flow on September 18, 2009 01:00:
FlickrExport recompresses your photos. Choosing Maximum Quality will actually create a BIGGER photo than your original.I'm glad there was a trial option because I wouldn't pay for this unless there was a way to make it LEAVE MY PHOTOS ALONE. Don't touch them. Don't compress them. Don't resize them. Just UPLOAD them.
Even the flickr uploadr and web forms can do this without a problem. Compare the original to the uploaded versions after using either of them and you'll see the files are exactly the same. You can't blame this on the API.
How is it that nobody's brought up this major flaw?
It's a shame because I'm looking for a product that can take the meta data I have in iPhoto and upload it to flickr with the photo WITHOUT RUINING IT. IPhoto doesn't do that, it ALSO recompresses prior to upload. What's the game here? I don't get it.
Utils replied on September 17, 2009 23:32 to the question "Resizing to Flickr using Flickrexport" in Connected Flow:
Utils replied on September 04, 2009 22:16 to the idea "Will Flock be supporting OpenSearch Autodiscovery at any point in the future?" in Flock:
Okay, so I was partly wrong. There IS support for adding search plugins like from Mycroft Project. In fact your search provider page handles it the same way.
But it would be nice to have OpenSearch Autodiscovery.
Understand that not everyone puts their search plugins on Mycroft.
A comment on the problem "Unable to setup pages in Facebook for ping" in Ping.fm:
Scroll up. I followed the wiki directions and had it working months ago. In fact there's even a screenshot on this page with the the 'grant permissions' link from the wiki. :| – Utils, on August 30, 2009 17:25
A comment on the problem "Ping.fm site not showing pictures on IE for Windows Mobile 6" in Ping.fm:
I send an e-mail to both myspace and flick. And flickr posts the photo link to twitter. Also when you e-mail myspace they use the title from your e-mail. Bonus! – Utils, on August 30, 2009 16:42
Utils replied on August 30, 2009 16:40 to the problem "Unable to setup pages in Facebook for ping" in Ping.fm:
Utils shared an idea in Flock on August 30, 2009 16:04:
Will Flock be supporting OpenSearch Autodiscovery at any point in the future?Will Flock be supporting OpenSearch Autodiscovery at any point in the future? Firefox 3, 3.5 have it built-in. Even IE 8 supports it.
Reference: http://www.opensearch.org/Specifications/OpenSearch/1.1#Autodiscovery_in_HTML.2FXHTML
It's nice that you supply this page but understand that compared to the rest of the World Wide Web that's barely enough. Not even Mycroft Project has everything.-
Utils started following the idea "Allow already short links to Twitter without conversion via tinyurl etc." in twitterfeed.
-
Utils started following the idea "Adding short URL only if message length exceeds twitter 140 characters limit" in twitterfeed.
Utils replied on August 28, 2009 07:48 to the problem ""We couldn't parse this feed" for valid url / feed" in twitterfeed:
I may have spoke too soon. After adding the feed above I left twitterfeed. I came back a short while later and on the list page the feed I was talking about displays an alert icon with this message: "we couldn't parse this feed, please check the URL is valid. we'll keep trying."
The thing about these feeds is that they parse on the edit page but I guess the list page is a different story. Hmmm.
Utils replied on August 28, 2009 07:30 to the problem ""We couldn't parse this feed" for valid url / feed" in twitterfeed:
Utils replied on August 28, 2009 06:13 to the problem ""We couldn't parse this feed" for valid url / feed" in twitterfeed:
I'm getting the "We couldn't parse this feed" issue. I'm using Yahoo pipes. Here's the feed URL:
http://pipes.yahoo.com/pipes/pipe.run...
Oddly enough, when I go to edit other RSS feeds on my list and click "test rss feed" I get the exact same message. But THOSE feeds have all green check marks. And those same feeds are all from Y! pipes.-
Utils started following the problem ""We couldn't parse this feed" for valid url / feed" in twitterfeed.
A comment on the problem "Ping.fm site not showing pictures on IE for Windows Mobile 6" in Ping.fm:
I've got nothing but love for Adam, Cadill. But I'm also truthful. When your friend makes you dinner and it's terrible do you lie and tell them you enjoyed it or are you honest with them? Same deal.
Those media pages are a black hole. At least with twitpic it's very obvious that you can comment on the photo and your followers will see a link to your photo and thus the photo growls virally. The ping.fm pages are a blackhole so that type of thing is impossible. People look, close the browser, then leave.
But hey, I don't use Ping.fm for that anymore. :) – Utils, on August 21, 2009 09:07
| next » « previous |
Loading Profile...






