PUBLIC MARKS with search thread

The problem is that, aside from a thread in Etsy's forums (which is almost entirely used by sellers, not buyers), Etsy has not notified users of the change in privacy settings or policy.

The ad-hoc mailing list is cool. But you never know when a discussion stop and restart. There are some ongoing discussions I have with friends which last for years but at a very irregular pace and sometimes with 6 months of inactivity.

The last year and a half I have been confronted to a similar issue:

1. It costs to create a mailing list (admin work, email addresses, etc.)

2. Archives are good, specifically in a work context. It helps rebuild context for people who are late in the discussion. It helps remembering some decisions.

3. People do not know how to use dynamic folders for managing their emails. (Unfortunately) (All my mails of the last 20 years are in dated space folder with dynamic folders created for the current needs)

4. People do not know how to unsubscribe a mailing-list, but they know how to cc someone.

5. Some mails really belongs to more than one context, and it is a struggle for some people to know where to send them.

Some thoughts about a possible system (all issues not solved)

1. So I was wondering about a system where each mail has a unique id (already the case) and is saved online with its own archive.

2. The mail before being sent to the recipients has its header modified with a Archived-At: containing the URI of this specific mail.

3. It could have another header X-Thread-Archive-at: with the list or content of all emails in this thread.

4. The ACLs are dynamically set on each Web individual archive depending on who has been copied to this email.

5. The ACLs are inclusive for any new persons who is being added to the thread, including previous messages.

6. There is a possibility to tag and/or do positive bias filtering on emails the same way we do with spam, in a working context we would have a kind of shared vocabulary of contexts dynamically created. So the mails would be showing in dynamic contextual views.

Posted by: karl at October 13, 2010 12:54 AM

Speaking as a long-time Web Developer, I'm appalled by the dismissive

and insulting attitude taken by the constituency dictating HTML 5 as

pertains to the standards that myself and those like me are perfectly

capable of understanding, by declaring repeatedly that we're a bunch of

morons who can't understand resource/representation or anything else

the vendors are hell-bent on changing, as justification for said

changes ignoring those well-understood standards.

Which motivates me to participate in this thread, because I don't want

that vendor-centric approach to pollute HTTPbis, rendering the spec so

large and unwieldy that only browser vendors could ever hope to

understand its meaning, in terms of what they've implemented. A big,

emphatic -1 to the notion that HTTPbis should follow HTML 5 down the

road of standardizing error correction behavior for user agents, for

C-D or anything else.

MIME was invented originally for email, based on general principles of 'messaging', foundational architecture. The role of MIME was to extend Internet messaging from ASCII-only plain text (other character sets, images, rich documents, etc.) The basic architecture of complex content messaging is:

Apolis Activism is an independent contemporary brand that began with dreams and thread. Three brothers — Raan, Shea, and Stenn Parton — created a unique bridge between commerce and sustainable development. Through their travels they discovered stories of struggle and survival from visionaries and activists for change. These experiences shaped their perspective, resulting in a union of ideal and action. They anchored this vision in the word Apolis, which translates as a “global citizen” — where there are no flags and no borders, humanity is our common cause and greatest priority.

Threading

We’re quite familiar with the idea of writing a program that follows a specific sequence of steps as outlined in, say, a main() function. A Thread is also a series of steps with a beginning, a middle, and an end. A thread’s sequence, however, can run independently of the main program. In fact, we can launch any number of threads at one time and they will all run concurrently. Visit the Java site for a more involved explanation.

This is incredibly useful when it comes to data mining, as we can have separate threads retrieving different pieces of information from the network. If one gets stuck or has an error, the entire program won’t grind to a halt, since the error only stops that individual thread. To create independent, asynchronous threads, we simply extend the Thread class.

tldr is an application for navigating through large-scale online discussions. The application visualizes structures and patterns within ongoing conversations to let the user browse to content of most interest. In addition to visual overviews, it also incorporates features such as thread summarization, non-linear navigation, multi-dimensional filtering, and various other features that improve the experience of participating in large-discussions.