If anything, I believe a reporting feature on Fedi is rather pointless, unless you run a big server with lots of users on it.
But if you're just a single user instance, it's just pointless.
As I stated, my goal isn't to have a reporting feature, I only want to know which one has it as an optional feature rather than either mandatory or not at all.
Because it seems to be the only feature that either available and you can't turn it off, or just isn't there.
寮 (ryo@social.076.moe)'s status on Thursday, 23-Feb-2023 10:56:25 JST
寮Does anyone know a Fediverse microblogging soft that has an optional reporting feature?
On the big 3 (Mastodong, Pleroma, and Misskey) it's mandatory, so you can't disable it.
On the other hand, on GNU Social no reporting feature exists at all.
And Mastodong loves to hardcode many features while all the others let you customize or even turn off, which is why I'm wondering about whether an optional reporting one exists or not.
Because reports are funny to read because 99% of the reports are being to be invalid, while at the same time because they're invalid they're typically a massive burden for instance admins.
Both userland and developer reich are divided into 2 camps: the "keep things simple and minimal" camp, and the "let's stuff everything into 1 pile of mess that breaks so much that it creates a new industry of post-release bug fixing" camp.
Governments and their corporations, soydevs, and normalcattle tend to be exclusively in the latter camp.
OK, after watching this video, I have to add a new requirement to the list:
・Drawing must look good, which immediately disgards literally every single character in that video.
Yea, it depends on the software in question.
Personally anything that can be used as an attack vector I prefer to have the latest version of, unless there are known exploits in the latest version.
Or just switch to something that's already secure by default, like replacing sudo for doas for example.
Though it's not always possible, for example replacing OpenSSL for LibreSSL will break lots of Linux soft that rely on it.
> I think i2pd itself is (was?) unstable. In the past I had it segfaulted every after a while on other distro (not Debian-based) too. But on Debian I have switched to their upstream binary since I experienced those bugs.
Thanks for proving my point.
Yes, I know that i2pd isn't often breaking on specific distro's, like it was working fine on Devuan, Artix, and kind of OK-ish on OpenBSD on version 2.44, but on FreeBSD it would crash all the time.
2.45 would crash if you have UPnP enabled, which I know because I even had the very guy who fixed that bug in my IRC server at the time, and 2.45.1 had an exploit that allowed the entire network to get DDoS'd.
This used to be a big problem in the past compared to now, but the problem still exists because too many devs sadly can't seem to make anything without relying on external dependencies (or at the very least make static builds instead of dynamic).
But I find Devuan and all the other Debian-based distro's to be a massive disservice when it comes to packages.
Even now in 2023 it still comes with lots of software versions released in 2018~2020 (hell, Debian even ships the most broken version of i2pd I've ever experienced!), which might be a guarantee for stability on servers, but on desktops I think this is more a hassle than anything to the point you need to resort to workarounds like .deb packages or AppImages (which are glorified statically compiled binaries) or PPA repo's (which tend to not work or stop working completely sometimes) to basically achieve something a rolling release distro would do natively, so why not just use a rolling release distro right away then?
寮 (ryo@social.076.moe)'s status on Wednesday, 22-Feb-2023 00:29:59 JST
寮I have to admit, all those people who once used Linux and converted to the BSD's are right, the more I use FreeBSD and OpenBSD, the more I like them, and the more I feel like Linux is just a big mess.
I still love Linux as much as I love OpenBSD and FreeBSD, but the latter 2 really feel like complete operating systems that are well thought out, easy to maintain, and very comfortable to use.
But it's all fine, because both of these are really meant to be full operating systems independent from everybody else, and Linux is really meant to be just a kernel with separate components developed in isolation from each other that put together form an OS.
The point of Linux is to give you the freedom to just replace each component you don't like for one you do like, whereas the BSD's are more meant to be used as intended by the developers, but still provide you the freedom to replace each component if you really want to.
And I will continue to use all 3 of them, though on servers I chose to go full BSD-only, because the only viable Linux distro's in my opinion are Artix and Gentoo, which are both excellent for desktops, but I can't recommend neither on servers at all.
Due to the nature of Linux, it makes perfect sense for distro's being rolling release, not fixed release, but rolling release on its turn only makes sense on desktops, not servers.
寮 (ryo@social.076.moe)'s status on Tuesday, 21-Feb-2023 23:25:00 JST
寮Oh, I just got Byobu to work on OpenBSD (though the modules are kind of broken, like no version reporting, no RAM reporting, and processor being "x1000000000.000GHz"), and getting tmux to be like Byobu was just tiring, so I'm giving up on that part, and instead I'll try to fix Byobu modules.
Yea, I'm already moving all my darknet sites over to my OpenBSD box, though a little bit to a newly installed FreeBSD box (OpenBSD couldn't recognize ethernet for some reason, which is the last thing you want to happen to a server) since both of them only have 4 GiB of RAM, the Devuan box has 8 GiB, and going to re-purpose it for something else later.
But I'm running into an issue now, so maybe you know what's going on?
I configured /etc/httpd.conf and /etc/relayd.conf, both services are started and didn't report any errors, and even the "relayctl show summary" and "relayctl show hosts" commands are showing it's working, but trying to accessing it doesn't work, it's either an endless loading page of death, or a 403 error.
Accessing it using local IP address + port number works perfectly fine, so the RC script and the compiled binaries are clearly working fine.
I can provide config files if that helps, but I'd like to know whether you have any experience with these tools or not.
寮 (ryo@social.076.moe)'s status on Tuesday, 21-Feb-2023 08:43:52 JST
寮Which is yet another reason why I left clearnet, even though they can DDoS darknet (which we've seen with Dread on one hand and an exploit in i2pd 2.45.1 on the other hand), but they can't actually deplatform me unless they physically find my servers.