Difference between pages "Talk:Upcoming events" and "Evolution Header Format"

From Forensics Wiki
(Difference between pages)
Jump to: navigation, search
(→‎calendar extensions)
 
 
Line 1: Line 1:
−
Wiki tables are normally such a pain, but yours look good.
+
<pre>
−
The problem with the "long list" below is that they are all pasted in and have a lot of html formatting.
+
Subject: header test
−
Really, we should have a database for the conferences. Do you know of a plug-in for mediawiki that does it? (I know that plone sdoes it ,but that would be a major overhaul.)(
+
From: Username <username@sendinghost.com>
−
--------------------------------------------------------------------
+
To: Username <username@receivinghost.com>
 +
Content-Type: text/plain
 +
Date: Sat, 28 Jul 2007 11:52:35 +0200
 +
Message-Id: <1185616355.19231.0.camel@localhost>
 +
Mime-Version: 1.0
 +
X-Mailer: Evolution 2.10.1
 +
Content-Transfer-Encoding: 7bit
 +
</pre>
  
−
This page is getting pretty long. I like the categories you've made and think they would make an excellent way to break up the page. How about the following:
+
The Message id consists of five parts:
  
−
# [[List of open calls for papers]]
+
# The current time as returned by the <tt>time</tt> function followed by a period. The value is dislayed in decimal and is the number of seconds since midnight on 1 Jan 1970. In the example above, 1185616355 refers to Sat, 28 Jul 2007 09:52:35 GMT.
−
# [[List of digital forensics conferences]]
+
# The process id number in decimal followed by a period
−
# [[List of ongoing and continuous training opportunities]]
+
# The third value starts at zero but may increase as more messages are sent. It is also followed by a period
−
# [[List of scheduled training courses]]
+
# The word <tt>camel</tt> followed by an '@'
 +
# If the canonical hostname can found, it is used. Otherwise the hostname
  
−
What do you think? [[User:Jessek|Jessek]] 20:36, 17 August 2007 (PDT)
+
The Message id format comes from the function <tt>camel_header_msgid_generate</tt> in <tt>evolution-data-server/camel/camel-mime-utils.c</tt>.
−
--------------------------------------------------------------------
+
−
 
+
−
I suppose I could break it up.  One of the reasons it is all on one page is that many folks want a single place to look for this sort of information.  I used to send it by email to multiple lists every month, and some folks complained it was too big, but most people said leave it alone.  The move of the list to the ForensicsWiki was to allow me to keep a long list, but have it available on demand, and have it updated in a single location, but still keep the "one list to rule them all" kind of listing.
+
−
 
+
−
Brian already has a "Conference" listing, which lists conferences, and some of the training providers have listings on a page for training providers/software providers.  This was added to be the "upcoming" list, which lists everything by date, more for things in the next month or so, but due to complaints by one person or another, I list everything I know about to keep anyone from suggesting I lean towards one provider or another.
+
−
[[User:Frnzxguy|Frnzxguy]] 13:49, 28 August 2007 (EDT)
+
−
--------------------------------------------------------------------
+
−
I don't know if Brian is maintaining his conference list or not. I would very much like to have a database-driven list of the conferences and training. How about doing it as a Google Calendar? We can link that over here. [[User:Simsong|Simsong]] 22:54, 31 August 2007 (PDT)
+
−
--------------------------------------------------------------------
+
−
I can look into it.  I have thought about a DB driven approach before, but even with a DB back-end, we still have to think of how we present it to the typical user, and who can edit/update the database.  And, with the wiki, it is easy to undo spammer hits to the list... a DB may not be quite as simple to revert, depending upon how it's set up.
+
−
[[User:Frnzxguy|Frnzxguy]] 08:05, 04 September 2007 (EDT)
+
−
--------------------------------------------------------------------
+
−
 
+
−
== calendar extensions ==
+
−
 
+
−
I've done some research and have come up with three calendar extensions for the wiki:
+
−
 
+
−
 
+
−
with iCal: http://www.mediawiki.org/wiki/Extension:SpecialCalendar
+
−
with short blurbs: http://www.mediawiki.org/wiki/User:Hex2bit/Calendar
+
−
all: http://www.mediawiki.org/wiki/Extension:Calendar
+
−
 
+
−
I'm probably going to install one or two of these over the next few days. Any opinions? [[User:Simsong|Simsong]] 23:39, 10 September 2007 (PDT)
+
−
 
+
−
:The Hex2Bit calendar looks great, but unfortunately that's the only one that has a screenshot. Do you have a image or demonstration of the the first one (that works with iCal)? Having iCal support would be a great addition, but it's not a deal breaker for me. [[User:Jessek|Jessek]] 06:33, 12 September 2007 (PDT)
+

Revision as of 10:07, 8 August 2007

Subject: header test
From: Username <username@sendinghost.com>
To: Username <username@receivinghost.com>
Content-Type: text/plain
Date: Sat, 28 Jul 2007 11:52:35 +0200
Message-Id: <1185616355.19231.0.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit

The Message id consists of five parts:

  1. The current time as returned by the time function followed by a period. The value is dislayed in decimal and is the number of seconds since midnight on 1 Jan 1970. In the example above, 1185616355 refers to Sat, 28 Jul 2007 09:52:35 GMT.
  2. The process id number in decimal followed by a period
  3. The third value starts at zero but may increase as more messages are sent. It is also followed by a period
  4. The word camel followed by an '@'
  5. If the canonical hostname can found, it is used. Otherwise the hostname

The Message id format comes from the function camel_header_msgid_generate in evolution-data-server/camel/camel-mime-utils.c.

Retrieved from "http://www.forensicswiki.org/w/index.php?title=Talk:Upcoming_events&oldid=7299"
Personal tools
Namespaces

Variants
Actions
Navigation:
About forensicswiki.org:
Toolbox