Hi,
I just took the opportunity to check out ForeignApiRepo, aka InstantCommons alpha. It's pretty sweet. http://modernthings.org/mwfresh/index.php?title=User:Pfctdayelise I did a little dance when it really and truly worked!
http://www.mediawiki.org/wiki/Manual:$wgForeignFileRepos#Using_files_from_Wikimedia_Commons_:_ForeignAPIRepo only says "keep in mind that you are hotlinking images from another site", and to somehow cache images locally if you have "a lot of visitors". Any suggestions on what a threshold for "a lot" is? Is some future development on this intended to have a local-caching option?
Is there any way for Wikimedia Commons users/admins to tell that an image is being used in this way? (I'm guessing not since we are still waiting for this native functionality for the Wikimedia universe...) Could some kind of filtered data log be made available perhaps via the toolserver so that we (community) can build a tool to check this? While I doubt third-party users would be a high priority for Commoners, it's still nice to avoid upsetting people by unexpectedly deleting their images if at all possible.
Which brings me to again another problem still existing within Wikimedia, how the local party can be informed of changes (overwrite uploads and deletions) to images that they are using via this method.
Is this maybe the kind of thing we should require people to register a key of some kind for? Then we would have a way of knowing how popular it is.
So, basically I would be interested to hear what the future plans for development for this will be.
thanks Brianna
On Tue, Nov 4, 2008 at 11:39 AM, Brianna Laugher brianna.laugher@gmail.comwrote:
Hi,
I just took the opportunity to check out ForeignApiRepo, aka InstantCommons alpha. It's pretty sweet. http://modernthings.org/mwfresh/index.php?title=User:Pfctdayelise I did a little dance when it really and truly worked!
< http://www.mediawiki.org/wiki/Manual:$wgForeignFileRepos#Using_files_from_Wi...
only says "keep in mind that you are hotlinking images from another site", and to somehow cache images locally if you have "a lot of visitors". Any suggestions on what a threshold for "a lot" is? Is some future development on this intended to have a local-caching option?
Is there any way for Wikimedia Commons users/admins to tell that an image is being used in this way? (I'm guessing not since we are still waiting for this native functionality for the Wikimedia universe...) Could some kind of filtered data log be made available perhaps via the toolserver so that we (community) can build a tool to check this? While I doubt third-party users would be a high priority for Commoners, it's still nice to avoid upsetting people by unexpectedly deleting their images if at all possible.
Which brings me to again another problem still existing within Wikimedia, how the local party can be informed of changes (overwrite uploads and deletions) to images that they are using via this method.
Is this maybe the kind of thing we should require people to register a key of some kind for? Then we would have a way of knowing how popular it is.
So, basically I would be interested to hear what the future plans for development for this will be.
thanks Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Short of adding some extra queries to see if a file was deleted (remember, all queries here are to a foreign site over their API, not a local database), I'm not really sure how you could easily get this information to the end-users, unfortunate though it is. The only thing I could suggest would be to add a dedicated API module that delivers all of the exact information we need on the client end in one nice big query, but ew :(
Future plans? Make caching in general not suck, and have the local thumb cache better integrated with the normal thumb path construction, it's a bit (read: very) haphazard right now. I'm not sure if it's still the case, but I know Betawiki was running the ForeignApiRepo live at one point, pointed at Commons.
-Chad
Hoi, Betawiki is still running this. I have added one of my favourite photos to my user page there. Not the pig for a change... Thanks, GerardM
http://translatewiki.net/wiki/User:GerardM
On Tue, Nov 4, 2008 at 9:19 PM, Chad innocentkiller@gmail.com wrote:
On Tue, Nov 4, 2008 at 11:39 AM, Brianna Laugher brianna.laugher@gmail.comwrote:
Hi,
I just took the opportunity to check out ForeignApiRepo, aka InstantCommons alpha. It's pretty sweet. http://modernthings.org/mwfresh/index.php?title=User:Pfctdayelise I did a little dance when it really and truly worked!
<
http://www.mediawiki.org/wiki/Manual:$wgForeignFileRepos#Using_files_from_Wi...
only says "keep in mind that you are hotlinking images from another site", and to somehow cache images locally if you have "a lot of visitors". Any suggestions on what a threshold for "a lot" is? Is some future development on this intended to have a local-caching option?
Is there any way for Wikimedia Commons users/admins to tell that an image is being used in this way? (I'm guessing not since we are still waiting for this native functionality for the Wikimedia universe...) Could some kind of filtered data log be made available perhaps via the toolserver so that we (community) can build a tool to check this? While I doubt third-party users would be a high priority for Commoners, it's still nice to avoid upsetting people by unexpectedly deleting their images if at all possible.
Which brings me to again another problem still existing within Wikimedia, how the local party can be informed of changes (overwrite uploads and deletions) to images that they are using via this method.
Is this maybe the kind of thing we should require people to register a key of some kind for? Then we would have a way of knowing how popular it is.
So, basically I would be interested to hear what the future plans for development for this will be.
thanks Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Short of adding some extra queries to see if a file was deleted (remember, all queries here are to a foreign site over their API, not a local database), I'm not really sure how you could easily get this information to the end-users, unfortunate though it is. The only thing I could suggest would be to add a dedicated API module that delivers all of the exact information we need on the client end in one nice big query, but ew :(
Future plans? Make caching in general not suck, and have the local thumb cache better integrated with the normal thumb path construction, it's a bit (read: very) haphazard right now. I'm not sure if it's still the case, but I know Betawiki was running the ForeignApiRepo live at one point, pointed at Commons.
-Chad _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
2008/11/5 Chad innocentkiller@gmail.com:
Short of adding some extra queries to see if a file was deleted (remember, all queries here are to a foreign site over their API, not a local database), I'm not really sure how you could easily get this information to the end-users, unfortunate though it is. The only thing I could suggest would be to add a dedicated API module that delivers all of the exact information we need on the client end in one nice big query, but ew :(
Indeed.
In the long term perhaps we need to set up a more sophisticated and robust version of CommonsTicker http://meta.wikimedia.org/wiki/User:Duesentrieb/CommonsTicker. When using the ForeignAPIRepo the wiki administrator could perhaps subscribe to an RSS/email feed of notifications relevant to their wiki.
Weirdly CommonsTicker is not hugely popular today, I think. Maybe because of delinker bots such as CommonsDelinker. OK, so another idea: Run a delinking/notification bot service that third parties can subscribe to, where they request/allow a bot to make edits in their wiki to remove deleted images and maybe put warning or notices on image pages for nominated-for-deletion images.
I really hope consideration is given to this, about how to run it so that it doesn't kill Wikimedia servers and also makes sense for third parties, because it is the most perfect way for Wikimedia Commons to distribute its works (very mission-fulfilling). You know that situation where you give a great tool as an experiment but people love it too much and you have to take it away again... that sucks! I hope we can avoid that scenario with ForeignAPIRepo.
Future plans? Make caching in general not suck, and have the local thumb cache better integrated with the normal thumb path construction, it's a bit (read: very) haphazard right now. I'm not sure if it's still the case, but I know Betawiki was running the ForeignApiRepo live at one point, pointed at Commons.
Great. Chad, were/are you one of the developers on this or is this just your wishlist for someone else? :)
cheers Brianna
On Wed, Nov 5, 2008 at 8:19 PM, Brianna Laugher brianna.laugher@gmail.comwrote:
2008/11/5 Chad innocentkiller@gmail.com:
Future plans? Make caching in general not suck, and have the local thumb cache better integrated with the normal thumb path construction, it's a bit
(read:
very) haphazard right now. I'm not sure if it's still the case, but I know Betawiki was running the ForeignApiRepo live at one point, pointed at Commons.
Great. Chad, were/are you one of the developers on this or is this just your wishlist for someone else? :)
Brion initially wrote it, but I've been poking at it here and there. I'd love to put more time into it soon, actually.
-Chad
Hi,
I did some work on a better way of accessing foreign sites, with the plan to eventually cache things like images. You can take a look in the remotesite branch (the related files are in the includes/remotesite folder of that branch). Although lately I've been busy with study, hopefully I'll be able to get back to that.
-Matt
-------------------------------------------------- From: "Brianna Laugher" brianna.laugher@gmail.com Sent: Wednesday, November 05, 2008 5:39 AM To: "wikitech-l" wikitech-l@lists.wikimedia.org Subject: [Wikitech-l] ForeignApiRepo plans?
Hi,
I just took the opportunity to check out ForeignApiRepo, aka InstantCommons alpha. It's pretty sweet. http://modernthings.org/mwfresh/index.php?title=User:Pfctdayelise I did a little dance when it really and truly worked!
http://www.mediawiki.org/wiki/Manual:$wgForeignFileRepos#Using_files_from_Wikimedia_Commons_:_ForeignAPIRepo only says "keep in mind that you are hotlinking images from another site", and to somehow cache images locally if you have "a lot of visitors". Any suggestions on what a threshold for "a lot" is? Is some future development on this intended to have a local-caching option?
Is there any way for Wikimedia Commons users/admins to tell that an image is being used in this way? (I'm guessing not since we are still waiting for this native functionality for the Wikimedia universe...) Could some kind of filtered data log be made available perhaps via the toolserver so that we (community) can build a tool to check this? While I doubt third-party users would be a high priority for Commoners, it's still nice to avoid upsetting people by unexpectedly deleting their images if at all possible.
Which brings me to again another problem still existing within Wikimedia, how the local party can be informed of changes (overwrite uploads and deletions) to images that they are using via this method.
Is this maybe the kind of thing we should require people to register a key of some kind for? Then we would have a way of knowing how popular it is.
So, basically I would be interested to hear what the future plans for development for this will be.
thanks Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org