|
|
| Author |
Message |
| 25 new of 113 responses total. |
kingjon
|
|
response 28 of 113:
| 
Feb 20 20:57 UTC 2006 |
http://nanoblogger.sourceforge.net/
"NanoBlogger is a small weblog engine written in Bash for the command line. It
uses common UNIX tools such as cat, grep, and sed to create static HTML
content. It's free to use and modify under the GNU General Public License."
|
richard
|
|
response 29 of 113:
|
Feb 21 22:47 UTC 2006 |
I was under the impression that janc was working on a backtalk blogosphere,
is he not>
|
janc
|
|
response 30 of 113:
|
Feb 23 17:18 UTC 2006 |
Yes, I have been working on a new blog interface for backtalk. Progress
has not been too fast, but I hope to be able to put more work in soon.
The idea would be that we would create "blog" confererences for users
upon request. These would basically be ordinary Picospan type
conferences, but with a few differences. First, the fairwitnesses would
have more power in them than the have in standard Grex conferences.
Second, there would be a short URL you could go to where you would be
viewing the conference through the "sage" interface, which presents the
conference as a blog.
For instance, if I started a Grex blog, it might be the "janc"
conference. You could read it from Fronttalk by doing "join janc" or
you could read it from Abalone or Pistachio like any other conference,
but the more normal way to access it would be to go to
"http://www.cyberspace.org/janc/", in which case you'd be reading the
conference through the sage interface, which would look pretty much
exactly like a standard blog. Actually, I'd love it if we could do
"janc.cyberspace.org" but don't know if we can. The way it works is
that each item appears as a blog entry. Under the text of each item,
there would be a comments link. Clicking on that, would give you the
list of responses to the item.
The fairwitnesses of these blog conferences would have much more control
over their conferences than those of standard conferences. It would be
treated as a conference that they own and that they fully control. Some
specifics:
- The default setting for a blog conference would be to allow only
the fairwitnesses to post new items (blog entries). The fair
witnesses would be able to change this, allowing any set of users
they want to post items.
- The right to post responses could be also be controlled. A very
common setting would be to allow anyone to post, without even
requiring them to have a Grex account. Or you could restrict it
to Grex accounts, or only a list of specific Grex accounts.
- Normally blogs would allow anonymous reading, so people don't need
Grex accounts to read the blog. But that also can be restricted to
Grex users or to a subset of Grex users.
- Fairwitnesses of blog conferences could determine if users can
edit their past postings.
- Fairwitnesses of blog conferences can delete blog entries, comments
or the whole blog without restriction.
They'd also have deep control over the look and feel of the blog.
Colors, fonts, background images, sidebars with lists of links, sidebars
with calendars to access past postings, etc, etc. My aim is to make it
possible to make the blog closely match the appearance of just about any
other blog on the web. The sage interface includes many admin pages for
controlling the look and feel. You can create multiple "skins" and
allow users to use any one of them to view the conference (one would be
the default skin) or you can read any blog using any system "skin".
There will be full support for permalinks, RSS, trackback, and pingback.
But it's only about half built. The built half is mostly underlying
infra-structure, like tools to create, edit and interpret skins.
It also will not work with Picospan. Picospan doesn't understand
concepts like "only the fairwitness can post items".
I can't really say when the first usuable version will be done. I'm
expecting to be able to put in some more work on it in the coming week.
|
slynne
|
|
response 31 of 113:
|
Feb 23 17:40 UTC 2006 |
It sounds really neat.
|
jadecat
|
|
response 32 of 113:
|
Feb 23 19:17 UTC 2006 |
I second that.
|
naftee
|
|
response 33 of 113:
|
Feb 23 21:55 UTC 2006 |
i third with our lovely ladies
|
remmers
|
|
response 34 of 113:
|
Feb 23 22:07 UTC 2006 |
Sounds extremely cool.
Are you using CSS to implement look-and-feel?
|
other
|
|
response 35 of 113:
|
Feb 24 02:33 UTC 2006 |
How about Ajax?
|
scholar
|
|
response 36 of 113:
|
Feb 24 04:43 UTC 2006 |
IT SMELLS TOO MUCH LIKE SEMEN< AHAHAHAha
|
nharmon
|
|
response 37 of 113:
|
Feb 24 04:45 UTC 2006 |
Ajax is most appropriately used for applications requiring immediate
data rendering like with Google maps. Otherwise, its a waste of
resources IMHO.
|
scholar
|
|
response 38 of 113:
|
Feb 24 05:07 UTC 2006 |
but why does it smell so much like semen. :(
|
other
|
|
response 39 of 113:
|
Feb 24 11:17 UTC 2006 |
37: You must be a great engineer. But you'd suck ass as a designer
with an attitude like that.
|
spooked
|
|
response 40 of 113:
|
Feb 24 12:50 UTC 2006 |
Oh, map rendering --- I have to "play" (code in) with that stuff (amongst
a mix of other stuff!) over the next few months!
|
nharmon
|
|
response 41 of 113:
|
Feb 24 13:09 UTC 2006 |
Re 37: Its funny you say that. I'm currently taking a web design class,
and am having a hard time not throwing up looking at the javascript
code they're having us write so an image changes when your mouse hovers
over it. :)
|
remmers
|
|
response 42 of 113:
|
Feb 24 16:21 UTC 2006 |
Maybe the code could be improved.
I could think some Ajaxish functionality that would be nice for blogging
or conferencing. For example, click on a link to a previous response
and have the response open in-place without reloading the whole page.
Then click on something to have the response disappear.
|
janc
|
|
response 43 of 113:
|
Feb 26 19:19 UTC 2006 |
Yeah, I agree with John. More ajax would be extremely cool. It's not
on the top of my agenda though.
I also don't think this should freeze the idea of using alternate
blogging software. I haven't exactly promised a delivery date on this.
|
spooked
|
|
response 44 of 113:
|
Feb 26 21:21 UTC 2006 |
From what I have read, your design and intended blogging functionality
sounds very good Jan and will integrate well - look and feel wise - with
Grex's existing software base so no rush - it will be well worth
it.
<begin-rant>
When we wake up to ourselves and move to an OS that supports Java
out-of-the-box, assembling and customising new components (from existing
OSS efforts) will also assist making Grex more attractive for new users.
</begin-rant>
Has anyone taken a look at Solaris 10? It is seriously very nice! I
was so impressed with my research that I have ordered the full boxed set
(with development tools and auxilliary software), and am also seriously
considering purchasing a Sun workstation - not compulsory for running
Solaris 10, but certainly supported better by the OS than my existing
Intel and Apple hardware. I have made a quote for the Sun Ultra 20
Workstation with Opteron 144 Processor - 64-bit computing, very nice.
|
keesan
|
|
response 45 of 113:
|
Feb 26 23:27 UTC 2006 |
Washtenaw Community College is running Solaris (I think it is 10). We found
and are using Kermit compiled specifically for it. They have a two year old
lynx as well. Jim has a shell account. I got up to 170K/sec downloads to
his account, compared with 10-15K when grex is not too busy.
|
spooked
|
|
response 46 of 113:
|
Feb 27 04:35 UTC 2006 |
I got an amazing quote (proposed by me:) for a
Sun Ultra 20 Workstation, see
http://www.sun.com/desktop/workstation/ultra20/index.jsp
so I'm going to go ahead and purchase it. I can run
Solaris 10, Windows XP, and Linux out of the box on it.
Will be an awesome Java development and server deployment
platform. Who knows, I might even host a minimal Grex
shell facility from it (without dialins:)
Grex *really* needs to migrate to a true operating system,
not a cutdown one without Java like OpenBSD -- Solaris 10
and Mac OS X (Darwin) are good candidates.
|
twenex
|
|
response 47 of 113:
|
Feb 27 11:11 UTC 2006 |
Why does Grex need Java?
|
spooked
|
|
response 48 of 113:
|
Feb 27 11:48 UTC 2006 |
Well, unless you want to continue living in the last century.....
However, if you *seriously* want to consider cool software, rapid
development, education, now and the future you *MUST* at least
support Java.
Not that living in the last century is to be frowned upon, but I thought
the consensus was we want to modernise Grex and make it a more attractive
place, especially for newcomers.
|
twenex
|
|
response 49 of 113:
|
Feb 27 14:54 UTC 2006 |
What would Grex use Java for?
|
mcnally
|
|
response 50 of 113:
|
Feb 27 18:08 UTC 2006 |
Just to have it. You know, to be all cool and stuff..
|
spooked
|
|
response 51 of 113:
|
Feb 27 21:41 UTC 2006 |
I never thought a bunch of techie-minded people could continue living
with their blinkers on for so long, but I should not be so surprised by
now.
It is no wonder that the large majority of staff and member base on
Grex are of the older generation, bought up on C (which, sure, has a
place and will never be outsourced). But, you insist on missing the boat
by living in the dark ages - that's all cool with me, I have not been
overly interested in Grex or its dieing conferences in many years now.
I'm totally happy to offer my services elsewhere.
|
kingjon
|
|
response 52 of 113:
|
Feb 27 21:47 UTC 2006 |
I'm not on staff, but I am a member, and I don't like Java -- and I'm not of
"the older generation," since I'm under 21. I primarily don't like it because I
often find myself on machines with limited bandwidth, limited memory, and/or
limited CPU speed -- and "limited" might be what you think of when you say
"obsolete" (the fastest computer I've ever owned is 350MHz) -- and Java wastes
all of them.
|