On Mon, Jan 25, 2021 at 09:32 AM, Joseph Lee wrote:

when you change subject lines, topics are split, and I believe this is also the case when hashtags are introduced by members in the middle of a topic.

No, it doesn't split if a tag is added. Even if you explicitly use the "split" function on the web to add a tag, it doesn't split. It stays the same thread/topic.
 
--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu

Ok thank you. Any luck with finding a fix? 
Are any other Canadian groups having this issue?

Hi Mark,

I'm with the majority:  Users, no, but it could probably work (with caveats) for only the mods and it may require extra work from you now and possibly later; or work (as intended) for just you and that would require less work overall.

But just curious...

>>> I could add the #done hashtag, instead of having to go to the website and editing the topic

- Construct reply as normally, but with #newhashtag also and email in.  (?? OR, instead of the normal address, email the message to (non-published) group+addhashtag@groups.... possibly ??)
- If sender not an admin, treat as now, strip #newhashtag and post, done.
- If an admin, scan the subject hashtags to see if there is a new one (or ones if recursion was used for possibly adding more than one capability)
- If one found, use that and call the code that runs when a hashtag is manually added to a topic by the admin.
- Post the message now, and done.

Is something like this what you had in mind?   It mimics an admin adding a hashtag so effect-wise, nothing changes, not any new disconnects or new side-effects; same thing if currently an admin did the topic hashtag addition by hand then turned around and send the message (with or without the new hashtag), or vice versa.

Cheers,
Christos

Mark, Just verified that it's fixed. Thanks, Joanie

Mark,,
I upgraded my 2,000 member list from Basic, two weeks ago.  Unfortunately I paid for the first year with my credit card on file and then activated
sponsorship, not knowing the level of list support I would receive, I had told my  list this would be done before the 18th.  And after the special notice
went out I started getting a lot of sponsors.  I then realized that I should have activated the sponsor feature a day before the upgrade.  AS it was I received
enough sponsors for two more years of Premium subscription.
   Within an hour of the upgrade I sent out a second notice to the list that they could donate to me using Paypal to reimburse me for the first year Premium fees.
within eight hours Paypal donations had paid for the initial upgrade and I asked Paypal donations to stop. Most donations were between $5 and $25, only two higher.
I got 17 contributions thru Paypal in eight hours and 34 thru the sponsorship function in 48 hours at which I had funds for three years and disabled the sponsorship 
function.  Several subscribers who had pledged earlier to contribute complained that the Paypal donation ended before they learned of the request.

Two lessons learned. 
First the Sponsorship function works effectively, just if you have a Basic list, turn it on BEFORE you upgrade.
Two Even though the Paypal donations were more complicated to make and did not directly add to the funds on hand, they came in faster and in larger amounts.
PAYPAL should be added to the sponsorship funds collection function.

ken clark

Many many of my members are bouncing since Jan 18th. Looks like all the @sympatico and @bell.net ones. The message for the bouncing reason is:
mxmta.owm.bell.net: read tcp4 66.175.222.12:36686->184.150.200.210:25: read: connection reset by peer
or
mxmta.owm.bell.net: read tcp4 66.175.222.12:49712->184.150.200.82:25: read: connection reset by peer
(what does this mean?)
Is this similar to the Gmail issue some weeks ago?
Is it happening to anyone else? We are in Canada (Toronto) if that makes a difference.
Thanks! Nancy

Mark,

Did you do something because a little bit better!
A little bit because for many photos in one folder nothing is coming.
For not many by folder seems ok.
Tested on 700 photos at least  (https://groups.io/g/listeATV/photosearch?q=IMSTP12) = NG.
Also on an other group, 1000 photos,( https://groups.io/g/TekScopes/photosearch?q=img) = OK
For the search on the last group, (https://groups.io/g/TekScopes/photosearch?q=Cabot)
Cabot in the second folder, couldn't not be not find.

Thank you for your help.

Best regards

Alain

https://groups.io/g/advantestinstrument
owner

On Mon, Jan 25, 2021 at 12:25 PM, Mark Fletcher wrote:

Currently, if you change the subject in a reply, to add an additional hashtag, that hashtag is just ignored. What do you all think about changing that, so that replies to topics can add hashtags?

Hashtags are a function of the topic, not a message. Is the intent that adding a hashtag to a subject line in a reply would apply only to that one message (my preference)? Or would that automatically propagate to all the other messages in the topic?

If the former, wouldn't that create a discrepancy between the emailed messages and what appears in the message archive? If the latter, what are the effects on the properties of messages previously posted in that topic (such as reply-to options, moderation, topic duration, and so on)?

To mix a metaphor, I'm having a hard time wrapping my head around this can of worms. Right now it just seems like asking for a slew of unintended, new "features." I have seen people reply to threads that are years old; and I can just see someone deciding to retroactively add a hashtag -- perhaps years from now -- with the wrong Topic Duration, causing large portions of the message archive to disappear.

Regards,
Bruce

Mark,

All of a sudden*** the attached images in the FO catch-up messages

Just to clarify, I did not test it with FO catch-up messages with embedded images, only "real" attachments, but I suspect the same problem will happen with embedded images too, since you're kinda treating them as attachments as far as storage/pointers is concerned.

Seems S3 is not returning the actual file data in time or something, only the filename does.

Cheers,
Christos

Mark,

This should be fixed now. It was a timing issue. We upload the attachments to S3 and then query S3 for a list of attachments. But S3 hadn't finished whatever it needs to do. I've added a delay.

I suspect you may also have to similarly-tweak another part of the code in regards to attachments and S3; I was actually in the middle of writing that bug report when I read this and it clicked.

I take it you are also using calls to S3 to query and retrieve (and embed/attach) the in-line image/attachments when the Follow-Topic catch-up emailer code is invoked. 

All of a sudden*** the attached images in the FO catch-up messages, while correctly named as in the original mailing, are now nothing but a 212 to 214 byte (in my test case) gibberish-contents file. (I can attach/mail them offlist if you think it may help)

Cheers,
Christos

*** or at least I just noticed it while testing for another bug I also just found, in that same FO catch-up mailer area (to be submitted soon)

Just an aside on a completely different issue ... (to raise in GM<F perhaps)

The left column of my pasted table of browser and OS details was black text on white in my sent folder and in my inbox when it came back from GIO ... but in the web interface that left column is displayed white text on white!

Malcolm.

Hmm, the left column of the table went missing en-route to GIO, here it is, with <Ctrl-Shft-V>

On Mon, Jan 25, 2021 at 11:54 AM, Mark Fletcher wrote:

What browser and operating system are you using?

On mine, it's Win7 Home Premium with FF 84.0.2, both 64 bit, everything set to CST.  I thought this problem might have something to do with my ISP, so I took my laptop to town and connected on another service - no help.  I don't use the Feed much, so not a major concern here, just curiosity now.  I've almost decided it may just be one of the joys of living in the boonies. ;>)

Duane

That looks good, unobtrusive, simple, and precise, thanks!

Cheers,
Christos

On Mon, Jan 25, 2021 at 12:36 PM, Mark Fletcher wrote:

This should be fixed now.

Yes it is, much obliged!

Cheers,
Cristos