Great, you are right to be conscious, here the same, not everybody are taking care but situation is really better now that what it was a month ago. Stay safe Trevor.
It’s a small thing, but I just saw that EOS broke into the top 20 over at distrowatch. Moving in the right direction.

What is the next step? In my opinion, the magical journey continues. The distro will become more and more stable and stable. After many years of using Linux, I can say that I have seen few such friendly communities as EOS has. Happy birthday, EOS!
Jolly good first year. Well done everyone!
Genuine congratulations and thanks to the whole team that has allowed us to benefit from such an excellent distro with so much choice and functionality and for sharing their time, bug hunting, scripting and sharing their advice on the worlds friendliest forum - that is where you win people over and enthuse them to learn.
Keep safe

You certainly don’t have to agree with us on anything but you already made a thread about this and sent us a pm about it. We and the community have tried to help you and we already said we didn’t have a solution for this at this moment. I am very sorry you are encountering this issue, but you cannot say we didn’t try to help you.
I completely understand your inconvenience, I hope you can understand my slight annoyance in you reporting an issue on several threads, with the illiusion that we have done nothing for you to look into the issue.
They are starting to take EOS more seriously in the media.
Correct me if i am wrong but it is my understanding that the r8169 is a kernel module that automatically loads for the realtek. The r8168 was added because of issues users had with the r8169. These issues were related to poor performance or not working at all. Supposedly the r8168 can’t be removed say’s @garybean but i find that hard to understand. I would think that one needs to try blacklisting it or removing it and trying with the r8169 only. There are a lot of users on here that have the chipset that uses the r8168 including myself and both modules are listed but mine is using the r8169. I have no issues but then again i am not using hibernation or suspend modes. There is the possibility to create a suspend, resume service but someone has to try it that has the issue and test it. I am wondering if when the computer goes into hibernation or suspend mode and then comes out or resumes that it may be either not loading the module or selecting the wrong module? I don’t really know.
…okay, I concede to being slightly annoying
While true I have made more than one thread, one response was to another user with the same issue.
From a user view, it seems reasonable that the issue be acknowledged in a more direct way (such as in the Wiki) so as to alert other users having this issue – thus reducing the issue being reintroduced into the forum.
If I have been lacking in showing my appreciation to the EndeavourOS team, please let me correct that and emphasize that I very much appreciate the effort and expense spent by the EndeavourOS team
Next time, do it in a less annoying way, because I’m really irritated by this sort of behaviour, certainly if you really want us to take it seriously.
I want to give my Congrats to everyone on the EndeavourOS Team, the Mods, the Community and all the supporters of this project!
I jumped on board on the first release and I still have it running to this day. Yes I have reinstalled it a few times in the beginning because of sound issues that @ricklinux an I were trying to fix the issue which ended in a bust with the onboard HDMI Sound / video. Time for a New Video card and the HDMI sound was fixed… Lol
Anyrate I have enjoyed EndeavourOS and I use it as my base install on most things, I even made a guide abd script to add the other stuff I wanted after the install. I am into Spectrwm window manager for now, and it works great on top EndeavourOS… Yes I did the BTW thing but I like the Endeavour way better… 
Thank you Endeavour Team for a Great OS and may this next year be a Great One Also!
Congrats!

LLAP
May have stumbled onto cause of my issue.
removed r8168 package, REBOOTED, r8169 appears under “nmcli”
ethernet network connection working!
(someone added the r8168 package to the EndeavourOS install?)
So is there success now? By the way, I also have a boot message on Debian Sid related to r8168 / 8169.
Awesome. Looks like a good point to see what’s new. 
I really dig personal commands!!! 
After a long hiatus, romanian translation is on.
Is the deepin not being available in the arm version out of prejudice or is it because of the deepin (distro) not having arm support?
There is no ARM support for Deepin.
You mean that when deepin supports arm you will make the deepin version available for the arm architecture?