On 23 Sep 2024 at 10:16a, deon pondered and said...

So like HPT, I built in the idea of read and/or write access to an area. So can you can make some areas read-only and/or write-only.

Yes that's good and what I thought was the case... coolio.

I've also been toying with the idea to have a voting system. It should be fairly easy for me to know if a node is active (messages being posted
from that system), vs a system running on auto-pilot (only receiving messages) - and thus for a voting system, to be able to determine if the majority of active nodes agree to something.

Interesting thought. As a ZC I'd think I'd want to have some way of setting certain parameters around this option if it were implemented.

(I was going to implement a way to vote for a new, or retire an old echoarea - and automatically create it when the majority of active nodes agree to have it. Thought it might be something useful, and I was
curious if, and how, I could make it work.)

perhaps a netmail from the nodelisted sysop much like an areafix command but instead something in the way of a vote etc. ? I think it would likely work OK and could have other outputs like summary of voting, stage of creation/removal reports etc. built around an agreed process.

But, I've taken a break from clrghouz - I'm sorting through a gazillion photos and videos to find duplicates (programmatically) - I'm spending most of my time to find the tech specis of AVI and MOV files, as well as JPG and HEIC pictures, and then suck some relevant data out of them and figure out which ones are dupes :)

this does not sound like a relaxing break to me hahahah :)

What I would request as/when you're up to it for Clrghouz would be to implement an areafix/filefix mechanism for nodes.

Once that's in place I'd like to look at moving say NET 4 over to Clrghouz as a next step :)

If there's a way we can set up some database mirroring that would be interesting to explore also.

I'm thinking down the track could hubs for fsxNet be set up to run Clrghouz and mirror databases so if one system was down then the node info etc. would be available at another HUB for a Z21 system to enable and use? This may be more fraught to do than I first envisage and would need some thinking around process and any risk mitigation against abuse etc. perhaps?

Just pondering aloud.

A way of being to do some limited customization to a ClrgHouz instance would be good (if possible) just so as an instance replied it was clear (asides it's FTN address) what/where it was etc. I'm thinking much like HUBs have their own name/personality etc.

Anyway happy Monday... I'm on a day off and you knee deep in photos today? I send you my condolences :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)