[Hotstorage-sc] [EXTERN] Input regarding AI generated submissions to HS '26

[Joo-young Hwang]

Hi All,

Although the HotStorage CFP does not include any specific comments on the
use of AI, I believe it would be reasonable to handle this case in
accordance with the ACM Publication Policy. Many good suggestions have
already been made, so I would like to add my thoughts on the following
three points.

   1.

   *Use of AI detectors*

According to the ACM policy, authors are not required to disclose the use
of AI tools merely to assist with writing. However, when AI tools are used
in conducting the research, their use must be described in the paper.

Therefore, when a paper does not disclose any such use but there are
substantive reasons to suspect that AI was used in conducting the research,
further investigation may be necessary. Due to false-positive problems,
detector outputs should be followed by manual examination by the PC chairs
and/or reviewers. Desk rejection should be considered only when this manual
review identifies concrete evidence of an undisclosed or problematic use of
AI that substantially affects the research or its conclusions.

   2.

   *Hallucinated references*

If fabricated, nonexistent, or materially inaccurate references play a
significant role in supporting the paper’s main claims, I believe desk
rejection would be appropriate. Minor citation errors may be handled
differently, but references that are essential to the technical argument
and cannot be verified raise a clear content-integrity concern.

   3.

   *Limiting the number of submissions*

It is not obvious to me what an appropriate submission limit would be. In
some respects, receiving multiple submissions from the same authors may
make problematic patterns easier to identify. For example, the chairs and
reviewers may be able to compare the submissions and detect substantial
similarities in structure, concepts, terminology, technical claims, or
flaws. However, similarities among papers could not be treated as proof of
AI use. They may instead provide a reason for closer manual examination. If
that examination identifies a material violation, desk rejection may then
be appropriate.

In all three cases above, before making a desk-rejection decision, I
believe the authors should be given a short period—perhaps a few days—to
provide an explanation or supporting evidence.

In addition, as others mentioned, we should have a more detailed discussion
about what scope of AI use should be permitted during the research
lifecycle.


best,

Joo-young

2026년 7월 16일 (목) 오전 5:19, Xiaosong Ma via Hotstorage-sc <
hotstorage-sc at fsl.cs.sunysb.edu>님이 작성:

> I agree with many of the points raised in the two threads of discussion on
> the topic.
>
> While having an “AI-mostly” track sounds interesting, the major challenge
> perhaps is to decide what makes a paper “AI-mostly”. We perhaps couldn’t
> rely on the authors’ self-declaration.
>
> Given the short form of HotStorage papers and focus on presenting
> preliminary ideas, would it be OK to assume that all papers are to some
> extent “AI-assisted” and have a round of preliminary (AI-assisted too)
> review to desk-reject papers that are clearly low-quality?
>
> Xiaosong
>
>
> *Xiaosong Ma  *
> Department Chair and Professor of Computer Science
> Computing and Mathematical Sciences Division
> *P* +971 2 811 3031  *W*.https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.mbzuai.ac.ae&c=E,1,oa0xFRDCvakGhMfx3grR8h6Bzo0zqxGY9c8p3RO45OIBKscMVx2cJ_Y-PMPF83Fo9YWDLh7Rfcl15Y4zJF9y7zf4XnaN-50ILCk7odsKvcyTkVk,&typo=1
> <https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.mbzuai.ac.ae%2f&c=E,1,zrBxIYYpMSUPz6HBw22K52qp3iH5GEa2Zh_6v6DGCbr8xGBi85Sd2CAP5SJ8zXD1WFxfy0JB2F3e-yobF2gThWRPG90FIpC2JMpNFTuLIC0,&typo=1>
> [image: mbzuai logo.png]        <https://www.instagram.com/mbzuai>
> <https://www.facebook.com/MBZUAI>   <https://www.youtube.com/c/mbzuai>
> <https://www.linkedin.com/school/mbzuai/>   <https://twitter.com/mbzuai>
> [image: Signature Banner.jpg]
> *From: *Hotstorage-sc <hotstorage-sc-bounces at fsl.cs.sunysb.edu> on behalf
> of Marcos K. Aguilera via Hotstorage-sc <hotstorage-sc at fsl.cs.sunysb.edu>
> *Date: *Wednesday, 15 July 2026 at 11:32 PM
> *To: *André Brinkmann <andre.brinkmann at uni-saarland.de>
> *Cc: *hotstorage-sc at hotstorage.org <hotstorage-sc at hotstorage.org>
> *Subject: *Re: [Hotstorage-sc] [EXTERN] Input regarding AI generated
> submissions to HS '26
>
> This Message Is From an Untrusted Sender
> You have not previously corresponded with this sender.
>
> I believe AI-mostly-generated papers have a role (e.g., OpenAI recently
> solved an Erdos conjecture) but they need to be treated separately, and we
> need to get authors to cooperate. Here's a perhaps crazy proposal.
> Conferences should create an AI-mostly track, limit the number of
> acceptances of such papers (say, 20% of all accepted papers), ask authors
> to mark their papers as AI mostly, use AI to assist in the review of such
> papers, and ensure the proceedings show the paper as mostly AI (e.g., must
> add "(AI paper)" to the title).
>
>
>
> On Wed, Jul 15, 2026 at 11:41 AM André Brinkmann via Hotstorage-sc <
> hotstorage-sc at fsl.cs.sunysb.edu> wrote:
>
> Hi Vasily,
>
> regarding your point 2), you raise a very important point, and I think we
> have all asked ourselves this question. After reviewing far too many
> AI-generated papers this year, my own answer is no. I do not believe such
> papers benefit a conference, because in many cases they have been written
> without being properly thought through. The main value of a conference,
> discussing with the authors and gaining insights beyond what the paper
> offers, is then most likely lost.
>
> The difficulty, of course, is that distinguishing AI-generated content
> from genuine research has become nearly impossible. So I cannot offer a
> real answer. What I can say is that when one set of authors submits ten
> papers including similar techniques, I am rather pessimistic that they are
> really interested in research, and I doubt I would get much out of a
> discussion with them.
>
> I look forward to discussing this with many of you in Prague, and I hope
> you have more optimistic answers than I do.
>
> Best regards,
>
> André
>
>
> On 15. Jul 2026, at 18:53, Vasily Tarasov <vtarasov at us.ibm.com> wrote:
>
> Lots of reasonable suggestions in the replies.
>
>
>    1. Do the 10 papers have evaluation section? Do the reviewers/chairs
>    think that the evaluation sections – i.e., experimental results – were
>    synthesized w/ AI (no actual experiments were run)?
>
>
>
>    2. One important question, IMHO, is how we view the following case. A
>    paper was *largely* generated with AI (far beyond polishing the text or
>    writing some sub sections). The system prototype was actually built (w/ AI
>    or not) and experiments were run for evaluation (AI took those results in
>    and generated eval section).  The authors did the due diligence reviewing
>    and revising the paper before submission. The paper turned out to satisfy
>    all requirements of a solid HotStorage paper (novel, clear, topic
>    appropriate, evaluation shows strong impact, etc.). Are we fine with
>    accepting such paper?
>    I think the answer is yes. (Don’t know if we want to add AI as
>    co-author – that’s what many code commits have nowadays 😉)
>
>
>
> Best,
>
> *Vasily Tarasov*
> Manager, Principal Research Scientist
> *vtarasov at us.ibm.com* <vtarasov at us.ibm.com>
> *IBM Data Platform / GPU*
>
> *From:* Hotstorage-sc <*hotstorage-sc-bounces at fsl.cs.sunysb.edu*
> <hotstorage-sc-bounces at fsl.cs.sunysb.edu>> *On Behalf Of *Sudarsun Kannan
> via Hotstorage-sc
> *Sent:* Wednesday, July 15, 2026 8:06 AM
> *To:* Gala Yadgar <*gala at cs.technion.ac.il* <gala at cs.technion.ac.il>>;
> Ali Anwar <*aanwar at umn.edu* <aanwar at umn.edu>>
> *Cc:* Andre Brinkmann <*andre.brinkmann at uni-saarland.de*
> <andre.brinkmann at uni-saarland.de>>; *hotstorage-sc at hotstorage.org*
> <hotstorage-sc at hotstorage.org>
> *Subject:* [EXTERNAL] Re: [Hotstorage-sc] Input regarding AI generated
> submissions to HS '26
>
> Hi all, I agree on previous comments and having some bounds on the number
> of papers per author, and maybe this could be mentioned in the future CFPs.
> Besides higher-level policies, some thoughts: Given that there is no clear
> consensus across
> Hi all,
> I agree on previous comments and having some bounds on the number of
> papers per author, and maybe this could be mentioned in the future CFPs.
> Besides higher-level policies, some thoughts:
> Given that there is no clear consensus across most of the conferences on
> what form of AI use is acceptable or not, we could come up with more
> precise description (and examples) for HS paper during one of the SC
> meetings.
> Regarding deciding on the 10 papers, unless all the 10 papers are solving
> the same problem or proposing similar design, a few questions we could ask
> are whether each of the submissions (1) advances storage research and
> systems research in general, (2) solves or proposes to solve a challenging
> and an important problem, and (3) helps realize the goals of the "hot"
> storage workshop and only accept papers that meet the bar.
>
> Best,
> Suda (Sudarsun)
> Associate Professor
> Rutgers CS
> *https://people.cs.rutgers.edu/~sk2113/*
> <https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2furldefense.proofpoint.com%2fv2%2furl%3fu%3dhttps%2d3A%5f%5fpeople.cs.rutgers.edu%5f%2d7Esk2113%5f%26d%3dDwMGaQ%26c%3dBSDicqBQBDjDI9RkVyTcHQ%26r%3d9ACgIpHPMvCLl2qNt6CDPIeSyoMUMdgz6SufhRu4R5Q%26m%3dAHwDRsTwKDFwAObY6Uqg2wkG6I0leKz%5f3bZz%5fWvOFVapMZ6M47UsrfQFbszh7r9Z%26s%3dzx0H4MJiF1bTyH5B3KpFK%5f2vWmlQnm0zkFAEeAhTd1w%26e%3d&umid=11d28bbb-0dec-4015-b657-6fd5086794f4&rct=1784143954&auth=2558bcdb84e02b0c27cd7aa4822a24989cb4e596-7be483486ba17a3c5c46e62ec21ebd0580a9d867>
> ------------------------------
> *From:* Hotstorage-sc <*hotstorage-sc-bounces at fsl.cs.sunysb.edu*
> <hotstorage-sc-bounces at fsl.cs.sunysb.edu>> on behalf of Ali Anwar via
> Hotstorage-sc <*hotstorage-sc at fsl.cs.sunysb.edu*
> <hotstorage-sc at fsl.cs.sunysb.edu>>
> *Sent:* Wednesday, July 15, 2026 10:20 AM
> *To:* Gala Yadgar <*gala at cs.technion.ac.il* <gala at cs.technion.ac.il>>
> *Cc:* Andre Brinkmann <*andre.brinkmann at uni-saarland.de*
> <andre.brinkmann at uni-saarland.de>>; *hotstorage-sc at hotstorage.org*
> <hotstorage-sc at hotstorage.org> <*hotstorage-sc at hotstorage.org*
> <hotstorage-sc at hotstorage.org>>
> *Subject:* Re: [Hotstorage-sc] Input regarding AI generated submissions
> to HS '26
>
>
> I agree that if the submissions are substantially similar in content, we
> should reject all of them, whether on the basis of self-plagiarism or
> another appropriate policy ground.
>
> However, if the submissions are meaningfully different, then the approach
> Erez suggested earlier makes more sense. Even in that case, I support
> limiting the number of submissions per author. OSDI has also introduced a
> submission limit this year. Such a rule would discourage authors from
> attempting this type of exploit in the future.
>
> Reviewing workloads have increased significantly, and we should not ask
> reviewers to evaluate multiple AI-generated papers that differ only in
> minor ways. More importantly, we should develop a systematic method for
> identifying related cohorts of submissions, either with support from the
> submission platform or through another tool. This would allow us to apply
> the same policy consistently and fairly to everyone.
>
> Regards,
> -Ali
>
> On Wed, Jul 15, 2026 at 7:03 AM Gala Yadgar via Hotstorage-sc <
> *hotstorage-sc at fsl.cs.sunysb.edu* <hotstorage-sc at fsl.cs.sunysb.edu>>
> wrote:
>
> I share Anrdé's sentiment.
>
> Submitting the same (or very similar) work as 10 different papers (or even
> two, for that matter) is abusing the system. AI makes it easier but is not
> necessarily the major problem in this case. I hope the PC can find an
> assertive way to send the message that this is unacceptable.
>
> If the scenario is as extreme as I understand it, then I think that
> accepting even one of those papers is problematic, because it would mean
> that the trick worked and that there was no penalty for the abuse.
>
> Best,
> Gala
>
> *From:* =?utf-8?q?Brinkmann=2C_Prof=2E_Dr=2E_Andr=C3=A9_via_Hotstorage-sc?=
> <*hotstorage-sc at fsl.cs.sunysb.edu* <hotstorage-sc at fsl.cs.sunysb.edu>>
> *Sent:* Wednesday, July 15, 2026 13:35
> *To:* Angela Demke Brown <*demke at cs.toronto.edu* <demke at cs.toronto.edu>>
> *Cc:* Andre Brinkmann <*andre.brinkmann at uni-saarland.de*
> <andre.brinkmann at uni-saarland.de>>; *hotstorage-sc at hotstorage.org*
> <hotstorage-sc at hotstorage.org>
> *Subject:* Re: [Hotstorage-sc] Input regarding AI generated submissions
> to HS '26
>
> Sie erhalten nicht häufig E-Mails von *hotstorage-sc at fsl.cs.sunysb.edu*
> <hotstorage-sc at fsl.cs.sunysb.edu>. *Erfahren Sie, warum dies wichtig ist*
> <https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2furldefense.proofpoint.com%2fv2%2furl%3fu%3dhttps%2d3A%5f%5faka.ms%5fLearnAboutSenderIdentification%26d%3dDwMGaQ%26c%3dBSDicqBQBDjDI9RkVyTcHQ%26r%3d9ACgIpHPMvCLl2qNt6CDPIeSyoMUMdgz6SufhRu4R5Q%26m%3dAHwDRsTwKDFwAObY6Uqg2wkG6I0leKz%5f3bZz%5fWvOFVapMZ6M47UsrfQFbszh7r9Z%26s%3d6mcR0iqoiPSb7tHog7ji7%5f80GIX%5fzeWGDtMVN%2dgKQIU%26e%3d&umid=11d28bbb-0dec-4015-b657-6fd5086794f4&rct=1784143954&auth=2558bcdb84e02b0c27cd7aa4822a24989cb4e596-a23cae65449079fe13c5f0a8a06cf0e84f00c1b8>
> Dear All,
>
> Reviewing is not much fun at the moment, and I assume that nearly any
> submitted paper uses some kind of AI support ... The difference here, from
> my perspective, is that the authors have submitted so many papers with
> similar techniques. They are therefore speculating that, statistically,
> some of these papers will be accepted, which is an unfair advantage
> compared to other authors. I would therefore desk reject for
> "self-plagiarism".
>
> Best regards,
>
> André
>
>
>
> On 15. Jul 2026, at 03:43, Angela Demke Brown via Hotstorage-sc <
> *hotstorage-sc at fsl.cs.sunysb.edu* <hotstorage-sc at fsl.cs.sunysb.edu>>
> wrote:
>
> We ran into something similar with SOSP. In our case it was 9 papers from
> one company/pair of authors and 6 papers from another company and pair of
> authors, which on investigation appeared to be the same authors using
> different first names.
>
> Given the lack of policy in the CFP on generative AI use, and the ACM
> authorship policies, we felt we couldn't do anything other than (a) ask the
> authors to explain their use of AI and (b) let the papers be rejected on
> the basis of their quality. The authors in our case claimed AI use only to
> polish their writing, which is generally allowed.
>
> I have no solutions to offer to HotStorage, unfortunately.
>
> All the best,
> Angela
>
> On Tue, Jul 14, 2026, 7:50 p.m. Ashvin Goel via Hotstorage-sc <
> *hotstorage-sc at fsl.cs.sunysb.edu* <hotstorage-sc at fsl.cs.sunysb.edu>>
> wrote:
>
> The 10 papers were submitted by the same set of authors.
>
> Ashvin
>
> On Tue, Jul 14, 2026 at 8:28 PM Erez Zadok <*ezk at fsl.cs.sunysb.edu*
> <ezk at fsl.cs.sunysb.edu>> wrote:
>
> That is a hotly debated topic nowadays among ACM EiCs and multiple
> conferences.  We just had heated debates about this on the ACM ATC SC too.
> Different people are trying different things to varying degrees of success,
> from requiring disclosure by authors, to automated tools, etc.  No perfect
> solutions.  ACM seems to have given up on getting an AI-detection tools but
> are looking into cite-checking tools.
>
> ACM recently loosened their AI policy: they no longer prohibit it outright
> but ask authors to disclose AI use if wanted, then ask the reviewers to
> decide what, if, and how much AI use is ok or not ok.  IOW, ACM now shifted
> the burden onto reviewers.  Some are ok with this change, others less so.
>
> One problem with any AI detectors is that actual text can easily be
> flagged as AI-generated even if the authors use AI to spell check, polish
> the text, or ask AI to shrink the text size: these are considered valid
> uses of AI that shouldn’t result in rejection.
>
> That said, the easiest way to catch bad AI use is via citation checks.  At
> TOS, we now validate each citation of a submission before sending it off to
> be reviewed.  Even with search tools, that’s more work but we have no
> choice: recently we caught several papers with bad/hallucinated cites deep
> into the reviewing process (thus wasting reviewers’ precious time).  Any
> paper with obviously bad/hallucinated cites gets desk-rejected, but we also
> email the authors to see if they can explain themselves first.
>
> So my suggestions are:
>
> 1. Papers with obviously large portions of AI text should be rejected with
> minimal reviews.  If authors didn’t spend any significant effort to develop
> the paper, then our reviewers shouldn’t waste their time either.  “You get
> what you paid for” principle.
>
> 2. Papers with too many hallucinated cites should be rejected right away
> without review.  1-2 cites max may be considered a silly mistake that
> students sometimes make (I’d ask the authors), but any more should be
> rejected.
>
> 3. I don’t think we should limit the number of submissions per author.
> While rare, it’s possible to see 2-3 papers submitted by a subset of the
> same authors.  Now, when you say “a set of authors had submitted 10
> papers,” *how many* are in the set?!  Is it the same exact authors who
> submitted 10 separate papers?
>
> Thanks,
> Erez.
>
> > On Jul 14, 2026, at 2:18 PM, Ashvin Goel via Hotstorage-sc <
> *hotstorage-sc at fsl.cs.sunysb.edu* <hotstorage-sc at fsl.cs.sunysb.edu>>
> wrote:
> >
> > Hi all,
> >
> > The HS '26 PC chairs (Young-ri and Bryan) are asking for input from us
> regarding a set of paper submissions that have likely been AI generated.
> Two reviewers expressed concerns to the chairs. They found several papers
> with similar concepts applied to different areas, following a similar
> structure, language (including hard to understand or strange words) and
> flaws. The chairs found that a set of authors had submitted 10 papers (13%
> of the 79 submissions). The reviewers are currently leaning negative on
> several of these papers, pointing out that the papers are difficult to
> understand, describe concepts vaguely, and use unfamiliar language. The
> positive-leaning papers will be discussed at the PC meeting.
> >
> > The chairs are looking for input about the best course of action to
> handle this case of suspected AI-generated papers. On the one hand, ACM
> allows the use of undisclosed AI. Thus, rejections should be grounded on
> the paper's technical contribution and novelty, rather than AI use, which
> is hard to detect accurately using current AI detection tools. On the other
> hand, such AI-generated papers will overwhelm reviewers in the future.
> >
> > Let me know if you have any specific suggestions regarding handling the
> current case with the 10 submissions. More broadly, we should discuss if HS
> should put in place any policies for AI generated papers. Here are some
> examples I have seen:
> >
> > 1. Using multiple detectors and letting reviewers know so they can decide
> > 2. Desk rejecting papers with hallucinated references
> > 3. Limiting number of submissions by authors
> >
> > Thanks
> > Ashvin
> > --
> > Hotstorage-sc mailing list
> > *Hotstorage-sc at fsl.cs.sunysb.edu* <Hotstorage-sc at fsl.cs.sunysb.edu>
> > *https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.fsl.cs.sunysb.edu%2fmailman%2flistinfo%2fhotstorage-sc%2a&c=E,1,3IYqvU7VEzthNJpxyAURg8dHqSbres1z1jzJMJROB7scTgjBBur1sclf2GMNzm5E4TulI1qQOsNlq5Hfnzre73LVQAEXdiyyOB3bJban1RhN&typo=1
> <https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2furldefense.proofpoint.com%2fv2%2furl%3fu%3dhttps%2d3A%5f%5flinkprotect.cudasvc.com%5furl%2d3Fa%2d3Dhttps%2d253a%2d252f%2d252flists.fsl.cs.sunysb.edu%2d252fmailman%2d252flistinfo%2d252fhotstorage%2d2Dsc%2d26c%2d3DE%2d2C1%2d2Cz8DobtW1BkooL5a0UNH0Ce6rw30e6DGipeCv9AQMN7tsuC2XM5d49YemzXRXUt7%2d5FW7l9VJuVm9ocASktZsTHaM%2d2DUuclKlYotowsgGzwhcHIBze7dcUCBCIUP4A%2d2C%2d2C%2d26typo%2d3D1%26d%3dDwMGaQ%26c%3dBSDicqBQBDjDI9RkVyTcHQ%26r%3d9ACgIpHPMvCLl2qNt6CDPIeSyoMUMdgz6SufhRu4R5Q%26m%3dAHwDRsTwKDFwAObY6Uqg2wkG6I0leKz%5f3bZz%5fWvOFVapMZ6M47UsrfQFbszh7r9Z%26s%3dv1%5fT5qi9LSTog%2dlceFHvhlJ1Cn7vfehFxBWubuwFS2M%26e%3d&umid=11d28bbb-0dec-4015-b657-6fd5086794f4&rct=1784143954&auth=2558bcdb84e02b0c27cd7aa4822a24989cb4e596-47ccd26979430397e42bc0f5ff7dffce274ad67e>
>
> --
> Hotstorage-sc mailing list
> *Hotstorage-sc at fsl.cs.sunysb.edu* <Hotstorage-sc at fsl.cs.sunysb.edu>
> *https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.fsl.cs.sunysb.edu%2fmailman%2flistinfo%2fhotstorage-sc%2a&c=E,1,2qlszCEI_HRy1Iyv9yNWEIrI8whcRS90u_Jzg06QMqyEhofhXslpUZX50qNtEJbuOxVNij3dwybXh5HeBOffmHiGRN5linZ9W_XpBzbQXZz-h_0e&typo=1
> <https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2furldefense.proofpoint.com%2fv2%2furl%3fu%3dhttps%2d3A%5f%5flinkprotect.cudasvc.com%5furl%2d3Fa%2d3Dhttps%2d253a%2d252f%2d252flists.fsl.cs.sunysb.edu%2d252fmailman%2d252flistinfo%2d252fhotstorage%2d2Dsc%2d26c%2d3DE%2d2C1%2d2COKoPXtu%2d2DmnaObnaEK68Trt0G3VMUZwc93VDvfavS9cNBfYCht%2d2D8zuM58VHWnfOJdnjBoRMsQLMz7gLHKV0QQvDEiNH59%2d5F5rsUcssAKf8bcEuFzI6No1n%2d26typo%2d3D1%26d%3dDwMGaQ%26c%3dBSDicqBQBDjDI9RkVyTcHQ%26r%3d9ACgIpHPMvCLl2qNt6CDPIeSyoMUMdgz6SufhRu4R5Q%26m%3dAHwDRsTwKDFwAObY6Uqg2wkG6I0leKz%5f3bZz%5fWvOFVapMZ6M47UsrfQFbszh7r9Z%26s%3dA6aZLUaVR5n3uRkHVy4jfrgS2SFBSbxp2bS3hIsCYW0%26e%3d&umid=11d28bbb-0dec-4015-b657-6fd5086794f4&rct=1784143954&auth=2558bcdb84e02b0c27cd7aa4822a24989cb4e596-1463451923202b3b04ea661fe488fa36eb253174>
>
> --
> Hotstorage-sc mailing list
> *Hotstorage-sc at fsl.cs.sunysb.edu* <Hotstorage-sc at fsl.cs.sunysb.edu>
> *https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.fsl.cs.sunysb.edu%2fmailman%2flistinfo%2fhotstorage-sc%2a&c=E,1,3fDNXgHe3WLIlA5dzAdWoHD5hN0g1WAG-V7dWEZdTLML7iIdlJbzT2wwqmQf-w7k1Oy_BWc2mDrzNNfM1phAVzOQq52sRjYQRmEKYgfUwamJPQ,,&typo=1
> <https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2furldefense.proofpoint.com%2fv2%2furl%3fu%3dhttps%2d3A%5f%5flinkprotect.cudasvc.com%5furl%2d3Fa%2d3Dhttps%2d253a%2d252f%2d252flists.fsl.cs.sunysb.edu%2d252fmailman%2d252flistinfo%2d252fhotstorage%2d2Dsc%2d26c%2d3DE%2d2C1%2d2CfjHwe0z08xZ16GBMBIKts4hz1%2d2DZBF7QclPPfzoixqTQGRTfupgTjbL3oaaKv3CLRphWVOHG6YJ5SDJeKfPRpXv9aNruWrCvS1dYGLLliuMi3tA5q2S4qKmRA7e4h%2d26typo%2d3D1%2d26ancr%2d5Fadd%2d3D1%26d%3dDwMGaQ%26c%3dBSDicqBQBDjDI9RkVyTcHQ%26r%3d9ACgIpHPMvCLl2qNt6CDPIeSyoMUMdgz6SufhRu4R5Q%26m%3dAHwDRsTwKDFwAObY6Uqg2wkG6I0leKz%5f3bZz%5fWvOFVapMZ6M47UsrfQFbszh7r9Z%26s%3drB%2dcmLors8Wvyp1IqopLSfSjMIRRdVggadxDAXaStAk%26e%3d&umid=11d28bbb-0dec-4015-b657-6fd5086794f4&rct=1784143954&auth=2558bcdb84e02b0c27cd7aa4822a24989cb4e596-7ea6caf751cd1c98b34dfc3534f7fb501e089afc>
>
>
> --
> Hotstorage-sc mailing list
> *Hotstorage-sc at fsl.cs.sunysb.edu* <Hotstorage-sc at fsl.cs.sunysb.edu>
> *https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.fsl.cs.sunysb.edu%2fmailman%2flistinfo%2fhotstorage-sc%2a&c=E,1,ZLeTSQRxf1sjjRQlJ_ghKsQpjiTDULItb6mpnXT_GX38Lg7lFynQNwC7UHN9LvwmS350kC9wG5Iwefl4CElcSiOv-U2QxH-Sr4ct_sw4iFCGFJI,&typo=1
> <https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2furldefense.proofpoint.com%2fv2%2furl%3fu%3dhttps%2d3A%5f%5flinkprotect.cudasvc.com%5furl%2d3Fa%2d3Dhttps%2d253a%2d252f%2d252flists.fsl.cs.sunysb.edu%2d252fmailman%2d252flistinfo%2d252fhotstorage%2d2Dsc%2d26c%2d3DE%2d2C1%2d2ClAPnJvqR92iGPUK2fa%2d2Dz1YSNms9ejuxSDj1NQatyMtzm49i637UUy8cXEXSWMWQcl8IRsKy8LtNl98Ctl3z9yyezQDklLvem2RXGTViW%2d2DJb8%2d26typo%2d3D1%26d%3dDwMGaQ%26c%3dBSDicqBQBDjDI9RkVyTcHQ%26r%3d9ACgIpHPMvCLl2qNt6CDPIeSyoMUMdgz6SufhRu4R5Q%26m%3dAHwDRsTwKDFwAObY6Uqg2wkG6I0leKz%5f3bZz%5fWvOFVapMZ6M47UsrfQFbszh7r9Z%26s%3dr6aQzuocX1srj%5fEP7NqEUxq7wRGJ4ec%2dIXmnEUbJYvU%26e%3d&umid=11d28bbb-0dec-4015-b657-6fd5086794f4&rct=1784143954&auth=2558bcdb84e02b0c27cd7aa4822a24989cb4e596-4633f6128182f90dc9a7a1ab8dfd91d2d6eebd18>
>
>
> --
> Hotstorage-sc mailing list
> Hotstorage-sc at fsl.cs.sunysb.edu
> https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.fsl.cs.sunysb.edu%2fmailman%2flistinfo%2fhotstorage-sc&c=E,1,1787_q2zwTuiBkwLfaBtIci8Y4dDVcqj3V3zHd_-Gj48ldQgUs_9ce6ae6-jsTNOPDcX4fIjd7A3ABaKQ_LA_BFDr2y_OUdALGqMDRyj4q0,&typo=1
> <https://urldefense.com/v3/__https://linkprotect.cudasvc.com/url?a=https*3a*2f*2flists.fsl.cs.sunysb.edu*2fmailman*2flistinfo*2fhotstorage-sc&c=E,1,bmcf8Yy7rAj8v4Xq0Vpw6xAPQBgwQjh2ytS-odTzSUkbUvjzJkZ3UcL0wm6DjzDYm_iW7QAnbTlwP2ucgfQ5XEFh8w6KvW31TrD_oAnpgjPcrMre&typo=1__;JSUlJSUl!!J2_iJ0WgAoU!dejMbP8KTptiwEVRreld4WTo-dIbe6-2lJ9fP_ZER5YWGYmHgJAo7YWxNfa-TKRXqFJ8Ukn11tIUogqiFissU9sQJb71i8fq0rwcCfo$>
>
> --
> Hotstorage-sc mailing list
> Hotstorage-sc at fsl.cs.sunysb.edu
> https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.fsl.cs.sunysb.edu%2fmailman%2flistinfo%2fhotstorage-sc&c=E,1,Pjj_5CTM5LMKDcPsKoLgSjH6rOhWNIsw9s0vS145qc0b32w6dS3CCZnamJbXj5ZHjQlVPrqKGunsV7WlB2omKx4HRnYLCm88OmhmbhHj25zSYsNJ&typo=1
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_instagram3_6d55ee4b-bfab-47b6-a7ec-bdb847e33ccf.png
Type: image/png
Size: 3262 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_logoforsignature_e73ff074-cb33-41b7-8a0e-df9d830d55df.png
Type: image/png
Size: 14963 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_facebook2_8163aee3-593b-481f-aecf-3f004bf0d8bf.png
Type: image/png
Size: 2264 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_youtube2_cf00ac2a-ec71-4a64-b7a7-1f8db2a4ea75.png
Type: image/png
Size: 2490 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_linkedin2_a5930c15-804c-42e8-a409-8fc8bb6b42dd.png
Type: image/png
Size: 2607 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_x2_8c2c79d7-7186-44be-8b14-7923cb0fc95f.png
Type: image/png
Size: 3167 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0017.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_signaturebanner_e602538b-d2d2-4b06-8d65-3edb587d09c1.jpg
Type: image/jpeg
Size: 909156 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_linkedin2_a5930c15-804c-42e8-a409-8fc8bb6b42dd.png
Type: image/png
Size: 2607 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0018.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_facebook2_8163aee3-593b-481f-aecf-3f004bf0d8bf.png
Type: image/png
Size: 2264 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0019.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_x2_8c2c79d7-7186-44be-8b14-7923cb0fc95f.png
Type: image/png
Size: 3167 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0020.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_instagram3_6d55ee4b-bfab-47b6-a7ec-bdb847e33ccf.png
Type: image/png
Size: 3262 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0021.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_signaturebanner_e602538b-d2d2-4b06-8d65-3edb587d09c1.jpg
Type: image/jpeg
Size: 909156 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_logoforsignature_e73ff074-cb33-41b7-8a0e-df9d830d55df.png
Type: image/png
Size: 14963 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0022.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: C2_signature_youtube2_cf00ac2a-ec71-4a64-b7a7-1f8db2a4ea75.png
Type: image/png
Size: 2490 bytes
Desc: not available
URL: <http://lists.fsl.cs.sunysb.edu/pipermail/hotstorage-sc/attachments/20260716/ff53dd9d/attachment-0023.png>