I agree with this statement wholeheartedly and have not stated anything contrary. However, just as the forum administrators have the right to administer their forum the way they want, I have the right to continue to highlight how making secret editing policy changes which were not asked for by the community are not consistent with their stated goals of Freedom and a  Community driven forum - at least as long as the site administrators give me that right.

I think removal of the delete button is a reasonable compromise as long as unlimited time limits for edits were restored. Posters could still remove the contents of their posts via edit leaving an empty post.

Well here we disagree. 24 hours is not enough time for a poster to mark an issue solved nor is it enough time for me, at least to complete my posts and correct all my typos and grammatical errors.

What do you mean by vandalizing? Is a poster, regretting some pejorative comment and deleting the contents of their post considered vandalizing by you? Please be specific.

Agree

Based on the response of the Manjaro community to their administrators losing many of their posts due to no backups and then instituting radical Forum changes, the critical and direct responses to the Devuan Forum administrators instituting secret policy changes should not have been unexpected.

Everyone has an axe to grind. My axe is called Freedom and Openness. Based on your advocacy of post editing time limits and keeping those limits secret, your axe is apparently called something quite different - authoritarianism and secrecy perhaps?

Don't see how this is fundamentally different from Debian making some packages systemd only and not telling users which ones they are to see who would notice. Freedom and Openness are fundamental principles to be adhered to, not experimented with.

1. Return things to the way they were with no time limits on editing and deletion of posts and inform users that they can archive any Devuan Forum threads they deem important at https://web.archive.org/save

   • Adheres to Freedom and Openness Principles

     • Allows the community to determine which threads are important to archive

     • Allows posters the freedom to edit and delete their posts

   • No additional Forum system administration requirements

Your proposal impinges on Freedom and Openness and results in additional Forum System Administration.

If someone in the community feels a thread is valuable, they should submit it to archive.org. This can be done by anyone - not just the post owner and doesn't induce any added forum administrative burden. The stealth change of editing timeouts and the comment about possibly removing this forum has prompted me to submit a variety of Devuan forum threads which I may find useful in the future to archive.org - including this one

https://web.archive.org/web/20200920170 … hp?id=3705

People should be centered enough to not get pissed off at what somebody says. I am amazed at your energy to help people on this forum even though you apparently don't use Devuan as your daily driver. Although I don't always agree with you, I think you are an great asset to this community.

I feel that having a free (as in freedom) and vibrant forum is crucial to the success of a project. For instance, one of the reasons I choose RaspberryPi single board computers instead of more capable boards are due to the RaspberryPi's vibrant community and forums.

I apologize for not understanding the distinction between Delete and Edit. In fact, I didn't realize until just now that there was a Delete button. I thought the person clicked on the Edit button and deleted the post contents leaving an empty post - not clicking the Delete button.

I would remove the Delete button entirely.

This would address your concern about someone deleting a post and deleting an entire thread. So can we just eliminate the Delete button and go back to the previous indefinite editing timeout policy?

Edit: Updated with archive.org suggestion

Thanks. I have now been able to edit my post.

Reasons to allow unlimited time for editing.

• Posted issues take an indeterminate time to solve. By setting an edit time limit, you don't allow posters to change a topic subject to [solved]

• I am a very poor typist and make many typos and grammatical errors which I may not notice until days later when reviewing my posts. And yes, I do like to go back and review my posts and admire them

• I may discover additional  issues that I should have discussed originally in a HOWTO days later or weeks later. Edit timeouts could prevent me from updating the HOWTO

Alternatives to Time Limits

• Quote posts you are replying to. Even if the original poster modifies or deletes a post, the post is still in the quoted reply

• Use rdiff-backup to take daily snapshots of your forum.  rdiff-backup  is like a version control system for files and only stores deltas for text files like CVS. If a post gets deleted, it can be restored with  rdiff-backup. Note that  rdiff-backup  works on many different file systems and platforms including MAC OSX

• Submit a discussion thread URL to archive.org.

Are timeouts set on a per forum basis? I can still edit my post on this forum made over an hour a go (Forum Feedback) but couldn't edit

https://dev1galaxy.org/viewtopic.php?pid=24754#p24754

less than two minutes after I posted it.

Regardless, any timeout changes should be published so as not to catch posters by surprise.

Your steps are incomplete. First, you want to make yourself root by issuing the su command.
The bluetoothctl list command should give you something like the following output.

Controller 5C:F3:70:9B:90:CB BlueZ 5.50 [default]

If you see something like the above, then you are good to go. Issue the command bluetoothctl. While in bluetoothctl, issue the following commands.

• scan on

  • Now put you Bluetooth headphone in pairing mode

  • After a few seconds, you should see something like
    [NEW] Device 50:BC:96:9D:DE:61 MyHeadphoneBrand

  • Copy the Bluetooth MAC address. For this example it is 50:BC:96:9D:DE:61 but your Bluetooth headphone MAC address will be different

• pair xx:xx:xx:xx:xx. Substitute your Bluetooth headphone MAC address that you obtained in the previous step for xx:xx:xx:xx:xx.

• connect xx:xx:xx:xx:xx. Substitute your Bluetooth headphone MAC address that you used in the previous step for xx:xx:xx:xx:xx.

• trust xx:xx:xx:xx:xx. Substitute your Bluetooth headphone MAC address that you used in the previous step for xx:xx:xx:xx:xx.

• scan off

• exit

Now, your Bluetooth headphone will automatically connect to your Devuan box every time you power on your Bluetooth headphone. No need to use any applet.

When I installed Beowulf with LXQt, connman was installed. I was having the same issue as you until I ran apt-get purge connman as root.

Off topic but I once tried f2fs on a micro-SD card mounted on one of my OpenWRT devices  Found it extremely slow, CPU intensive and therefore unusable. Switched back to ext4. Have been running both RaspberryPis and micro-routers out of ext4 formatted SD/micro-SD cards for years without any issues. Note that most smart phones have a lot more horse power than my micro router with a MIPS 260Mhz 32 bit CPU and 32Mb of RAM.

First, thanks for pointing to the ps_mem tool. I was unaware of it. When I use ps_mem on my Devuan Buster netbook with 8 Firefox tabs open, I get

 16.8 MiB +   7.4 MiB =  24.1 MiB       WebExtensions
 27.1 MiB +  18.6 MiB = 145.7 MiB       firefox-esr
129.7 MiB +  67.3 MiB = 197.0 MiB       Web Content (8)

Note that the Firefox memory usage on my Devuan system is less than even the memory usage for Badwolf on your Alpine system. Perhaps its time to switch to Devuan

My test details.

• Dell Vostro A90 netbook running Devuan Buster with LXQt

• Out of the box Firefox with nothing disabled

• Tab Contents

  1. https://dev1galaxy.org/

  2. https://dev1galaxy.org/viewforum.php?id=12

  3. https://dev1galaxy.org/viewforum.php?id=10

  4. https://dev1galaxy.org/viewforum.php?id=2

  5. https://dev1galaxy.org/viewforum.php?id=7

  6. https://dev1galaxy.org/viewforum.php?id=3

  7. https://dev1galaxy.org/viewforum.php?id=5

  8. https://dev1galaxy.org/viewforum.php?id=25

Complete ps_mem output.

# ps_mem 
 Private  +   Shared  =  RAM used       Program

164.0 KiB +  20.5 KiB = 184.5 KiB       anacron
236.0 KiB +  39.5 KiB = 275.5 KiB       rtkit-daemon
256.0 KiB +  26.5 KiB = 282.5 KiB       init
260.0 KiB +  35.5 KiB = 295.5 KiB       cron
412.0 KiB +  35.5 KiB = 447.5 KiB       pcscd
520.0 KiB +  21.5 KiB = 541.5 KiB       ssh-agent
504.0 KiB + 115.0 KiB = 619.0 KiB       dbus-launch (2)
472.0 KiB + 166.5 KiB = 638.5 KiB       xfconfd
524.0 KiB + 147.5 KiB = 671.5 KiB       agent
236.0 KiB + 478.0 KiB = 714.0 KiB       saned (2)
640.0 KiB + 145.5 KiB = 785.5 KiB       gvfs-mtp-volume-monitor
612.0 KiB + 187.5 KiB = 799.5 KiB       at-spi-bus-launcher
456.0 KiB + 400.5 KiB = 856.5 KiB       su
408.0 KiB + 456.0 KiB = 864.0 KiB       avahi-daemon (2)
676.0 KiB + 193.5 KiB = 869.5 KiB       at-spi2-registryd
568.0 KiB + 329.0 KiB = 897.0 KiB       getty (6)
792.0 KiB + 118.5 KiB = 910.5 KiB       gvfs-goa-volume-monitor
908.0 KiB + 143.5 KiB =   1.0 MiB       gvfsd-fuse
852.0 KiB + 213.5 KiB =   1.0 MiB       gvfs-gphoto2-volume-monitor
572.0 KiB + 497.5 KiB =   1.0 MiB       dbus
688.0 KiB + 409.5 KiB =   1.1 MiB       gvfsd
908.0 KiB + 452.5 KiB =   1.3 MiB       gvfs-afc-volume-monitor
  1.2 MiB + 137.5 KiB =   1.4 MiB       xscreensaver
908.0 KiB + 542.5 KiB =   1.4 MiB       gvfsd-trash
  1.6 MiB +  45.5 KiB =   1.7 MiB       elogind-daemon
  1.6 MiB + 112.5 KiB =   1.7 MiB       bluetoothd
  1.7 MiB +  65.5 KiB =   1.8 MiB       rsyslogd
  1.6 MiB + 197.5 KiB =   1.8 MiB       udevd
  1.4 MiB + 512.5 KiB =   1.9 MiB       upowerd
  1.8 MiB + 217.5 KiB =   2.0 MiB       polkitd
  1.5 MiB + 799.5 KiB =   2.3 MiB       gvfs-udisks2-volume-monitor
  2.0 MiB + 421.5 KiB =   2.4 MiB       dhclient
  2.0 MiB + 434.0 KiB =   2.4 MiB       dbus-daemon (4)
  1.6 MiB + 912.0 KiB =   2.5 MiB       lightdm (2)
  1.4 MiB +   1.2 MiB =   2.6 MiB       bash (2)
  2.0 MiB + 713.5 KiB =   2.7 MiB       cups-browsed
  2.5 MiB + 545.5 KiB =   3.0 MiB       cupsd
  3.2 MiB + 501.5 KiB =   3.7 MiB       wpa_supplicant
  3.7 MiB + 358.5 KiB =   4.0 MiB       ModemManager
  2.6 MiB +   1.8 MiB =   4.4 MiB       lxqt-policykit-agent
  2.7 MiB +   1.7 MiB =   4.4 MiB       lxqt-globalkeysd
  2.7 MiB +   1.8 MiB =   4.4 MiB       lxqt-session
  3.9 MiB + 631.5 KiB =   4.5 MiB       udisksd
  2.5 MiB +   2.0 MiB =   4.6 MiB       lxqt-notificationd
  4.3 MiB +   1.7 MiB =   6.0 MiB       nm-tray
  5.5 MiB + 743.5 KiB =   6.2 MiB       NetworkManager
  3.7 MiB +   2.6 MiB =   6.3 MiB       lxqt-powermanagement
  6.2 MiB + 209.5 KiB =   6.4 MiB       colord
  6.6 MiB +   1.1 MiB =   7.7 MiB       xfwm4
  5.6 MiB +   2.8 MiB =   8.4 MiB       lxqt-runner
  6.3 MiB +   4.0 MiB =  10.2 MiB       qterminal
 11.9 MiB + 971.5 KiB =  12.9 MiB       pulseaudio
  9.0 MiB +   4.3 MiB =  13.3 MiB       pcmanfm-qt
 13.8 MiB +   1.1 MiB =  14.9 MiB       applet.py
 14.2 MiB +   5.2 MiB =  19.4 MiB       lxqt-panel
 16.8 MiB +   7.4 MiB =  24.1 MiB       WebExtensions
 20.6 MiB +   6.9 MiB =  27.5 MiB       Xorg
127.1 MiB +  18.6 MiB = 145.7 MiB       firefox-esr
129.7 MiB +  67.3 MiB = 197.0 MiB       Web Content (8)
---------------------------------
                        583.4 MiB
=================================

Probably because no one who complains about it has submitted a patch to fix it.

Tried running the binary and got version `GLIBC_2.28' not found

Didn't investigate further because I only use Chromium for web sites that don't support Firefox and Jitsi. For some reason, I don't know whether it is due to Firefox Javascript or WebRTC implementation, Jitsi is much more stable with Chromium.

One of the many reasons I prefer Firefox is its Reader mode which I believe is only found on one other browser - Safari.

Normal web site rendering

After clicking on the Reader icon next to the URL

Notice that the page is now rendered like a Book Reader and all the cruft is gone.