Create Account
Log In
Dark
chart
exchange
Premium
Terminal
Screener
Stocks
Crypto
Forex
Trends
Depth
Close
Check out our API

DBSC
Deepwater Beachfront Small Cap ETF
stock NASDAQ

Inactive
Apr 23, 2026
25.84USD+0.115%(+0.03)167
Pre-market
0.00USD0.000%(0.00)0
After-hours
0.00USD0.000%(0.00)0
OverviewHistoricalExchange VolumeDark Pool LevelsDark Pool PrintsExchangesShort VolumeShort Interest - DailyShort InterestBorrow Fee (CTB)Failure to Deliver (FTD)ShortsTrends
DBSC Reddit Mentions
Subreddits
Limit Labels     

We have sentiment values and mention counts going back to 2017. The complete data set is available via the API.
Take me to the API
DBSC Specific Mentions
As of Aug 6, 2026 8:59:21 AM EDT (1 min. ago)
Includes all comments and posts. Mentions per user per ticker capped at one per hour.
29 days ago • u/Beginning_Gain_4230 • r/fidelityinvestments • request_for_fidelity_to_adopt_passkeys_and_plan • C
Good comment. I totally agree on passkey support. However, if I had to nitpick, I might prioritize mitigating against infostealers above the quantum threat you mention.

As I understand it, infostealer malware harvests live session cookies/tokens directly from an infected device after a user has already authenticated--thereby bypassing MFA and passkeys entirely, since the attacker isn't stealing the credential, but the already-authenticated session.

Apparently, Chrome on Windows now has Device Bound Session Credentials (DBSC), which cryptographically binds a session to hardware on the user's device so a stolen session token can't be replayed elsewhere, are just beginning to address this threat. I'd ask that Fidelity's security roadmap address this threat as well --not just passkey adoption at login, but protections against post-authentication session theft, such as short-lived sessions, or requiring the user to re-authenticate for any substantive actions, or device-bound session credentials, etc. To some extent, I guess we can self-mitigate against this by only using Fidelity from mobile environments that tend to be more secure against malware (like iOS, etc).
It definitely is a hard problem.
sentiment -0.78
29 days ago • u/Beginning_Gain_4230 • r/fidelityinvestments • request_for_fidelity_to_adopt_passkeys_and_plan • C
Good comment. I totally agree on passkey support. However, if I had to nitpick, I might prioritize mitigating against infostealers above the quantum threat you mention.

As I understand it, infostealer malware harvests live session cookies/tokens directly from an infected device after a user has already authenticated--thereby bypassing MFA and passkeys entirely, since the attacker isn't stealing the credential, but the already-authenticated session.

Apparently, Chrome on Windows now has Device Bound Session Credentials (DBSC), which cryptographically binds a session to hardware on the user's device so a stolen session token can't be replayed elsewhere, are just beginning to address this threat. I'd ask that Fidelity's security roadmap address this threat as well --not just passkey adoption at login, but protections against post-authentication session theft, such as short-lived sessions, or requiring the user to re-authenticate for any substantive actions, or device-bound session credentials, etc. To some extent, I guess we can self-mitigate against this by only using Fidelity from mobile environments that tend to be more secure against malware (like iOS, etc).
It definitely is a hard problem.
sentiment -0.78


Share
About
Pricing
Policies
Markets
API
Info
tz UTC-4
Connect with us
ChartExchange Email
ChartExchange on Discord
ChartExchange on X
ChartExchange on Reddit
ChartExchange on GitHub
ChartExchange on YouTube
© 2020 - 2026 ChartExchange LLC