791–800 of 900 posts
Two things: I am building a Pinterest clone that filters out AI generated imagery[1]. It is built on top of Bluesky so gets the benefit of its large library of well alt-text'd images, which aids with search. Also working on a new kind of social media, where every user is a verified human[2]. The idea is to avoid the problems that sock puppet accounts controlled by the rich and powerful can have on our society. Again,…
But what about the furries :(
Earlier quoted context omitted.
Cool idea, tried to signup and got: Invalid state parameter
:( Are you on mobile by any chance?
You could also clear your cookies - in case you managed to log-in the previous time and they got set.
Optimizing the Marginalia Search index code. The new code is at least twice as fast in benchmarks, but I can't run it in production because it turns out when you do it's four times as slow as what came before it for the queries that are the simplest and fastest to the point where queries exceed their timeout values by a lot. I'm 97% certain this is because the faster code leads to more page thrashing in the mmap-base…
Which part of the index are you putting in the buffer pool here? The postings list, the doc store or the terms dict? Is it being cached for future queries or are you just talking about putting it in memory to perform the computation for a query?
Caching will likely be fairly tuned toward the operation itself, since it's not a general-purpose DBMS and I can fairly accurately predict which pages will likely be useful to cache or when read-ahead is likely to be fruitful based on the operation being performed.
For keyword-document mappings some LRU cache scheme is likely a good fit, when reading a list of documents readahead is good (and I can inform the pool of how far to read ahead), when intersecting document lists I can also generally predict when pages are likely to be re-read or needed in the future based on the position in the tree.
Will definitely need a fair bit of tuning but overall the problem is greatly simplified by revolving around very specific types of access patterns.
Im investigating creating a nattokinase overexpression strain for fun. This is my second home-brewed food GMO! Basically, nattokinase is an enzyme made by natto (Japanese fermented soybeans). It’s been show clinically to help against blood clots. Unfortunately, the clinical dose is 5x the quantity in a serving of natto. That’s too much natto to eat! So I’m working to genetically engineer a normal, typical natto strai…
Earlier quoted context omitted.
Cool concept, would you expect this to be compatible with Firefox/Safari as well? Safari in particular would be useful as it doesn't natively support Puppeteer/Playwright.
Absolutely. However, it is easier to start with just Chromium flavor of browsers. The two important concepts from Puppeteer/Playwright are managing the lifecycle of pages (tabs) and frames and the other is using handles / locators. There are a lot of limitations using the extension API in any browser instead of CDP / Webdriver BiDi. I'm curious, how would you use this idea?
Earlier quoted context omitted.
Thanks for the feedback! The long URL is a compromise that lets the service work without requiring sign-ups or storing user data. I’ll definitely try to make the “support my work” popup less aggressive.
I think you could cut the URL length in half if you remap the JSON keys before compressing. Like turning "total": 18, "vatTableSummaryIsVisible": true, "paymentMethod": "wire transfer", "paymentMethodFieldIsVisible": true, "paymentDue": "2025-08-27", "stripePayOnlineUrl": "https://example.com", "notes": "Reverse charge", "notesFieldIsVisible": true, "personAuthorizedToReceiveFieldIsVisible": false, ... to this "1": 1…
Earlier quoted context omitted.
Which part of the index are you putting in the buffer pool here? The postings list, the doc store or the terms dict? Is it being cached for future queries or are you just talking about putting it in memory to perform the computation for a query?
I'm primarily looking at document lists and possibly the keyword-documents mapping. Caching will likely be fairly tuned toward the operation itself, since it's not a general-purpose DBMS and I can fairly accurately predict which pages will likely be useful to cache or when read-ahead is likely to be fruitful based on the operation being performed. For keyword-document mappings some LRU cache scheme is likely a good f…
Edit: I should specify they shard the corpus by document so there isn't a replica with the entire term dict on it.
Still working on https://phrasing.app - an app for polyglots to learn over 120 languages in the most effective manner and a beautiful UI. Just finished a onboarding flow, now updating the search and create experience to fall more in line with actual usage from users, then hopefully prepping for a more public launch :) Had a fun week fixing up the application so it’s 100x faster on 5 different axes, and it’s starting…
I signed-in and took a look around getting a few "Error rendering home" errors occasionally, fyi.
I was a little surprised at the CC#/subscribe page, since the prices didn't seem to be matching up with the marketing pricing page.
You might want to consider having like a sandbox account with some sample materials so people can feel the power of the app rather than depending on someone subscribing based on the video only.
Cool idea!