Slashgeo Log In
Sharing and Replying to User Comments
posted by Satri
on Thursday April 03, @11:18AM
Permalink
Trackback URI
Slashdotthis
Diggthis
Del.icio.us
from the I-agree-we-disagree dept.
Permalink
Trackback URI
Slashdotthis
Diggthis
Del.icio.us
from the I-agree-we-disagree dept.
It's been a while since we shared a Slashgeo tip of the day. There's two main ways to share comments on Slashgeo: (a) replying on the "root" of the story by selecting the "Reply" button on the right-hand side below the story summary, and (b) replying to a specific user comment by selecting the "Reply to This" link immediately after the said comment. Why is the distinction important? For several reasons and I'll give you two: (1) if you reply to another user's comment instead of the root, that user will receive a notification that you replied and will be able to share more experience, opinion and information, and (2), when replying directly to a user comment, the comments threads will stick together.
Related to the comment and story interactions mechanism, Slashdot now uses AJAX for the display and interaction with their story pages. Their code has not been pushed to Slashcode (Slashgeo's open source engine). One significant improvement to Slashgeo, in our long to-do list, will be using this AJAX code since is will circumvent the requirement to reload full html pages. Nobody likes waiting for pages to reload! :-) We can't however provide a deadline since this code implementation is mainly in their hands.
For your curiosity, despite theoretically being in slow geonews publishing mode and thanks to our expanding team of Slashgeo "editors", I'm happy to report we're now at 7,000 direct unique visitors daily, a number which slowly climbs. This is important since we're all volunteers here trying to provide a useful and ad-free tool for the geospatial community we're part of. Cheers!
Related to the comment and story interactions mechanism, Slashdot now uses AJAX for the display and interaction with their story pages. Their code has not been pushed to Slashcode (Slashgeo's open source engine). One significant improvement to Slashgeo, in our long to-do list, will be using this AJAX code since is will circumvent the requirement to reload full html pages. Nobody likes waiting for pages to reload! :-) We can't however provide a deadline since this code implementation is mainly in their hands.
For your curiosity, despite theoretically being in slow geonews publishing mode and thanks to our expanding team of Slashgeo "editors", I'm happy to report we're now at 7,000 direct unique visitors daily, a number which slowly climbs. This is important since we're all volunteers here trying to provide a useful and ad-free tool for the geospatial community we're part of. Cheers!
« Leica Geosystems Geospatial Imaging Rebrands As ERDAS | Dynamic Maps of Nonprime Mortgage Conditions in the U.S. »
Related Stories
ThinkGeo.com Donation and Slashgeo in the Coming Months
[+]
First, I'm happy to announce a new financial donation to help Slashgeo.org stay not too far below the red line, ThinkGeo.com (blog entry) is now amongst the Slashgeo.org top donors. Thank you! Donors have a link to them in the right side column.
Second, I admit I'm not entirely proud of Slashgeo's geonews coverage since the beginning of the year. As most of you already know, Slashgeo is ad-free and is ran only by voluntary contributions, mainly time given by a small team of geoenthusiasts to aggregate the most pertinent geonews out there for the geospatial community. For the last two years and a half, I've had a lot of precious help from other enthusiasts who joined the Slashgeo bandwagon as editors, but I still publish most of the stories on Slashgeo at the moment. Being a new father and away from my day job for a while, I have trouble finding the required time to adequately feed Slashgeo on a regular basis. Unless something unexpected happens and instead of being myself constantly worried, I ask you, our dear users, to allow a reduction of service for the coming months until about September. This does not mean Slashgeo will stop publishing, it just means we'll more than ever rely on user contributions and, even if efforts will be done to cover the most pertinent geonews, they may be published with a delay of a few days or more. Hopefully, Slashgeo should afterward go back to our more frequent and timely geonews publishing. Thank you for your comprehension. Alex aka Satri.
Second, I admit I'm not entirely proud of Slashgeo's geonews coverage since the beginning of the year. As most of you already know, Slashgeo is ad-free and is ran only by voluntary contributions, mainly time given by a small team of geoenthusiasts to aggregate the most pertinent geonews out there for the geospatial community. For the last two years and a half, I've had a lot of precious help from other enthusiasts who joined the Slashgeo bandwagon as editors, but I still publish most of the stories on Slashgeo at the moment. Being a new father and away from my day job for a while, I have trouble finding the required time to adequately feed Slashgeo on a regular basis. Unless something unexpected happens and instead of being myself constantly worried, I ask you, our dear users, to allow a reduction of service for the coming months until about September. This does not mean Slashgeo will stop publishing, it just means we'll more than ever rely on user contributions and, even if efforts will be done to cover the most pertinent geonews, they may be published with a delay of a few days or more. Hopefully, Slashgeo should afterward go back to our more frequent and timely geonews publishing. Thank you for your comprehension. Alex aka Satri.
Sharing and Replying to User Comments
|
Log In/Create an Account
| Top
| 6 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
don't go the ajax route
(Score:2, Interesting)Re:don't go the ajax route
(Score:3)( http://alexandreleroux.blogspot.com/ | Last Journal: Friday March 17, @05:07PM )
I don't have outstandingly powerful computers and the AJAX on Slashdot feels pretty snappy to me. I use mainly Firefox (Debian) and Safari. Can you help us pinpoint the source of your irritation? (I think the Slashdot developers are aware that MS IE is having issues with the code, but they don't care that much afaik)
BTW, you're right, normally, comment moderation and thresholds set in preferences by logged-in users should be enough to display the comments in a useful manner.
Re:don't go the ajax route
(Score:3, Interesting)Re:don't go the ajax route
(Score:3, Interesting)( http://www.geoblue.org/ )
Re:don't go the ajax route
(Score:3, Interesting)