Condition:  Thousands of bots trying to break into a public forum/list
Response:  Admins trying to keep out bots
Solution:  No anonymous users ever participate in the forum
Question:  What are the identity criteria for a bot?

1st of all the user does not see any bots, so it is logical to doubt the admin.
Admin is not interested what users think, she/he does what it takes to keep the forum "safe and functional".

Question/Hypothesis:  In an organic/bio gardening forum, there may be thousands of users, but there haven't many bot attacks.  Why do bots attack linux forums in specific (if they do)?

Aaaahhaaaahhh!!

RIP Tom Petty, I'll have to do one for him too now.

Can you export virtual cup cakes out of the Netherlands without virtual dogs sniffing them?
I thought I'd lure you in taking the stand on this discussion, but you resist.

I did a little research on dconf, and there exist such a thing as dconf editor, some gnomy gui clicky thing.
The "funny" thing is, it does not edit all that dconf controls and there are warnings that editing can break
your system.  It is like playing with the wheel of an airplane with autopilot on.  Only the button that turns
off the autopilot can affect the plane.

I am infatuated with UUID (as a necessity) and the ability of iPv6.  Intercepting a few packets can send
special forces to your door and live evidence of who said what.  It is freedom of speech after all, not freedom
to write in public.

where is the LIKE button when you really need one!

@greenjeans, I have promised mother @golinux that I will behave if I am to stay here so ....... no comment

I think that Devuan gave it one hell of a shot.  It took the impossible, jessie w/o systemd, and made it real.  The route as I understand it is either to fork its own distribution with what it already has been able to cleanse or progressively fall further and further behind Debian.  When systemd progressively expands its domination, in a distribution supported by thousands of developers and package managers, it is not ability or good will, it is man-hours.  When you have thousands intentionally destroying, it will not matter how well and how fast your small team builds.  The outcome will be total destruction.

If devuan developers were counting for a surge of funding of their revolutionary project, I think they are naive idealists.  And I am sorry for their expected disappointment.  Money goes with money, interests go with money and interests, and that is h/w manufacturers, consulting, and "control of information".  Either they will vanish or not do what they have been doing.

What do we have?  A good base, a springboard, to do things on our own.  Are we willing and able?  Who prevents any of us to switch a functional ascii or ceres to debian only repositories, block out "apt-get dist-upgrade" from ever running again, and simply do debian "apt upgrade" of what already exists and works, while keeping our own cache/repository?  If something comes up with an non-existing dependency get the source, hack-it patch-it, and go.  Hopefully share your success and maybe collectively we can go a step further.

Out of curiosity I have a buster and sid distributions and three days of being unattended had a storm of updates.  It is not just updated packages it is "new" packages and "purged" packages that make those distributions functional.
Devuan and Refracta have provided many of us the ability to fork our own projects.  The torch has been passed and we should be thankful of those three-ten years of hard work that was handed to us.  It is not over till we say it is over.  Manjaro, just like Ubuntu is sold pre-installed now in expensive hardware.  The easy way is sweet.

If you have a consumerist kind of attitude demanding better service and support chances are you were here for all the wrong reasons.

The struggle must go on at all costs.  Otherwise we should be cut off from the grid and head for the hills on foot, if you know what I mean.

One important difference is that with a backup if your hardware blows up and you need to restore to a very different machine, it may not work or it would take some hacking and modifying to make it work.
With refracta you get a live system that can boot pretty much anywhere (read on the differences of uefi/non-uefii images).  Then you install from that live image into the new machine and you are ready to go.

I am sold.  This is a gift to all of us unable to create consistently a live image of our system.

motherinlaw milfpassword, I think you just have the hots for your mother in law.  Which is OK

A while ago I used a script reading the ip, writing it to a file, then use a terminal based email to mail it to me.

I understand the focus of Devuan is to make Debian work without systemd, not to fork from debian.  The instant a distribution is forked it isn't ever coming back.  Meanwhile debian has about 50,000 pkgs and a zillion package maintainers and developers working on them.  It would be impossible to fork and maintain this capacity with a small group of people.  Even with 500 pkgs installed in debian it is constantly raining updates with no intention to work without systemd.
I am not trying to come up with excuses for Devuan but I see this as part of what Debian SHOULD have been doing to be fair on its tradition.  I believe debian died with wheezy and this is debian-systemd or debian2.  Devuan is the continuation of true debian.

I wrote a small aricle in my site about how I think that debian is a specific fork of devuan.

he did say "busybox-syslogd and syslog-ng"

I can't believe this is out for so long and nobody caught it.  Ceres has a single repository, ascii has exactly the same repositories as jessie (security, update, etc).  Just switch all your jessie lines into ascii.  If you had looked at the proper web page it lists exactly the proper repositories.  This is for future reference as too much time has gone by.

I have in a way parked all my devuan installations waiting for developers to deal with existing issues.
It appears that the summer siesta hasn't ended yet or things haven't gotten in a rolling mode again.
It appears as a strange decision to release Devuan 1 and then go on vacation, it just makes the project
look less professional, or serious.  Maybe they should have waited for September.

In any case, those more serious about bug fixing seem to have concentrated on the list, after all they
are mostly debian escapees and they will not adopt to anything better.  The logs of the list are next
to impossible to search and locate meaningful information.  It has been that way on debian since the
stone age and remains the same in devuan.

Personally if it wasn't for the good work from refracta/fsmithred I would have lost all interest in this system.

For all it is worth I see yt in qupzilla, midori, and most of the times with older videos smtube/smplayer works well too.
I was really surprised with midori playing them well.  No pulse-ation, only alsa-tion.

$ ls /etc/apt/trusted.gpg.d

-rw-r--r-- 1 root root 7.4K May 25 21:17 debian-archive-stretch-automatic.gpg
-rw-r--r-- 1 root root 7.4K May 25 21:17 debian-archive-stretch-security-automatic.gpg
-rw-r--r-- 1 root root 2.3K May 25 21:17 debian-archive-stretch-stable.gpg
-rw-r--r-- 1 root root 3.6K Nov 22  2016 devuan-keyring-2016-archive.gpg
-rw-r--r-- 1 root root 2.2K Nov 22  2016 devuan-keyring-2016-cdimage.gpg
-rw-r--r-- 1 root root 5.1K Nov 30  2014 debian-archive-jessie-automatic.gpg
-rw-r--r-- 1 root root 5.1K Nov 30  2014 debian-archive-jessie-security-automatic.gpg
-rw-r--r-- 1 root root 2.8K Nov 30  2014 debian-archive-jessie-stable.gpg
-rw-r--r-- 1 root root 3.7K Nov 30  2014 debian-archive-wheezy-automatic.gpg
-rw-r--r-- 1 root root 2.8K Nov 30  2014 debian-archive-wheezy-stable.gpg

to

$ ls /etc/apt/trusted.gpg.d

-rw-r--r-- 1 root root 3.6K Nov 22  2016 devuan-keyring-2016-archive.gpg
-rw-r--r-- 1 root root 2.2K Nov 22  2016 devuan-keyring-2016-cdimage.gpg

Should something like this produce errors, or only devuan specific packages come from devuan and the rest from debian?