What’s holding me back is mostly the fact that historically there’s been 10 red months in the btc cycle and we’re at 7, so we’re not going back to bear market yet if this data is to be trusted, which I don’t know for sure. Many things to consider here, my feelings are telling me we can go lower but man idk submitted by /u/Freemlvzzzz [link] [Kommentare]
ok then submitted by /u/krysisalcs [link] [Kommentare]
I got out with a small profit in 2022. Got tired of the scammers and crypto bros. Since then my robinhood stock account had done quite well. Should I wait till October to get back in? submitted by /u/CoatForeign2948 [link] [Kommentare]
Not on copium, just curious. Will it lead to a bull run ? submitted by /u/-InvictusShadow [link] [Kommentare]
Hey everyone, hope this is okay to post here. My co-author and I are currently between institutional affiliations, which means we don't have the academic email arXiv needs for an endorsement. We're hoping to find someone in cs.CV willing to take a quick look at our paper and endorse it if it meets your bar. The project: Locate-SAM2 We built a training-free pipeline connecting NVIDIA's LocateAnything-3B to Meta's SAM 2.1 through a lightweight adapter. The question we wanted to answer was simple: in a modular text-to-mask pipeline where everything is frozen, does the choice of grounder actually matter for the final mask? A few specifics, since the details are what tell you we're not just generating noise: On RefCOCO val, our system reaches 0.772 mIoU versus 0.717 for Grounding DINO Base, using the same SAM 2.1 backend throughout. RefCOCO appears in LocateAnything's training data, so we frame this honestly as in-domain benchmarking, not zero-shot transfer. We're not pretending otherwise. The paper has controlled comparisons across RefCOCO/+/g, adapter ablations, a ground-truth box oracle, a failure taxonomy, and a nonsense-prompt probe showing the pipeline needs abstention logic. Code is on GitHub and the paper is close to submission-ready. What we're hoping for Mainly an endorsement: someone to read the draft and, if they think it holds up, endorse us on arXiv. We'd acknowledge it and that's the whole ask. If anyone wants to get more involved, we're open to expanding the experiments or pointing the paper at a specific venue, and we'd talk co-authorship based on real contribution. We also have separate work in progress in physically-constrained DL, geospatial AI, and AI governance, in case any of that overlaps with what you do. We're not looking for a blind voucher. Drop a comment or a DM and we'll share the PDF and the repo. Happy to answer questions, and thanks for reading. submitted by /u/j_root_ [link] [Kommentare]
Don't get your hopes up.
We have 50,000 registered participants in SSoC 2026. Three hundred projects. Five thousand mentors. The most impactful engineering work we did this season? A hidden admin dashboard that no participant will ever see.