October 16, 2019
On Saturday, 12 October 2019 at 14:06:47 UTC, bauss wrote:
> On Saturday, 12 October 2019 at 13:51:57 UTC, NonNull wrote:
>> On Tuesday, 8 October 2019 at 17:15:30 UTC, bauss wrote:
>>> On Tuesday, 8 October 2019 at 09:52:40 UTC, Andrea Fontana wrote:
>>>> On Tuesday, 8 October 2019 at 08:56:26 UTC, zoujiaqing wrote:
>>>>> [...]
>>>>
>>>> So finally we have a working xml parser!
>>>
>>> https://github.com/DiamondMVC/Diamond/tree/master/xml
>>>
>>> Since 9 months ago.
>>
>> https://diamondmvc.org/ --- certificate has expired
>
> Already aware of it and will fix it soon. Just haven't gotten around to it. http should work just fine.

Its a bad sign cus all modern browsers will show a red flag on non-https websites. Its serious than you seem to think. You can use an automated letsencrypt daemon or service
October 16, 2019
On Wednesday, 16 October 2019 at 20:46:06 UTC, aberba wrote:
> On Saturday, 12 October 2019 at 14:06:47 UTC, bauss wrote:
>> On Saturday, 12 October 2019 at 13:51:57 UTC, NonNull wrote:
>>> On Tuesday, 8 October 2019 at 17:15:30 UTC, bauss wrote:
>>>> On Tuesday, 8 October 2019 at 09:52:40 UTC, Andrea Fontana wrote:
>>>>> On Tuesday, 8 October 2019 at 08:56:26 UTC, zoujiaqing wrote:
>>>>>> [...]
>>>>>
>>>>> So finally we have a working xml parser!
>>>>
>>>> https://github.com/DiamondMVC/Diamond/tree/master/xml
>>>>
>>>> Since 9 months ago.
>>>
>>> https://diamondmvc.org/ --- certificate has expired
>>
>> Already aware of it and will fix it soon. Just haven't gotten around to it. http should work just fine.
>
> Its a bad sign cus all modern browsers will show a red flag on non-https websites. Its serious than you seem to think. You can use an automated letsencrypt daemon or service

On latest Firefox, i'm getting...

> Warning: Potential Security Risk Ahead

> Firefox detected an issue and did not continue to diamondmvc.org. The website is either misconfigured or your computer clock is set to the wrong time.

> It’s likely the website’s certificate is expired, which prevents Firefox from connecting securely. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.

> What can you do about it?

> Your computer clock is set to October 16, 2019. Make sure your computer is set to the correct date, time, and time zone in your system settings, and then refresh diamondmvc.org.

> If your clock is already set to the right time, the website is likely misconfigured, and there is nothing you can do to resolve the issue. You can notify the website’s administrator about the problem.


Not everybody will take that as a trivial issue.
October 17, 2019
On 17/10/2019 9:46 AM, aberba wrote:
> On Saturday, 12 October 2019 at 14:06:47 UTC, bauss wrote:
>> On Saturday, 12 October 2019 at 13:51:57 UTC, NonNull wrote:
>>> On Tuesday, 8 October 2019 at 17:15:30 UTC, bauss wrote:
>>>> On Tuesday, 8 October 2019 at 09:52:40 UTC, Andrea Fontana wrote:
>>>>> On Tuesday, 8 October 2019 at 08:56:26 UTC, zoujiaqing wrote:
>>>>>> [...]
>>>>>
>>>>> So finally we have a working xml parser!
>>>>
>>>> https://github.com/DiamondMVC/Diamond/tree/master/xml
>>>>
>>>> Since 9 months ago.
>>>
>>> https://diamondmvc.org/ --- certificate has expired
>>
>> Already aware of it and will fix it soon. Just haven't gotten around to it. http should work just fine.
> 
> Its a bad sign cus all modern browsers will show a red flag on non-https websites. Its serious than you seem to think. You can use an automated letsencrypt daemon or service

Or throw a CDN in front of it and let e.g. CloudFlare handle it for you.
October 18, 2019
On Tuesday, 15 October 2019 at 12:28:40 UTC, Dejan Lekic wrote:
> On Tuesday, 8 October 2019 at 08:56:26 UTC, zoujiaqing wrote:
>> RapidXml is an attempt to create the fastest XML parser possible, while retaining useability, portability and reasonable W3C compatibility. It is an in-situ parser written in modern C++, with parsing speed approaching that of strlen function executed on the same data. RapidXml has been around since 2006, and is being used by lots of people.
>
> So... you ported the RapidXml code, yet you do not mention this project anywhere, no credits to its authors, no information about the original license, etc? Am I summing this up correctly?

Sorry, I didn't pay attention to the details.

Solved:
 1. Add C++ version copyright to source code
 2. Add C++ version link to README.md

October 18, 2019
On Tuesday, 15 October 2019 at 14:12:45 UTC, drug wrote:
> On 10/15/19 3:28 PM, Dejan Lekic wrote:
>> On Tuesday, 8 October 2019 at 08:56:26 UTC, zoujiaqing wrote:
>>> RapidXml is an attempt to create the fastest XML parser possible, while retaining useability, portability and reasonable W3C compatibility. It is an in-situ parser written in modern C++, with parsing speed approaching that of strlen function executed on the same data. RapidXml has been around since 2006, and is being used by lots of people.
>> 
>> So... you ported the RapidXml code, yet you do not mention this project anywhere, no credits to its authors, no information about the original license, etc? Am I summing this up correctly?
>
> In fact that's really disappointing

Added some information to source code and README.md :)

C++ version copyright is:
Copyright (C) 2006, 2009 Marcin Kalicinski (For C++ Version 1.13)
1 2
Next ›   Last »