Re: [fossil-users] This mailing list is now deprecated
On Aug 11, 2018, at 12:19 PM, Warren Young wrote: > > The /forum repository on fossil-scm.org currently doesn’t even allow you to > clone the repository I’m misremembering. See https://fossil-scm.org/forum/forumpost/db505ad4af ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] This mailing list is now deprecated
On Aug 11, 2018, at 12:01 PM, Andy Bradford wrote: > > Throwing a rock through an 747's window is one way to solve the problem > of getting a plane to drop in altitude, but that doesn't mean it's the > best way. Why is that a good analogy for what’s been done here? I’d say your analogy is exactly backwards: we’ve got people throwing rocks at our plane to make it drop in altitude, and we can’t prevent them from doing so, so instead we’ve redesigned the plane to make it impervious to thrown rocks. > The problem described on that link is about spammers subscribing to the > mailing lists and then sending automated spam to those who post to the > mailing list. Yes, and that can’t happen with Fossil forums. > I guess this new forum feature was easier to implement, The Fossil forum feature is inherently valuable, so you can’t charge the effort spent on it against the current spam problems. Two of my own public Fossil-based projects will be adopting it soon. With that cost externalized, the question then becomes whether it’s easier to use Fossil’s new forum moderation features or to keep fighting the spammers one-on-one. Since part of that cost is also externalized — i.e. by drh making me a moderator — it seems likely that the new method will mean less overall work for drh. That in turn means we either get more improvements in Fossil and SQLite, or drh gets time to do things he’d rather be doing than fighting spammers. That sounds like a good thing to me. > even if it does make communication less useful. The Fossil forum has been quite busy over the past few days. Most of the discussion is about the forums themselves, rather than general-interest Fossil topics, but that’s normal for a big new feature set. It doesn’t seem that the new method is materially less useful than the old. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] This mailing list is now deprecated
On Aug 11, 2018, at 11:36 AM, Andy Bradford wrote: > > The mailing list has yet to > deliver spam as far as I can tell. I’d have a hard time proving it, since I delete such things from my local archive, and I wouldn’t be surprised if many of the public archives have their own inbound spam filtering, too. But, I’m pretty sure I do remember a few incidents of this. The mailing list admin then has to go in and manually boot the user out, and probably add filtering to prevent that email address from re-joining the list. That probably falls on drh’s shoulders. Certainly there’s no reason in principle this could not happen. As long as the Fossil forum moderators are paying attention, it *can’t* happen with Fossil forums. > I believe what you mean is that your email address that you use on this > mailing list has been harvested by spammers and that they are contacting > you directly. Fossil does not expose the email address of its users. The /forum repository on fossil-scm.org currently doesn’t even allow you to clone the repository, and even if it did, you wouldn’t get a copy of the user table without high-level privileges that won’t be handed out to anyone who isn’t already trusted. > That can be easily thwarted by simply setting your From address to be an > invalid address “Easily”? Either: 1. On every post, you manually edit the “From” address in your MUA to something invalid. Yes, it’s just a drop-down selection in modern MUAs, but it’s an extra step on each and every posting. 2. You reconfigure your mailer to always use the invalid address by default, and then have to remember to fix it on every email reply where you’d actually like to receive a reply. 3. Set up some kind of smart filtering system (procmail, etc.) to do this based on the destination address for each email. All three options fall outside the scope of “easily,” in my book. Maybe you have an easier option? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] This mailing list is now deprecated
Ok, obscured my email, but that cat has been out of the bag for years :( On Sat, Aug 11, 2018 at 2:06 PM, wrote: > Doh! Didn't know you could submit a dummy email. > Even though mail is deprecated, are we still able to change settings? > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/options/fossil-users > > I asked for my password and no reply? > > On Sat, Aug 11, 2018 at 2:01 PM, Andy Bradford hkgenpbcdpglgfggc...@bradfords.org> wrote: > >> Thus said Warren Young on Fri, 10 Aug 2018 08:34:24 -0600: >> >> >http://sqlite.1065341.n5.nabble.com/Problems-with-v3-9-0- >> entry-point-sqlite3-finalize-could-not-be-located-td85005.html#a85069 >> > >> > You only need to read the first post, not the whole thread. >> > >> > Fossil forums prevent that problem. >> >> Throwing a rock through an 747's window is one way to solve the problem >> of getting a plane to drop in altitude, but that doesn't mean it's the >> best way. >> >> The problem described on that link is about spammers subscribing to the >> mailing lists and then sending automated spam to those who post to the >> mailing list. >> >> We've discussed this before on this mailing list and some suggestions >> were made, and I guess this new forum feature was easier to implement, >> even if it does make communication less useful. >> >> Oddly enough, I haven't seen much of the spam that people are >> complaining about lately---maybe that means my spam blocking is getting >> it, or maybe it means the spammers have left? >> >> Andy >> -- >> TAI64 timestamp: 40005b6f2492 >> >> >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] This mailing list is now deprecated
Doh! Didn't know you could submit a dummy email. Even though mail is deprecated, are we still able to change settings? http://lists.fossil-scm.org:8080/cgi-bin/mailman/options/fossil-users I asked for my password and no reply? On Sat, Aug 11, 2018 at 2:01 PM, Andy Bradford < amb-sendok-1536602477.hkgenpbcdpglgfggc...@bradfords.org> wrote: > Thus said Warren Young on Fri, 10 Aug 2018 08:34:24 -0600: > > >http://sqlite.1065341.n5.nabble.com/Problems-with-v3-9- > 0-entry-point-sqlite3-finalize-could-not-be-located-td85005.html#a85069 > > > > You only need to read the first post, not the whole thread. > > > > Fossil forums prevent that problem. > > Throwing a rock through an 747's window is one way to solve the problem > of getting a plane to drop in altitude, but that doesn't mean it's the > best way. > > The problem described on that link is about spammers subscribing to the > mailing lists and then sending automated spam to those who post to the > mailing list. > > We've discussed this before on this mailing list and some suggestions > were made, and I guess this new forum feature was easier to implement, > even if it does make communication less useful. > > Oddly enough, I haven't seen much of the spam that people are > complaining about lately---maybe that means my spam blocking is getting > it, or maybe it means the spammers have left? > > Andy > -- > TAI64 timestamp: 40005b6f2492 > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] This mailing list is now deprecated
Thus said Warren Young on Fri, 10 Aug 2018 08:34:24 -0600: > > http://sqlite.1065341.n5.nabble.com/Problems-with-v3-9-0-entry-point-sqlite3-finalize-could-not-be-located-td85005.html#a85069 > > You only need to read the first post, not the whole thread. > > Fossil forums prevent that problem. Throwing a rock through an 747's window is one way to solve the problem of getting a plane to drop in altitude, but that doesn't mean it's the best way. The problem described on that link is about spammers subscribing to the mailing lists and then sending automated spam to those who post to the mailing list. We've discussed this before on this mailing list and some suggestions were made, and I guess this new forum feature was easier to implement, even if it does make communication less useful. Oddly enough, I haven't seen much of the spam that people are complaining about lately---maybe that means my spam blocking is getting it, or maybe it means the spammers have left? Andy -- TAI64 timestamp: 40005b6f2492 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Test From masquerading
Thus said "Andy Bradford" on 11 Aug 2018 11:41:01 -0600: > This is just a test. Only now at the end do I realize that Fossil Users allowed subscribers to hide their subscriber email address... pity. Andy -- TAI64 timestamp: 40005b6f213b ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Test From masquerading
Hello, This is just a test. Andy -- TAI64 timestamp: 40005b6f1fd2 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] This mailing list is now deprecated
Thus said sky5w...@gmail.com on Fri, 10 Aug 2018 13:35:15 -0400: > Whoa, I still receive spam from this mail list. :( Correction: You received spam from spammers. The mailing list has yet to deliver spam as far as I can tell. I believe what you mean is that your email address that you use on this mailing list has been harvested by spammers and that they are contacting you directly. That can be easily thwarted by simply setting your From address to be an invalid address, much like Will Parsons does: From: Will Parsons To: fossil-users@lists.fossil-scm.org Date: Wed, 8 Aug 2018 19:49:27 -0400 (17:49 MDT) Subject: Re: [fossil-users] This mailing list is now deprecated I wasn't aware that fossil-users actually allowed using a different From header than is in the Envelope From or I would have been doing this ages ago. Andy -- TAI64 timestamp: 40005b6f1ea9 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Why no EXE+DLL like SQLite?
On Aug 10, 2018, at 4:05 PM, Ron W wrote: > > I recall some discussion about adding fsuser support to Fossil Yes, it was checked in years ago. See src/fusefs.c. Getting FUSE working on Windows is reportedly difficult, however: https://superuser.com/q/179436/14927 > so this could be done. Fossil-via-FUSE sounds pretty risky to me. What happens if the host application says “File > Save” but there’s a merge conflict? Does the app give an error dialog like “File I/O error”? Will the user understand what that means and why it’s happening? Does the user then manually do a “fossil up” and then save their copy over the top, effectively reverting the other user’s work? At some point, you can’t insulate the users from having to know what version control is all about. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
