David Humphrey

Rebased onto @DukeManh's test changes for SAML.

Looks like this is good to go.

This is a really interesting idea. The best way to approach this would be to keep track of our "cursor" in the timeline, where we load the posts, see https://github.com/Seneca-CDOT/telescope/blob/2359565d11aa045eedadfee2ef72d29f62d87bee/src/web/src/components/Posts/index.tsx#L43-L62....

This isn't critical for 3.0

Noticed this is still an issue: ``` error - ESLint: Failed to load plugin 'react' declared in '.eslintrc.js » @senecacdot/eslint-config-telescope': Cannot find module 'eslint-plugin-react' Require stack: - /vercel/path1/__placeholder__.js Referenced from:...

The most recent build you did yesterday had it: ``` info - Checking validity of types... -- 12:13:08.704 | error - ESLint: Failed to load plugin 'react' declared in '.eslintrc.js...

By all means, @cypersii.

@DiegoHdz7 sure, go for it.

cc @PedroFonsecaDEV. Maybe we should use trailing ellipses `...` to shorten it, and show the whole thing on hover?

Pre-3.0 or Post-3.0? Seems big.