• Re: Is binkp/d's security model kaputt?

    From Blue White@21:4/134 to Digital Man on Friday, December 31, 2021 19:40:20
    Digital Man wrote to apam <=-

    With Synchronet, I also supported PostLink networking (e.g. RIME) in
    the past and certainly have no love of FTN, but I think it'd be best to know what you're trying to fix before you try to replace it with
    something else. :-) --

    +1



    ... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From apam@21:1/151 to Digital Man on Saturday, January 01, 2022 14:55:29
    I find the topic of a new messsage network technology interesting and
    have been following along here.

    It's interesting, I'm kind of a little bit fickle about the idea, I'm not really sure it's worth pursuing. I mean, from a development point of
    view, making new things for the sake of making new things can be fun, but
    who would use it?

    However, before anything "new" is proposed, I suggest a careful
    examination of what is wrong with the current technology (FTN). I've
    started my own list here:

    Yep, I agree, I read your list, and think it's pretty much spot on.

    To be honest though, I think it's a kind of dead end. It's interesting to
    talk about though I suppose.

    Happy birthday by the way, not sure if it was today or yesterday..
    facebook told me, but I don't know how that works with timezones :)

    Andrew

    --
    |03Andrew Pamment |08(|11apam|08)
    |13Happy|10Land |14v2.0|08!|07


    --- Talisman v0.35-dev (Windows/x64)
    * Origin: The Grinning Cat - telnet://gcat.talismanbbs.com:11823 (21:1/151)
  • From Digital Man@21:1/183 to apam on Friday, December 31, 2021 21:22:51
    Re: Is binkp/d's security model kaputt?
    By: apam to Digital Man on Sat Jan 01 2022 02:55 pm

    I find the topic of a new messsage network technology interesting and have been following along here.

    It's interesting, I'm kind of a little bit fickle about the idea, I'm not really sure it's worth pursuing. I mean, from a development point of
    view, making new things for the sake of making new things can be fun, but who would use it?

    It's always possible that a network could be formed (or switch to) a non-FTN technoloy. And that could then be a new technology. But so far, I haven't found any limitation or issue with QWK that I couldn't address, so that's where I tend to focus my message-networking-innovation. I appreciate your adopting (and testing the interoperability) of some of my QWKnet extensions too.

    However, before anything "new" is proposed, I suggest a careful examination of what is wrong with the current technology (FTN). I've started my own list here:

    Yep, I agree, I read your list, and think it's pretty much spot on.

    To be honest though, I think it's a kind of dead end. It's interesting to talk about though I suppose.

    Yeah, probably a dead end. There's the occasional discussion of the same subject on FidoNet proper (e.g. Future4fido echo), but I don't think it's ever going to amount to much because of the compatiblity issue.

    Happy birthday by the way, not sure if it was today or yesterday..
    facebook told me, but I don't know how that works with timezones :)

    Thanks. It's still the 31st here in California, so still my birthday (the Unix epoch, for this timezone anyway). :-)
    --
    digital man (rob)

    Breaking Bad quote #4:
    Tagging trees is a lot better than chasing monsters. - Hank
    Norco, CA WX: 47.0øF, 90.0% humidity, 0 mph ESE wind, 0.01 inches rain/24hrs --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)
  • From apam@21:1/151 to Digital Man on Saturday, January 01, 2022 15:54:00
    It's always possible that a network could be formed (or switch to) a
    non-FTN technoloy. And that could then be a new technology. But so
    far,

    Yes, it would have to offer something FTN doesn't though I think, even if
    it was technically superior, FTN does work and I suspect unless both
    Synchronet and Mystic supported it natively, very few would be bothered
    to set it up.

    I haven't found any limitation or issue with QWK that I couldn't
    address, so that's where I tend to focus my
    message-networking-innovation. I appreciate your adopting (and testing
    the interoperability) of some of my QWKnet extensions too.

    That's cool, I mainly just wanted messages from talisman to be a bit more seemless for those viewing on synchronet (so people didn't get mad lol)
    but I'm glad it was helpful to test things.

    Thanks. It's still the 31st here in California, so still my birthday
    (the Unix epoch, for this timezone anyway). :-)

    Ah, ok. That's interesting. So facebook must tell me it's peoples
    birthdays in my own timezone not theirs.

    Sorry, I don't mean to be a bit of a downer regarding message nets - I'm
    not sure if it's coming across that way.

    Andrew

    --
    |03Andrew Pamment |08(|11apam|08)
    |13Happy|10Land |14v2.0|08!|07


    --- Talisman v0.35-dev (Windows/x64)
    * Origin: The Grinning Cat - telnet://gcat.talismanbbs.com:11823 (21:1/151)