theogravity

Short via Hyperliquid or some other crypto exchange that tokenizes stock? HL does have a trading pair for MSFT and trades 24/7.

The site visually feels "compressed" due to the font used? It's a bit jarring. The tutorial link in the header nav doesn't go anywhere.

When you're building a social networking site like this, when do you need to start to worry about laws from different states and countries (eg age bans, data export, etc)?

Site renders extremely poorly on mobile safari that it is completely unreadable.

This is really cool! How are you sandboxing the tiles and allowing limited JS execution?

If I'm on 18.7.1, do I still need to upgrade?

https://www.cvedetails.com/version/2021355/Apple-Iphone-Os-1...

seems to be the same as 18.7.2

https://www.cvedetails.com/version/2037518/Apple-Iphone-Os-1...

Paywalled.

You need to update again.

The second example confuses me. The Person type has isCool: boolean, not an explicit true. How does using satisfies here pass coolPeopleOnly?

Really interested in how you do this. When I as looking into building my own finance-related app, you have to pay a ton to get market data (stocks, crypto, ETFs, options) and connecting bank accounts if it's not for individual use (you still have to pay for individual use, but not significantly as much).

Adding new transports and documentation to my Typescript logging library (MIT licensed), LogLayer (https://loglayer.dev). Just added documentation for Bun and Deno support added some new logging library transports (LogTape), and finishing up Logflare and Betterstack transports so you can send logs to their logging APIs.

It's already happening. There are visual novel groups that take pateron sponsorship to run the script through machine translation. It's now done in giant batches. They're released for free and I am not able to speak of the quality as I've never tried them, but when I see reviews on steam for a VN that has been machine translated, it never results in a good review.

Yes

My first thought would be consistency in localization / typesetting. Groups have their own ways of localizing and typesetting content and most likely would not want to share their style guide when they lost out on something they recently translated to a lower bidder.

This surprisingly made this easy to remember for me.

Unfortunately, the merge sort instructions doesn't make sense to me, specifically step 3.

I also had similar issues and wrote a guide on how to use LogLayer + pino to get server-side logs working properly.

https://loglayer.dev/example-integrations/nextjs.html

Overall, the logging experience in Next.js is terrible, and not being able to chain middleware, even more so.

Really love the idea! I tried going to the FAQ on mobile safari on iOS and can't scroll on the answer sections, so the text is cut off.

Is it me, or am I the only one not finding the play button on this via mobile safari?

Same. Using Mobile Safari on iPadOS on an M2 iPad Pro.

The statement was revised later to specify the date "July 5, 2025" as that of an asteroid impact,[8] or even the end of the world.[9]

I'm not the OP.

In my new transport, I added a PROMPTS.md file that just has the prompts I used

https://github.com/loglayer/loglayer/blob/master/packages/tr...

I discovered the local docker install and managed to write the transport:

https://loglayer.dev/transports/victoria-logs.html

Is there a way to sign up for the service to test it? It seems I need to book a demo first?

Definitely possible. HTTP direct send is a common pattern that I'm working on an HTTP-specific transport that can be used for these use-cases (vs making a unique impl for each one).

I'll reach out when this is available.

This is really cool considering how expensive DataDog can get. I'm the author of LogLayer (https://loglayer.dev), which is a structured logger for TypeScript that allows you to use multiple loggers together. I've written transports that allows shipping to other loggers like pino and cloud providers such as DataDog.

I spent some time writing an integration for HyperDX after seeing this post and hope you can help me roll it out! Would love to add a new "integrations" section to my page that links to the docs on how to use HyperDX with LogLayer.

https://github.com/hyperdxio/hyperdx-js/pull/184

I think FusionAuth does something similar. They have a global user, and uses the notion of tenants / application registrations (which I think is comparable to a Tesseral Organization) to segment the same user.

Then you can define applications (which are mapped 1:1 to tenants) where a user has a registration entry against that application, where a user can be referenced by their global user id, or application-specific user id.

Applications are OAuth2 applications (meaning a dedicated client id / secret), so we only create a single application and tenant, and maintain organization segmentation on our own application / db side instead.

(We're paying customers of FusionAuth. Anyone from FusionAuth, feel free to correct me.)

I totally recommend the Basement Brothers YouTube channel which has a large set of reviews with summarized playthroughs and historical background for PC-88 and 98 games:

https://www.youtube.com/watch?v=96tLZTtNcZA&list=PL_W1EM66_B...

As another asked, "why?" on no JWT? It makes interfacing with our API servers so much easier as we don't need to maintain infra for sessions and wouldn't be limited by the 4kb limit for sending cookies.

No hooks on the FE side. We use a global lock via a promise. Our API clients are not tied to react in any way.

For all API calls, if the lock is not set, it checks if the JWT is still valid. If it is not, then the lock is set by assigning a new promise to it and saving the resolve call as an external variable to be called after the refresh is done (which resolves the held promise on the other calls, allowing the latest token to be used).

All calls await the lock; it either waits for the refresh to complete or just moves on and performs validation with the currently set token.

Looks like this:

- await on lock; if the lock has been resolved, will just continue on

- Check for JWT validity via exp check (the API server itself would be responsible for checking signature and other validity factors); if not valid, update lock with a new promise and hold the resolver. Perform refresh. Release lock by resolving the promise.

- Use current / refreshed JWT for API call