On Friday, 5 June 2015 at 02:03:48 UTC, Vladimir Panteleev wrote:
> On Friday, 5 June 2015 at 02:02:11 UTC, IgorStepanov wrote:
>> Sorry if this question has been raised but is the reason for the inability to edit posts?
>
> Posts are not editable because once sent, they are relayed to the NNTP server, mailing lists, and users' email inboxes.
>
>> Will be this feature implemented sometime?
>
> Only when it becomes possible to edit a sent email.

Ok, why we use email/NNTP server instead of simple database/file storage?
Do we use some free mail server, or we must support some old infrastructure?

On Friday, 5 June 2015 at 02:11:17 UTC, IgorStepanov wrote:
> On Friday, 5 June 2015 at 02:03:48 UTC, Vladimir Panteleev wrote:
>> On Friday, 5 June 2015 at 02:02:11 UTC, IgorStepanov wrote:
>>> Sorry if this question has been raised but is the reason for the inability to edit posts?
>>
>> Posts are not editable because once sent, they are relayed to the NNTP server, mailing lists, and users' email inboxes.
>>
>>> Will be this feature implemented sometime?
>>
>> Only when it becomes possible to edit a sent email.
>
> Ok, why we use email/NNTP server instead of simple database/file storage?
> Do we use some free mail server, or we must support some old infrastructure?

Yes, this forum was created explicitly to replace Web-News, an NNTP newsreader. Initially all communication was done via NNTP (Web-News or a desktop NNTP client) and mailing lists. The last time I checked, only 50% of posters used forum.dlang.org, others used NNTP or mailing lists.

If it weren't for this requirement, we might have used an off-the-shelf web forum, such as phpBB.

On Friday, 5 June 2015 at 02:14:08 UTC, Vladimir Panteleev wrote:
> On Friday, 5 June 2015 at 02:11:17 UTC, IgorStepanov wrote:
>> On Friday, 5 June 2015 at 02:03:48 UTC, Vladimir Panteleev wrote:
>>> On Friday, 5 June 2015 at 02:02:11 UTC, IgorStepanov wrote:
>>>> Sorry if this question has been raised but is the reason for the inability to edit posts?
>>>
>>> Posts are not editable because once sent, they are relayed to the NNTP server, mailing lists, and users' email inboxes.
>>>
>>>> Will be this feature implemented sometime?
>>>
>>> Only when it becomes possible to edit a sent email.
>>
>> Ok, why we use email/NNTP server instead of simple database/file storage?
>> Do we use some free mail server, or we must support some old infrastructure?
>
> Yes, this forum was created explicitly to replace Web-News, an NNTP newsreader. Initially all communication was done via NNTP (Web-News or a desktop NNTP client) and mailing lists. The last time I checked, only 50% of posters used forum.dlang.org, others used NNTP or mailing lists.

Interestingly, they do it because they are accustomed, or they have a handy desktop/mobile applications?

On 6/4/2015 8:04 AM, Vladimir Panteleev wrote:
> http://beta.forum.dlang.org/
>
> Many major and minor improvements.
>
> Some major ones:
>
> - dlang.org theme, fully responsive and mobile-friendly
> - keyboard navigation in all views
> - automatically saved post drafts
> - get notified of new posts and replies with subscriptions
> - full text search
> - by persistent request, a new view mode (vertical-split)
> - post to mailing lists
> - even faster, believe it or not.
>
> This update is the sum of 256 commits over 34 days of development.
>

Pretty dazz! I also like the new stats display at the top. Just for fun eye candy, you could juice that up and show a graph of the stats for the past month or whatever.

Another idea:

Consider the display:
 http://beta.forum.dlang.org/group/general
and compare with:

http://www.digitalmars.com/d/archives/digitalmars/D/I_won_a_school_game-creation_competition_263965.html

In particular:

Vladde Nordholm (12/12) May 30 So hey everyone! I am very hap...
◦  Marcin Szymczak (3/3) May 30 That is great news! Congratula...
◦  extrawurst (3/16) May 30 here is the link i suppose: ...
◾  Dennis Ritchie (3/21) May 30 The game starts normally but w...
◾  Vladimir Panteleev (3/8) May 30 I saw the same problem (access...
◦  Andrei Alexandrescu (2/14) May 30 Congratulations! -- Andrei...
◦  Vladde Nordholm (8/8) May 31 Quick note to Dennis and Vladi...

After each post, the first non-quoted line of text from the post is inserted. (The n/m means n = non-quoted lines and m = total lines.) This gives a nice clue which one would be most interesting to click on. Slashdot does this:


http://hardware.slashdot.org/story/15/06/04/2250233/researchers-power-a-security-camera-with-wi-fi-signals

Slashdot does it even better by expanding/contracting the clicked on post inline rather than opening a new page, and having to go back and forth between pages. I think this significantly better.

On 5 June 2015 at 11:45, Vladimir Panteleev via Digitalmars-d-announce <digitalmars-d-announce@puremagic.com> wrote:
> On Friday, 5 June 2015 at 01:42:20 UTC, Manu wrote:
>>
>> Also, oauth?
>> There is no way I would register an account to make a post unless I
>> was *really* motivated.
>
>
> What gave you the impression that you have to register an account in order to post? The front page now explicitly says that you don't need an account to post.

Ah okay. I totally missed that detail somewhere.
You seem to have fixed it, nice :)


>> It may be that we have lost potential participants because they clicked away from the page within seconds of realising there was no oauth (I definitely would).
>
>
> It's doable but just seems a little overkill to me. Every time I looked into implementing OAuth I was swamped by how overly complicated it was (or maybe I just never found a succint-enough description).

Yeah I've had the same experience. I reckon there's room for a libOAuth... I would hella-make-use-of-that!

On Friday, 5 June 2015 at 04:03:48 UTC, Manu wrote:
> Yeah I've had the same experience. I reckon there's room for a
> libOAuth... I would hella-make-use-of-that!

https://github.com/adamdruppe/arsd/blob/master/oauth.d

my implementation is a bit bizarre and tied to my cgi.d but it supports the oauth 1 flow, full client, server signing checks, and has been tested (over a year ago though) against several providers.

On Thursday, June 04, 2015 18:05:32 Andrei Alexandrescu via Digitalmars-d-announce wrote:
> Also, after thinking today about the universe and everything, I concluded that that's without a doubt the ugliest bold font created by the human civilization.

That's a bold statement. :)

- Jonathan M Davis

On 06/04/2015 10:59 PM, IgorStepanov wrote:
> On Friday, 5 June 2015 at 02:14:08 UTC, Vladimir Panteleev wrote:
>> On Friday, 5 June 2015 at 02:11:17 UTC, IgorStepanov wrote:
>>>
>>> Ok, why we use email/NNTP server instead of simple database/file
>>> storage?
>>> Do we use some free mail server, or we must support some old
>>> infrastructure?
>>
>> Yes, this forum was created explicitly to replace Web-News, an NNTP
>> newsreader. Initially all communication was done via NNTP (Web-News or
>> a desktop NNTP client) and mailing lists. The last time I checked,
>> only 50% of posters used forum.dlang.org, others used NNTP or mailing
>> lists.
>
> Interestingly, they do it because they are accustomed, or they have a
> handy desktop/mobile applications?

As nice as forum.dlang.org is, many of us just like native NNTP clients way better. I'm accessing this though Thunderbird (although I've also used claws-mail and IIRC Outlook Express for it in the past.)

Incidentally, I used to be a web forum fan, and it was this NG that introduced me to NNTP (back before this NG had a decent web interface). But then I ended up liking NNTP clients better. :)

I do use forum.dlang.org on mobile though, since I'm not aware of any worthwhile mobile NNTP client.

On 6/4/15 6:37 PM, Vladimir Panteleev wrote:
> Except for the bold part, believe it or not, it's exactly the same font
> as we use on dlang.org, size and all (Verdana 14px). And as for the bold
> part, it doesn't look so bad on Windows, so what does that say about the
> famed OS X font rendering? :D

Guess it says "let's steer clear of Verdana". -- Andrei

Am 05.06.2015 um 02:01 schrieb Vladimir Panteleev:
> On Thursday, 4 June 2015 at 21:10:13 UTC, Sönke Ludwig wrote:
>>> I don't know how things are now, but when I tried to move to
>>> Vibe.d
>>> (which was several years ago), you had to do some strange
>>> acrobatics in
>>> order to read the same connection in one fiber but write to it
>>> from
>>> another. In ae.net, reads are handled by callbacks, and all
>>> writes are
>>> delayed (data is queued and sent when the socket loop says the
>>> socket is
>>> writable), which means there is no contention and you can
>>> "write" to any
>>> socket from anywhere in the program (as long as it's in the
>>> same thread).
>>
>> This has been solved in the meantime. Reads and writes can now occur
>> concurrently in different fibers.
>
> Good to know. What about writing from multiple fibers to the same
> connection (e.g. an IRC client that needs to send PINGs from a timer
> fiber and also announce events coming from other fibers)? IIRC a
> connection's input/output streams needed to be explicitly associated
> with a fiber?

You'd need to use a TaskMutex to serialize access to the connection in that case, but no explicit ownership management is needed (that has actually been removed from the API back then). I was thinking about making this the default behavior, though (instead of throwing an assertion error for mutual write access). After all that's what happens with normal blocking I/O and threads, too.