Subj : Webring Reminder To : Ogg From : alterego Date : Mon Jun 01 2020 10:07 am Re: Webring Reminder By: Ogg to All on Sun May 31 2020 01:48 pm a>> IE: Hubs dont sent to hubs, but rather post to the DB and pull from a>> the DB. Og> Wouldn't a system like that keep a DB growing and growing like one big Og> blockchain? Not necessarily, you would still expire/purge messages as configured per echoarea. Og> How would you know when all the old (picked up and received) messages were Og> all collected? I havent worked through this in great detail, but I think I was heading down a path that incoming mail would be queue for collection (a record in a queue table) - so when that system polled I know exactly what is waiting for them. (Which then also enables a stats table of who hasnt collected mail.) %RESCAN would still work as well, resending the last x or days of messages (probably useful for new systems configured). Og> So instead of directories full of individual packets or packet bundles per Og> system, the data was sitting in a database. Right that would be the end goal. For me to completely realise this, I need to change binkd (or write a binkd), that built a mail bundle when a connection came in dynamically. I'm probably going to need help here - I did start, on this, but I didnt want to re-write a zmodem. Og> Speaking of ansitex, can you please disable that shell in my account on Og> your system and reset me to the default? The *nn# commands didn't seem to Og> respond for me. I couldn't get back to the S)etup screen so that I could Og> switch to another shell. Not sure what you meant by didnt respond. I have the "#" and return keys mapped so selecting a page *516# or *516 should work. *90# should have taken you to the familiar Synchronet user configuration page, where you could then re-choose your shell. I've probably broken some functionality, as I fixed or enhanced something else - so I know I have a few things to fix before its ready for prime time. (The main dev is not on my main BBS, but on an instance of SBBS which isnt directly accessible.) Og> Ansitex is not what I thought it was. :( Too much repetative typing for Og> me. What did you think it was? I think its a BBS version of the world wide web. Service providers own a page prefix (like a domain name for the internet), and can host any page in their prefix. Navigating around is by typing a page *nnn...# (like typing an address in your browser), or navigating via menus. Each page can "link" to another page (as defined on the page), using the number keys 0-9. Convention was that "0" would take you "up" to a menu - but it was only convention not a rule. When its working, I'll have "about ansitex" on pages *516#, end user help and system config on a page begining with *9.., and public echomail on *1.. - leaving pages *200... to *899... (in 3 character prefixes) available to anybody who wants to host a (set of) pages. (And if they run Synchonet with my shell, then can author the pages on their system.) Anyway, I'll share when its a little more robust - thanks for taking a look and SEEN-BY: 1/100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 SEEN-BY: 1/117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 133 134 SEEN-BY: 1/135 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 SEEN-BY: 1/153 154 155 156 157 158 159 160 161 163 164 165 166 167 168 169 171 SEEN-BY: 1/172 173 174 175 176 178 180 181 182 183 184 185 186 187 188 189 190 SEEN-BY: 1/191 192 193 194 195 197 198 199 200 201 202 203 204 205 206 207 208 SEEN-BY: 1/209 211 212 214 215 217 218 219 220 222 223 224 225 226 227 228 229 SEEN-BY: 1/230 231 232 233 234 235 236 616 995 2/100 101 106 107 108 111 114 SEEN-BY: 2/115 116 118 128 130 132 137 138 140 141 145 147 150 151 159 160 161 SEEN-BY: 2/162 163 167 1202 3/100 4/100 106 5/100 .