On 18 Sep 2024 at 07:29p, paulie420 pondered and said...

We'd talked about having an echo for homelab/server/VM discussions, seems like there's a lot of people who could contribute. Would love t see something like that happen.

I'd like an echo like this - but fsxNet is usually slow to add; and thats almost a good thing... we know what we have and new echoes sometimes get some traction for a minute and then are just dead weight.

I'd like it, but wonder if theres enough folks to make it active - we'll see what Avon thinks, but I love that fsxNet is solid and stable.

I'm open to it, won't look at this until I get back from some planned travels. I think I should revisit the current echomail list just to see what may need trimming... but what I have also learned is that it's easy to add but hard to remove an echo once added as some systems keep sending posts to retired echos long after they have been pulled. Guess it all comes down to how the HUB software can handle such things.

With HPT I think we negate it with write level access being set higher than normal node privileges allow for. I think ClrgHouz does the same - Deon?

Anyway I digress. I'm not against an echo that's being requested over many months being created. I'm also never 100% sure if inactivity in some echos is necessarily a bad thing and should ensure an echo is retired. Some stuff if more niche it seems and ebbs and flows in popularity.

I do think having echos with wider topic coverage is better than really niche so support the idea mooted by someone else (sorry can't recall who) that perhaps a modern computing echo vs the retro one may suffice?

Poindexter - ping me again in 2-3 weeks time and we'll circle back to this and look to sort :)

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)

Re: Re: FSX_HOMELAB?
By: Avon to paulie420 on Mon Sep 23 2024 11:15 am

Howdy,

may need trimming... but what I have also learned is that it's easy to add but hard to remove an echo once added as some systems keep sending posts to retired echos long after they have been pulled. Guess it all comes down to how the HUB software can handle such things.

With HPT I think we negate it with write level access being set higher than normal node privileges allow for. I think ClrgHouz does the same - Deon?

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.

If you attempt to write to an area that is read-only (or you dont have permission to write because its an area that is writable by others,eg: "private" echoareas), then clrghouz will send you a netmail telling you that your post was not accepted and why (insufficent access).

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.

(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.)

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 :)


...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

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)

I'm open to it, won't look at this until I get back from some planned travels. I think I should revisit the current echomail list just to see what may need trimming... but what I have also learned is that it's easy to add but hard to remove an echo once added as some systems keep
sending posts to retired echos long after they have been pulled. Guess
it all comes down to how the HUB software can handle such things.

Nice - I'd be willing to help out any way(s) I can; I think the topic would either be in lots of users lives already, or spark learning the topic.

I've created a fairly nice homelab and its really helped me learn lots more about Linux, networking and computing in general.

I vote yes.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

We'd talked about having an echo for homelab/server/VM discussions,
seems like there's a lot of people who could contribute. Would love to
see something like that happen.

I'd like an echo like this - but fsxNet is usually slow to add; and thats almost a good thing... we know what we have and new echoes sometimes get some traction for a minute and then are just dead weight.

I'd like it, but wonder if theres enough folks to make it active - we'll see what Avon thinks, but I love that fsxNet is solid and stable.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

I'd like an echo like this - but fsxNet is usually slow to add; and
thats almost a good thing... we know what we have and new echoes
sometimes get some traction for a minute and then are just dead
weight.

There's been some good conversations around Homelabs recently on fsxnet,
but I wonder if a dedicated echo area is too niche, vs something like
"Modern Computing" (vs Retro) that could capture that topic and more...

|07 .'|08.
|07 ||15o|08| |03J0hnny A1pha
|07 .'|15o|08'. |06gOLD mINE HQ
|07 |.-.|08| |08---------------------
|07 '|14( |12)|08' |05SpaceJunkBBS.com|13:|052323
|07 |12)

--- Talisman v0.54-dev (Linux/x86_64)
* Origin: Space Junk! BBS :: SpaceJunkBBS.com:2323 (21:4/158)