[DVC]DevCoin - Official Thread - Moderated

[develCuy]

All file custodians are now synced and ready for round 101.

Happy holidays!

- develCuy

[Vlad2Vlad]

All file custodians are now synced and ready for round 101.

Happy holidays!

- develCuy

101

10100

Excellent...   

[novacadian]

Wishing everyone in the DevCoin Community a happy and prosperous 2020!

- Nova

[realdantreccia]

Wishing everyone in the DevCoin Community a happy and prosperous 2020!

- Nova

You as well. Thanks.

[Wekkel]

That 2020 may bring good things 

[unicode.03C0]

Dedcoin
Why are not fixing vulnerable problems that bitcoin already fix

[novacadian]

Dedcoin
Why are not fixing vulnerable problems that bitcoin already fix

Hi unicode.

My understanding is that the Developer Admin position has recently been vacated with the recent resignation of ctya. Perhaps knotwork may be able to address your question being one of the original Devs of the project.

If you could offer some links or more details as to the vulnerabilities it may be helpful in getting an answer to your question.

- Nova

[realdantreccia]

Ignorance values - stay tuned.

[ranlo]

Hi, DVC admins! I want to start off by apologizing for my absence. Over the past couple years I've gone through major life changes and my health has deteriorated significantly. Mixed with DVC as a whole having been a bit stagnant at the time, I continued what I could but didn't really see much going on regarding my jobs (Inspector Factotum, for example, I had been doing, but there wasn't a lot of writing). I want to say that I appreciate you all keeping the project alive and rebooting what we all spent so much time and effort on in the past!

I'm finally getting to a point where my health is at least normalized (though still fairly bad), but I would be happy to rejoin as an administrator in the future when I'm to a point where I feel my contributions would warrant holding a position.

Thank you all again!

[Vlad2Vlad]

Ignorance values - stay tuned.

Soon? 

[novacadian]

Hi, DVC admins! I want to start off by apologizing for my absence. Over the past couple years I've gone through major life changes and my health has deteriorated significantly. Mixed with DVC as a whole having been a bit stagnant at the time, I continued what I could but didn't really see much going on regarding my jobs (Inspector Factotum, for example, I had been doing, but there wasn't a lot of writing). I want to say that I appreciate you all keeping the project alive and rebooting what we all spent so much time and effort on in the past!

I'm finally getting to a point where my health is at least normalized (though still fairly bad), but I would be happy to rejoin as an administrator in the future when I'm to a point where I feel my contributions would warrant holding a position.

Thank you all again!

Nice to hear that things are turning around for you, ranlo. Your input will always be welcome when you feel ready.

- Nova

[realdantreccia]

Hi, DVC admins! I want to start off by apologizing for my absence. Over the past couple years I've gone through major life changes and my health has deteriorated significantly. Mixed with DVC as a whole having been a bit stagnant at the time, I continued what I could but didn't really see much going on regarding my jobs (Inspector Factotum, for example, I had been doing, but there wasn't a lot of writing). I want to say that I appreciate you all keeping the project alive and rebooting what we all spent so much time and effort on in the past!

I'm finally getting to a point where my health is at least normalized (though still fairly bad), but I would be happy to rejoin as an administrator in the future when I'm to a point where I feel my contributions would warrant holding a position.

Thank you all again!

I almost died from health issues 3 years ago. Your contributions are always appreciated. Welcome back.

[Vlad2Vlad]

Hi, DVC admins! I want to start off by apologizing for my absence. Over the past couple years I've gone through major life changes and my health has deteriorated significantly. Mixed with DVC as a whole having been a bit stagnant at the time, I continued what I could but didn't really see much going on regarding my jobs (Inspector Factotum, for example, I had been doing, but there wasn't a lot of writing). I want to say that I appreciate you all keeping the project alive and rebooting what we all spent so much time and effort on in the past!

I'm finally getting to a point where my health is at least normalized (though still fairly bad), but I would be happy to rejoin as an administrator in the future when I'm to a point where I feel my contributions would warrant holding a position.

Thank you all again!

I almost died from health issues 3 years ago. Your contributions are always appreciated. Welcome back.

Why don’t you go write a book about it or something?   

[develCuy]

Hey everybody,

I have to inform that round 102 started with the already known fallback reduction, which happens when file custodians aren't in sync. This time we have learned something knew, as soon as the custodians are in sync, the network goes back to normal, producing 50k new Devcoins per block. The fallback reduction started on block 408000 and stopped on block 408322, so we have 322 blocks with the penalty.

What was the cause?

In the first place I found that one custodian synced too late, again. For the safety of the network, we need a new file custodian to take over. In the second place, two file custodians were affected by a miss-configuration in the DNS, which forced redirection to HTTPS, this is a known bug that has been fixed already and is included in the latest release of Devcoin core. It is very well known that the world is deprecating HTTP, so we are now forced to upgrade our nodes to the latest release, or at least patch them with the HTTPS fix. More info here: https://github.com/devcoin/core/issues/77 At the time of writting, 20% of the network is running Devcoin 0.8.6

Let's make round 103 pass smooth!

Go go Devcoin!

- develCuy

[Traxo]

Happy birthday, Vitalik MarkM! =)

[ranlo]

Hey everybody,

I have to inform that round 102 started with the already known fallback reduction, which happens when file custodians aren't in sync. This time we have learned something knew, as soon as the custodians are in sync, the network goes back to normal, producing 50k new Devcoins per block. The fallback reduction started on block 408000 and stopped on block 408322, so we have 322 blocks with the penalty.

What was the cause?

In the first place I found that one custodian synced too late, again. For the safety of the network, we need a new file custodian to take over. In the second place, two file custodians were affected by a miss-configuration in the DNS, which forced redirection to HTTPS, this is a known bug that has been fixed already and is included in the latest release of Devcoin core. It is very well known that the world is deprecating HTTP, so we are now forced to upgrade our nodes to the latest release, or at least patch them with the HTTPS fix. More info here: https://github.com/devcoin/core/issues/77 At the time of writting, 20% of the network is running Devcoin 0.8.6

Let's make round 103 pass smooth!

Go go Devcoin!

- develCuy

If I can get pings each month for the new files I can ensure that they're uploaded to my mirror within 24h of a PM going forward (usually much faster, within minutes, but just in case I'm asleep and have to take off immediately after I wake up or whatever).

[FuzzyBear]

Hey everybody,

I have to inform that round 102 started with the already known fallback reduction, which happens when file custodians aren't in sync. This time we have learned something knew, as soon as the custodians are in sync, the network goes back to normal, producing 50k new Devcoins per block. The fallback reduction started on block 408000 and stopped on block 408322, so we have 322 blocks with the penalty.

What was the cause?

In the first place I found that one custodian synced too late, again. For the safety of the network, we need a new file custodian to take over. In the second place, two file custodians were affected by a miss-configuration in the DNS, which forced redirection to HTTPS, this is a known bug that has been fixed already and is included in the latest release of Devcoin core. It is very well known that the world is deprecating HTTP, so we are now forced to upgrade our nodes to the latest release, or at least patch them with the HTTPS fix. More info here: https://github.com/devcoin/core/issues/77 At the time of writting, 20% of the network is running Devcoin 0.8.6

Let's make round 103 pass smooth!

Go go Devcoin!

- develCuy

Had a PM basically blaming me for this and asking me to step down my role as custodian so I may be kicked from the community... been a fun and enjoyable 8 years and sorry to see it end like this for a file that took me just over a week to upload. If it that crucial then need MORE custodians to help not less. some very backwards thinking going on and I can suddenly see why ctya was having issues. I will stop everything immediately if I do leave as there is no point when the fun has stopped.

Fuzzybear

[ranlo]

Hey everybody,

I have to inform that round 102 started with the already known fallback reduction, which happens when file custodians aren't in sync. This time we have learned something knew, as soon as the custodians are in sync, the network goes back to normal, producing 50k new Devcoins per block. The fallback reduction started on block 408000 and stopped on block 408322, so we have 322 blocks with the penalty.

What was the cause?

In the first place I found that one custodian synced too late, again. For the safety of the network, we need a new file custodian to take over. In the second place, two file custodians were affected by a miss-configuration in the DNS, which forced redirection to HTTPS, this is a known bug that has been fixed already and is included in the latest release of Devcoin core. It is very well known that the world is deprecating HTTP, so we are now forced to upgrade our nodes to the latest release, or at least patch them with the HTTPS fix. More info here: https://github.com/devcoin/core/issues/77 At the time of writting, 20% of the network is running Devcoin 0.8.6

Let's make round 103 pass smooth!

Go go Devcoin!

- develCuy

Had a PM basically blaming me for this and asking me to step down my role as custodian so I may be kicked from the community... been a fun and enjoyable 8 years and sorry to see it end like this for a file that took me just over a week to upload. If it that crucial then need MORE custodians to help not less. some very backwards thinking going on and I can suddenly see why ctya was having issues. I will stop everything immediately if I do leave as there is no point when the fun has stopped.

Fuzzybear

I missed this event but I really hope this isn't the case. You've been a major part of DVC for a long time while we worked together. I believe I was also removed as file custodian but I had stopped uploading files when I stopped getting messages, .

[realdantreccia]

Hey everybody,

I have to inform that round 102 started with the already known fallback reduction, which happens when file custodians aren't in sync. This time we have learned something knew, as soon as the custodians are in sync, the network goes back to normal, producing 50k new Devcoins per block. The fallback reduction started on block 408000 and stopped on block 408322, so we have 322 blocks with the penalty.

What was the cause?

In the first place I found that one custodian synced too late, again. For the safety of the network, we need a new file custodian to take over. In the second place, two file custodians were affected by a miss-configuration in the DNS, which forced redirection to HTTPS, this is a known bug that has been fixed already and is included in the latest release of Devcoin core. It is very well known that the world is deprecating HTTP, so we are now forced to upgrade our nodes to the latest release, or at least patch them with the HTTPS fix. More info here: https://github.com/devcoin/core/issues/77 At the time of writting, 20% of the network is running Devcoin 0.8.6

Let's make round 103 pass smooth!

Go go Devcoin!

- develCuy

Had a PM basically blaming me for this and asking me to step down my role as custodian so I may be kicked from the community... been a fun and enjoyable 8 years and sorry to see it end like this for a file that took me just over a week to upload. If it that crucial then need MORE custodians to help not less. some very backwards thinking going on and I can suddenly see why ctya was having issues. I will stop everything immediately if I do leave as there is no point when the fun has stopped.

Fuzzybear

Unless anything comes from this account on here it is not from me. =P

Just making that clear. Also FuzzyBear, I support you. Your efforts are very appreciated here

[realdantreccia]

Hi, DVC admins! I want to start off by apologizing for my absence. Over the past couple years I've gone through major life changes and my health has deteriorated significantly. Mixed with DVC as a whole having been a bit stagnant at the time, I continued what I could but didn't really see much going on regarding my jobs (Inspector Factotum, for example, I had been doing, but there wasn't a lot of writing). I want to say that I appreciate you all keeping the project alive and rebooting what we all spent so much time and effort on in the past!

I'm finally getting to a point where my health is at least normalized (though still fairly bad), but I would be happy to rejoin as an administrator in the future when I'm to a point where I feel my contributions would warrant holding a position.

Thank you all again!

I almost died from health issues 3 years ago. Your contributions are always appreciated. Welcome back.

Why don’t you go write a book about it or something?   

I did. And those methods cured me. Maybe 1 day people will shine a light on me and the world of people that need something to battle that disease will stumble upon my book. I'd make it free to use if possible at a later date. I lost the copy of the one I submitted to Amazon. Perhaps I'll just change that price to zero when I find my amazon password for that account...