Menu
▾
▴
slashcode-general — This is the general discussion list. Install questions welcome.
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(30) |
Mar
(123) |
Apr
(188) |
May
(90) |
Jun
(68) |
Jul
(129) |
Aug
(72) |
Sep
(97) |
Oct
(99) |
Nov
(168) |
Dec
(35) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(75) |
Feb
(55) |
Mar
(104) |
Apr
(49) |
May
(12) |
Jun
(11) |
Jul
(47) |
Aug
(104) |
Sep
(14) |
Oct
(26) |
Nov
(31) |
Dec
(10) |
| 2003 |
Jan
(78) |
Feb
(76) |
Mar
(47) |
Apr
(30) |
May
(19) |
Jun
(36) |
Jul
(48) |
Aug
(43) |
Sep
(54) |
Oct
(25) |
Nov
(79) |
Dec
(39) |
| 2004 |
Jan
(43) |
Feb
(14) |
Mar
(17) |
Apr
(15) |
May
(18) |
Jun
(20) |
Jul
(7) |
Aug
(30) |
Sep
(49) |
Oct
(17) |
Nov
(14) |
Dec
(72) |
| 2005 |
Jan
(55) |
Feb
(27) |
Mar
(34) |
Apr
(15) |
May
(8) |
Jun
(23) |
Jul
(7) |
Aug
(19) |
Sep
(3) |
Oct
(44) |
Nov
(3) |
Dec
|
| 2006 |
Jan
(20) |
Feb
(5) |
Mar
(8) |
Apr
(12) |
May
(16) |
Jun
(22) |
Jul
(39) |
Aug
(65) |
Sep
(4) |
Oct
(11) |
Nov
|
Dec
(5) |
| 2007 |
Jan
(2) |
Feb
(2) |
Mar
(8) |
Apr
(3) |
May
(28) |
Jun
(6) |
Jul
(3) |
Aug
(9) |
Sep
(15) |
Oct
|
Nov
(12) |
Dec
(2) |
| 2008 |
Jan
(3) |
Feb
(14) |
Mar
|
Apr
(4) |
May
|
Jun
(12) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2009 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
|
May
|
Jun
(14) |
Jul
|
Aug
(1) |
Sep
(66) |
Oct
(21) |
Nov
|
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
(100) |
Mar
(17) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Larson, T. E. <TEL...@we...> - 2009-06-15 18:24:42
|
From: Shane Zatezalo [mailto:sh...@lo...] > I don't know of any other way to "help" the community, other then to > devote time to it. Which at the moment, and for the foreseeable > future, I do not have. I guess I think that if slashcode is still a viable project, there'd be discussion on this list, there'd be postings on slashcode.com (even if nothing but YASS). There'd be _something_ visibly happening. The lack of the former makes it seem as if development is not occurring (there may be a core group of people hacking away, but it seems insular if there is no discussion). The lack of the former makes it seem as if nobody is adopting slashcode, leaving only use by legacy sites. Either way, it doesn't look like an attractive project to contribute to. Tim |
|
From: gnul <nul...@gm...> - 2009-06-15 18:21:40
|
Building an open source community seems to be a chicken and egg type of problem. You need a quality code base that appeals to a wide audience; and you need that audience using the code. (Writing documentation and contributing to the code also helps.) While Slashcode /appeals/ to a wide audience, and a lot of people still read Slashdot, it seems many web developers are unable to use the code. I feel there are two large limiting factors to growing the Slashcode community, others have already mentioned both: 1) Very infrequent updates by the maintainers means that I can't checkout the latest code and have something that "feels" like /. (I can understand that Slashdot itself wants to keep it's look & feel unique, so ship a subset of images + css. But the ajax and other enhancements are key to having a working site.) 2) The Apache 1.x limitation. It means that developers wanting to setup a Slashcode site need to setup a virtual server specifically for Apache 1. (And maintain that software). If the Slashcode maintainers don't want to extend the effort necessary to make Slashcode work with Apache 2 as well as ship packaged releases, then the only option for the community is a fork, which is always unfortunate. With all of the other active communities for this type of software, I think it may be less work to gain a larger community by hacking other software to include slashcode features such as moderation and the firehose... Yet forking or modding other software is still a lot of work. Bummer. Perhaps the best course of action is to lobby the Slashcode maintainers? I really want[ed] to build a Slashcode site, but the Apache 1 limitation prevents me. Good luck! -gnul |
|
From: Axel B. <ab...@no...> - 2009-06-15 17:44:07
|
Hi, since my initial mails seems to have been moderated, I send it once again from the address I'm subscribed with on this list: On Thu, Jun 11, 2009 at 08:49:53AM -0400, Alexandre Leroux wrote: > Here's my latest Slashdot journal entry, trying to get feedback in order > to make the best decisions for the future of my slashsite. > > Don't hesitate to share comments! :-) Not sure if you wanted comments here on the list or to your journal entry. :-) > http://slashdot.org/~Lord+Satri/journal/231231 I just posted the following comment there: ---snip--- I am, no, I was the last packager of Slashcode for Debian. Slashcode is no more packaged for Debian, since it has two big problems: It doesn't run with Apache 2.x and Apache 1.3 is no more present in many Linux distributions. That's the main reason why it dropped out of Debian, too. 5 years ago a mod_perl 2.0 patch has been posted on Slashcode.com <http://www.slashcode.com/article.pl?sid=04/02/19/2144259>, but it seems as it never got incorporated by Slashcode and Slashcode continued to evolve without Apache 2 compatibility. Two years ago someone submitted a question what's the current state of Slashcode on Apache 2 <http://www.slashcode.com/submit.pl?op=viewsub&subid=9782¬e=&title=Slash+%26amp%3B+Apache2%2Fmod_perl2%2C+three+years+later%3F>, but this submission seems still pending. Slashdot.org btw. still runs on Apache 1.3. Probably for the very same reason. They missed that train and I don't want to know what effort it will be today, to move over to Apache 2.x. I expect that even when Slashdot dies, it will die running on a prehistoric Apache 1.3. The second big problem: There are no official stable releases since many, many years. Only code out of the VCS repository. This also has problems with security fixes. Statements like "all 2.x releases" are affected usually aren't true and you have to check the code yourself if it is affected or not. This drives every distributor crazy. I don't know how I will proceed with my Slashsite. Probably use the last official stable release 2.2.6 and see if I get it running with Apache 2.2 somehow. Or hope that Slashcode will once run on Apache 2.2 out-of-the-box against all fears. But despite that I'm usually an optimist, I don't expect this to happen. ---snap--- Regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | ab...@de... (Mail) X | ab...@no... (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web) |
|
From: Clifton W. <cli...@gm...> - 2009-06-15 17:31:45
|
That pretty much hits the nail on the head, there. - Cliff On Thu, Jun 11, 2009 at 4:45 PM, Shane Zatezalo <sh...@lo...> wrote: > > On Jun 11, 2009, at 8:49 AM, Alexandre Leroux wrote: > > > > > [...] > > > > Slashcode is dead, long live Slashcode? > > > > <snipped> > > I too agree, and disagree. > > The community seems to be slowly drifting away. Things like not > accepting patches, vagaries about where things are heading, no > official releases, no automated migratory path from 2.2.6 to the > latest, moving from CVS at SF to git at github and then seemingly > stopping commits to it, all are rough on an open source project. (to > be fair, it's been many months since I did a git pull to look, but > there seemed to be quite a draught from the faucet for quite some time). > > That said, it's open source. We all have the source. Want a feature? > Code it up. Can't code? Learn or pay someone to do it. > > Just because a company open sources it's wares, doesn't mandate that > it prop the community, drive it nor fund it. They've done the vast > majority of the work just by agreeing to put it out there for all to > use, for free, ridicule, bitch about. And most of the time when this > happens, employees end up devoting a chunk of their personal time to > help out the project or stick around on IRC or help handhold those w/ > lesser skills. Sometimes a ridiculous amount of personal time, emails, > IM's and IRC chats, considering it's their *own* time. > > Also, someone pointed out one of the best things about Slashcode > (IMHO) - the stability of it. Over the past few years there have been > an absolute minimal number of security holes. For the most part, it's > stable like a rock. You can get it running, and then you don't spend > your time having to maintain it daily, you and your staff just use it. > > So I guess I've seen it both ways. > > I suppose someone could step up and fork it, put up a project and > system for it, patch it, mod it, take requests, take submissions > (review, tweak, test, patch), take all the existing feature requests > on SF and implement them. Would that drive the community back to what > it once was years ago? > > Who's got a hand waving in the air volunteering to do all that for > free?? > > I don't know of any other way to "help" the community, other then to > devote time to it. Which at the moment, and for the foreseeable > future, I do not have. > > Shane > > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > |
|
From: Shane Z. <sh...@lo...> - 2009-06-11 21:08:53
|
On Jun 11, 2009, at 8:49 AM, Alexandre Leroux wrote: > > [...] > > Slashcode is dead, long live Slashcode? > <snipped> I too agree, and disagree. The community seems to be slowly drifting away. Things like not accepting patches, vagaries about where things are heading, no official releases, no automated migratory path from 2.2.6 to the latest, moving from CVS at SF to git at github and then seemingly stopping commits to it, all are rough on an open source project. (to be fair, it's been many months since I did a git pull to look, but there seemed to be quite a draught from the faucet for quite some time). That said, it's open source. We all have the source. Want a feature? Code it up. Can't code? Learn or pay someone to do it. Just because a company open sources it's wares, doesn't mandate that it prop the community, drive it nor fund it. They've done the vast majority of the work just by agreeing to put it out there for all to use, for free, ridicule, bitch about. And most of the time when this happens, employees end up devoting a chunk of their personal time to help out the project or stick around on IRC or help handhold those w/ lesser skills. Sometimes a ridiculous amount of personal time, emails, IM's and IRC chats, considering it's their *own* time. Also, someone pointed out one of the best things about Slashcode (IMHO) - the stability of it. Over the past few years there have been an absolute minimal number of security holes. For the most part, it's stable like a rock. You can get it running, and then you don't spend your time having to maintain it daily, you and your staff just use it. So I guess I've seen it both ways. I suppose someone could step up and fork it, put up a project and system for it, patch it, mod it, take requests, take submissions (review, tweak, test, patch), take all the existing feature requests on SF and implement them. Would that drive the community back to what it once was years ago? Who's got a hand waving in the air volunteering to do all that for free?? I don't know of any other way to "help" the community, other then to devote time to it. Which at the moment, and for the foreseeable future, I do not have. Shane |
|
From: Stubbe P. <pau...@mi...> - 2009-06-11 14:38:26
|
We are running a slashcode based site on an intranet. The advantage of this community is that the site has been running since Apr 2006 without interruptions. So the focus is on content and effective use and not on IT evolutions. We really do appreciate this tool. The IT departement would indeed appreciate to find more information on the slashcode site to be able to stay tuned with the /. look and feel. Now they tell us that they are not able to do that. Paul This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. |
|
From: lists <li...@ku...> - 2009-06-11 14:01:07
|
Larson, Timothy E. wrote: > I completely agree regarding this "community". Several years ago I was very excited about setting up a Slash site, because I like it's discussion format better than any other weblog engine's. (I recall being very excited about your GEO extensions too.) But given the state of slashcode, my plans will probably never come to fruition. > > > Tim > <snipped> I both agree and disagree :-) I agree that the community is mostly dead. I disagree that it is beyond revival. There is clearly a place for slashcode driven sites. As long as that demand remains, and there are enthusiasts to support it, slashcode will live. We just need a plan of action. Pete -- |
|
From: Larson, T. E. <TEL...@we...> - 2009-06-11 13:24:37
|
I completely agree regarding this "community". Several years ago I was very excited about setting up a Slash site, because I like it's discussion format better than any other weblog engine's. (I recall being very excited about your GEO extensions too.) But given the state of slashcode, my plans will probably never come to fruition. Tim |
|
From: Alexandre L. <ale...@ec...> - 2009-06-11 13:18:43
|
Dear list! Here's my latest Slashdot journal entry, trying to get feedback in order to make the best decisions for the future of my slashsite. Don't hesitate to share comments! :-) Thanks - Alex http://slashdot.org/~Lord+Satri/journal/231231 /Slashcode is dead, long live Slashcode?/ /"The good news is Slashdot <http://slashdot.org/> is still an interesting site to me, continues to evolve and is in active development. But the good news about Slashdot do not apply to Slashcode <http://www.slashcode.com/>, Slashdot's open source engine. I'm the main manager of a small Slashcode-based website <http://slashdot.org/%7ELord+Satri/journal/slashgeo.org>. Despite my enthusiasm, the truth is Slashcode is dead. It has been dead for quite some time and I wonder if it can be resurrected. How can Slashcode be dead? There is no community behind it anymore. There has been no official release since 2002, granted you can and should use the CVS tags, but it has not been updated with anything recent such as the AJAX code used on Slashdot for the last few years./ /Rebuilding the community? Maybe, but enthusiasts quickly hit a wall. Slashcode's own main page is not up to date, there's a lot of missing information and my previous efforts at helping updating it got no answers from the site admins. How can you build a community when there's no way to learn who's in the boat with you <http://www.slashcode.com/sites.pl>? Ah! The mailing lists, of course! There are two main Slashcode mailing lists. On the Slashcode-general list <https://sourceforge.net/mailarchive/forum.php?forum_name=slashcode-general>, there was only 8 threads in 2008, 3 so far for 2009. For the Slashcode-development, it's worse: 2 posts since May 2007, both from our small team. You can ask questions, but you never know if someone will answer the phone./ /A few years ago our small team developed a plugin that adds webmaps to stories and GeoRSS to the feed but failed to get much feedback from anyone. We're far from the community and the development workforce than, to name just one, the one behind Drupal, which has its own conference and 2000 developer accounts <http://en.wikipedia.org/wiki/Drupal#Community>. Slashdot's responsibility? None directly, Slashcode is open source software, they rightfully have no obligation to contribute to a community./ /Slashcode still has some attracting features and an excellent auto-moderation system. So, what's Slashcode future? I'm interested in the insights you have to share. I fear my own Slashsite will die out of technological obsolescence and that other Slashsites have no future. A Slashcode community won't spring out of the digital blue overnight, but it all has to start somewhere. Is it too late to try to build a vibrant Slashcode community?"/ -- Alexandre Leroux, M.Sc., Ing. Environnement Canada / Environment Canada Centre météorologique canadien / Canadian Meteorological Centre Section de la réponse aux urgences environnementales / Environmental Emergency Response Section ale...@ec... |
|
From: Andrew H. <hol...@gm...> - 2009-03-08 23:24:33
|
I do have every reason to believe that this is a current version, but I don't know what command to issue to find out the slash version that is currently running to verify. There does not seem to be a reference to this command that I can see either in the book or online. Thank you, -Andrew On Thu, Mar 5, 2009 at 7:15 AM, Shane Zatezalo <sh...@lo...> wrote: > > On Mar 4, 2009, at 9:44 PM, Andrew Holden wrote: > >> Hi - we are in the process of setting up a new Slash site but I have >> an issue that I hope someone can help with. >> >> The server is up and running on Debian and I started to try and change >> some of the appearance but I run into issues with the color blocks. > > What version of Slashcode are you running? Sounds as if you are > following an ancient book with an ancient version of Slashcode. > > IMHO, you should be running one of the last Tagged-Versions out of > their CVS > > http://sourceforge.net/cvs/?group_id=4421 > > or even HEAD from their GIT repo if you want to live dangerously ;) > > http://github.com/scc/slash/tree/master > > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > |
|
From: Alexandre L. <ale...@ec...> - 2009-03-05 16:31:22
|
Hi all, I have two topics for which I'd like an RSS feed. Only 'Skins/Sections' have distinct RSS feeds. Ideally, I don't want to mess with my actual Skins/Section structure. Are there other options than setting up a new Skin/Section and add the two topics to that section? In order to avoid setting up new nexus topics, I guess I could simply promote the two actual topics to nexus-topics and associate each of them with a new skin. I would only need two new skins and nothing else. Does that make sense too? Other options? Thanks for any feedback - Alex :-) -- Alexandre Leroux, M.Sc., Ing. Environnement Canada / Environment Canada Centre météorologique canadien / Canadian Meteorological Centre Section de la réponse aux urgences environnementales / Environmental Emergency Response Section ale...@ec... |
|
From: Shane Z. <sh...@lo...> - 2009-03-05 11:46:31
|
On Mar 4, 2009, at 9:44 PM, Andrew Holden wrote: > Hi - we are in the process of setting up a new Slash site but I have > an issue that I hope someone can help with. > > The server is up and running on Debian and I started to try and change > some of the appearance but I run into issues with the color blocks. What version of Slashcode are you running? Sounds as if you are following an ancient book with an ancient version of Slashcode. IMHO, you should be running one of the last Tagged-Versions out of their CVS http://sourceforge.net/cvs/?group_id=4421 or even HEAD from their GIT repo if you want to live dangerously ;) http://github.com/scc/slash/tree/master |
|
From: Andrew H. <hol...@gm...> - 2009-03-05 02:44:32
|
Hi - we are in the process of setting up a new Slash site but I have an issue that I hope someone can help with. The server is up and running on Debian and I started to try and change some of the appearance but I run into issues with the color blocks. On page 133 of the Slash book it shows what the page should look like, with a pull down select box near the top where you are supposed to tell it what color block you wish to edit. However there is no pull down box on my page. I have made some block names of the form XXX_colors from which I think I should be able to choose. I have tried rebooting the server, and I have tried using IE instead of Firefox with no change in the condition. Any thoughts on what might be going on? Thanks. -Andrew |
|
From: Shane Z. <sh...@lo...> - 2009-02-23 15:51:21
|
On Feb 15, 2009, at 10:28 PM, matrix wrote: > HI: > I'am a newbie，and an admin of chinese slash site。this site have > many > problem.today i'am creating some new topics,suddenly Server report > "Internal Server Error", > Details below : > >>> HTTP/1.1 200 OK Date: Mon, 16 Feb 2009 02:51:49 GMT Server: Apache/ >>> 1.3.33 (Unix) mod_perl/1.29 Connection: close Transfer-Encoding: >>> chunked Content-Type: text/html; charset=iso-8859-1 >>> OK >>> The server encountered an internal error or misconfiguration and >>> was unable to complete your request. > >>> You need to read through your Apache's error logs to find more information inorder to determine what's going on. Typically /usr/local/ apache/logs/error.log (etc) |
|
From: matrix <a.h...@gm...> - 2009-02-16 03:28:16
|
HI: I'am a newbie，and an admin of chinese slash site。this site have many problem.today i'am creating some new topics,suddenly Server report "Internal Server Error", Details below : >> HTTP/1.1 200 OK Date: Mon, 16 Feb 2009 02:51:49 GMT Server: Apache/1.3.33 (Unix) mod_perl/1.29 Connection: close Transfer-Encoding: chunked Content-Type: text/html; charset=iso-8859-1 >> OK >> The server encountered an internal error or misconfiguration and was unable to complete your request. >> Please contact the server administrator, ad...@so... and inform them of the time the error occurred, and anything you might have done that may have caused the error. >> More information about this error may be available in the server error log. Thanks for the help,sorry for my poor english. -- http://www.solidot.org |
|
From: Shane Z. <sh...@lo...> - 2008-12-08 19:34:22
|
There is an unsubscribe plugin that will let you (as an admin) hit / unsubscribe.pl on your site and paste in a list of email addresses that should be unsubscribed. It apparently does all of the work for you. You would just have to install-plugin on your site to add it so it's available for your website. A little late on the reply, sorry, freetime is sparse. Shane On Nov 26, 2008, at 9:45 AM, Alexandre Leroux wrote: > > Hi list, > > For my small slash site (1,800 registered users, about 30-40,000 daily > hits), I want to unsubscribe users that are subscribed to the daily > headlines or newsletter but which have their email addresses bouncing > back every night. [...] |
|
From: Alexandre L. <ale...@ec...> - 2008-11-26 14:45:34
|
Hi list, For my small slash site (1,800 registered users, about 30-40,000 daily hits), I want to unsubscribe users that are subscribed to the daily headlines or newsletter but which have their email addresses bouncing back every night. I'm a SQL novice, so I'd simply like a confirmation that this command below is the right way to do it. DELETE FROM users_messages WHERE uid IN (SELECT uid FROM users WHERE realemail = 'enter-real-email-here') AND code <= 1; Some more details below if you need it. Thanks a lot for the help! Alex for Slashgeo.org -- Alexandre Leroux, M.Sc., Ing. Environnement Canada / Environment Canada Centre météorologique canadien / Canadian Meteorological Centre Section de la réponse aux urgences environnementales / Environmental Emergency Response Section ale...@ec... >> I think I must find the 'uid' from the 'users' table with the >> 'realemail' field. For this 'uid', I must delete (right??) entries >> with code '0' and '1' from the 'users_messages' table. >> >> >> mysql> select * from message_codes; >> +------+----------------------------+---------+-------+------------+-----------+-------+-----------------+ >> >> | code | type | seclev | modes | send | >> subscribe | acl | delivery_bvalue | >> +------+----------------------------+---------+-------+------------+-----------+-------+-----------------+ >> >> | -2 | Registration Mail | 1 | 0 | now >> | 0 | | 0 | >> | -1 | Unknown Message | 1 | 0 | now >> | 0 | | 0 | >> | 0 | Daily Newsletter | 1 | 0 | now >> | 0 | | 1 | >> | 1 | Daily Headlines | 1 | 0 | now >> | 0 | | 1 | >> | 2 | Metamoderation Results | 1 | | collective >> | 0 | | 3 | >> | 3 | Comment Moderation | 1 | | collective >> | 0 | | 3 | >> | 4 | Comment Reply | 1 | | now >> | 0 | | 15 | >> | 5 | Journal Entry by Friend | 1 | | now >> | 0 | | 7 | >> | 6 | New Submission | 100 | 0 | now >> | 0 | | 1 | >> | 7 | Journal Reply | 1 | | now >> | 0 | | 7 | >> | 8 | New Comment | 1000000 | | now >> | 0 | | 0 | >> | 10 | Daily Site Stats | 100 | 0 | now >> | 0 | stats | 1 | >> | 11 | Email Story | 1 | 0 | now >> | 0 | | 1 | >> | 12 | Relationship Change | 1 | | collective >> | 1 | | 3 | >> | 13 | Bad login attempt warnings | 1 | 1 | now >> | 0 | | 2 | >> | 14 | Daily Moderation Stats | 100 | 0 | now >> | 0 | stats | 1 | >> | 18 | Invalid HTML Input | 100 | | now >> | 0 | | 3 | >> | 19 | System Messages | 100 | 0 | >> | 0 | | 4 | >> | 20 | New Story Posted | 1 | 0 | >> | 0 | | 12 | >> +------+----------------------------+---------+-------+------------+-----------+-------+-----------------+ >> >> 19 rows in set (0.00 sec) >> >> mysql> >> mysql> describe users_messages; >> +-------+-----------------------+------+-----+---------+----------------+ >> >> | Field | Type | Null | Key | Default | >> Extra | >> +-------+-----------------------+------+-----+---------+----------------+ >> >> | id | int(11) | | PRI | NULL | >> auto_increment | >> | uid | mediumint(8) unsigned | | MUL | 0 >> | | >> | code | int(11) | | | 0 >> | | >> | mode | tinyint(4) | | | 0 >> | | >> +-------+-----------------------+------+-----+---------+----------------+ >> >> 4 rows in set (0.00 sec) >> >> mysql> >> mysql> describe users; >> +-------------------------+-----------------------+------+-----+---------+----------------+ >> >> | Field | Type | Null | Key | >> Default | Extra | >> +-------------------------+-----------------------+------+-----+---------+----------------+ >> >> | uid | mediumint(8) unsigned | | PRI | >> NULL | auto_increment | >> | nickname | varchar(20) | | MUL >> | | | >> | realemail | varchar(50) | | MUL >> | | | >> | fakeemail | varchar(75) | YES | | >> NULL | | >> | homepage | varchar(100) | YES | | >> NULL | | >> | passwd | varchar(32) | | >> | | | >> | sig | varchar(200) | YES | | >> NULL | | >> | seclev | mediumint(8) unsigned | | | >> 0 | | >> | matchname | varchar(20) | YES | MUL | >> NULL | | >> | newpasswd | varchar(8) | YES | | >> NULL | | >> | journal_last_entry_date | datetime | YES | | >> NULL | | >> | author | tinyint(4) | | MUL | >> 0 | | >> +-------------------------+-----------------------+------+-----+---------+----------------+ >> >> 12 rows in set (0.00 sec) >> >> mysql> |
|
From: Andre-John M. <aj...@sy...> - 2008-06-23 13:39:58
|
On 23-Jun-08, at 09:25 , Jamie McCarthy wrote: > ms...@di... (Manu Sporny) writes: > >>> We haven't really considered it. Semantic markup isn't high on >>> our priority list. >> >> What!? Haven't you heard, the semantic web is the future of the >> Internet! Web 3.0 and all that jazz... :) > > Oh, I'd heard. I suspect, like IPv6, it's the future of the > internet and always will be ;) > > <https://slashdot.org/article.pl?sid=01/04/10/2023246> > <https://slashdot.org/article.pl?sid=07/03/21/0235208> With the EU now mandating IPv6 support, and the US government doing the same for its departments, I think IPv6 is heck of a lot closer to being supported than the semantic web. The former once implemented is essentially deploy and forget. The semantic web is going to need a lot more effort by web site designers. Just my 5c. Andre |
|
From: Jamie M. <ja...@mc...> - 2008-06-23 13:25:58
|
ms...@di... (Manu Sporny) writes: >>We haven't really considered it. Semantic markup isn't high on >>our priority list. > >What!? Haven't you heard, the semantic web is the future of the >Internet! Web 3.0 and all that jazz... :) Oh, I'd heard. I suspect, like IPv6, it's the future of the internet and always will be ;) <https://slashdot.org/article.pl?sid=01/04/10/2023246> <https://slashdot.org/article.pl?sid=07/03/21/0235208> >The first pass would merely identify story titles, dates, >abstracts and source URLs, which would all be done automatically. Automatically? Sounds interesting, I'm looking forward to the patch. -- Jamie McCarthy http://mccarthy.vg/ ja...@mc... |
|
From: Manu S. <ms...@di...> - 2008-06-22 13:04:06
|
Jamie McCarthy wrote: > ms...@di... (Manu Sporny) writes: >> Are there any plans to support RDFa[1] on Slashdot or in Slashcode >> in the near future? > > We haven't really considered it. Semantic markup isn't high on > our priority list. What!? Haven't you heard, the semantic web is the future of the Internet! Web 3.0 and all that jazz... :) >> - Could we submit a patch to Slashcode that adds RDFa support to >> pages? The first pass would add Dublin Core[2] elements... Would >> you accept a patch to enable Microformats support in stories as >> well? > > Patches are always welcome but we're a small and overworked dev team, > don't expect us to get right on it. :( That's fine, and certainly understandable. I just wanted to make sure that you guys weren't opposed to semantic markup in Slashcode/Slashdot before taking the time to put together a patch. > My guess is that if this isn't too much extra work for the editors > who post the stories, this could be something Slash (and Slashdot) > could find useful. If it turns out to be a hassle, then again, > this isn't high on our priority list. There should be no extra work for the editors who post the stories. The first pass would merely identify story titles, dates, abstracts and source URLs, which would all be done automatically. No extra work would be required by any of the authors or editors. We'll put together a patch, submit it via SourceForge, and chat about it in more depth after we have some code to review. -- manu -- Manu Sporny President/CEO - Digital Bazaar, Inc. blog: Blacksburg BarCamp 1.0 http://blog.digitalbazaar.com/2008/05/15/blacksburg-barcamp-10/ |
|
From: Jamie M. <ja...@mc...> - 2008-06-22 07:44:25
|
ms...@di... (Manu Sporny) writes: > Are there any plans to support RDFa[1] on Slashdot or in Slashcode > in the near future? We haven't really considered it. Semantic markup isn't high on our priority list. > - Could we submit a patch to Slashcode that adds RDFa support to > pages? The first pass would add Dublin Core[2] elements... Would > you accept a patch to enable Microformats support in stories as > well? Patches are always welcome but we're a small and overworked dev team, don't expect us to get right on it. :( My guess is that if this isn't too much extra work for the editors who post the stories, this could be something Slash (and Slashdot) could find useful. If it turns out to be a hassle, then again, this isn't high on our priority list. -- Jamie McCarthy http://mccarthy.vg/ ja...@mc... |
|
From: Jamie M. <ja...@mc...> - 2008-06-21 16:19:29
|
sc...@gu... (W. Scott Lockwood III) writes: > Or better yet, do what Scoop does - allow people to SEE who've > moderated. There's nothing like bright light for accountability. Slash is open source :) You're all welcome to set the modreasons table however you want on your own Slash sites, or to emit the modCommentLog for nonadmins so everyone can see what moderation has been done. Commentary about Slashdot's "groupthink" is off-topic for this mailing list, though. -- Jamie McCarthy http://mccarthy.vg/ ja...@mc... |
|
From: W. S. L. I. <sc...@gu...> - 2008-06-20 13:42:58
|
Or better yet, do what Scoop does - allow people to SEE who've moderated. There's nothing like bright light for accountability. -- W. Scott Lockwood III <sc...@gu...> LRSE Hosting On Fri, 2008-06-20 at 08:40 -0500, Larson, Timothy E. wrote: > Yes, but if it doesn't affect anything, who cares? I don't > particularly > agree with the limitation that someone cannot both mod and comment in > the > same story. (As long as you can't mod your OWN posts, other than the > high > karma posting bonus, I don't see the point.) If that restriction were > lifted, there would be no need for Agree/Disagree mods at all. |
|
From: Larson, T. E. <TEL...@we...> - 2008-06-20 13:41:06
|
W. Scott Lockwood III <> wrote:
> On Fri, 2008-06-20 at 07:50 -0500, Larson, Timothy E. wrote:
>> I
>> wouldn't mind
>> changing it to a -0 "Disagree" so that moderators (who cannot reply
>> lest
>> their moderations be undone) can still "comment" in this way. If
>> they want
>> to burn a mod point, let them go ahead. But it shouldn't affect the
>> post's
>> score. The expanded view of moderations on the post would still show
>> how
>> many disagreements there were, though.
>
> Isn't that still meta?
Yes, but if it doesn't affect anything, who cares? I don't particularly
agree with the limitation that someone cannot both mod and comment in the
same story. (As long as you can't mod your OWN posts, other than the high
karma posting bonus, I don't see the point.) If that restriction were
lifted, there would be no need for Agree/Disagree mods at all.
Tim
--
Tim Larson AMT2 Unix Systems Administrator
InterCall, a division of West Corporation
Eschew obfuscation!
|
|
From: W. S. L. I. <sc...@gu...> - 2008-06-20 13:28:57
|
Isn't that still meta? -- W. Scott Lockwood III <sc...@gu...> LRSE Hosting On Fri, 2008-06-20 at 07:50 -0500, Larson, Timothy E. wrote: > Mike Hearn <> wrote: > > I don't think slashdot would be any poorer if it were simply scrapped. > > Thoughts? > > I agree. "Overrated" is metamoderation done in moderation. I wouldn't mind > changing it to a -0 "Disagree" so that moderators (who cannot reply lest > their moderations be undone) can still "comment" in this way. If they want > to burn a mod point, let them go ahead. But it shouldn't affect the post's > score. The expanded view of moderations on the post would still show how > many disagreements there were, though. > > Tim > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ Slashcode-general mailing list Sla...@li... https://lists.sourceforge.net/lists/listinfo/slashcode-general |
19 messages has been excluded from this view by a project administrator.
