Hacker Newsnew | past | comments | ask | show | jobs | submit | Humphrey's commentslogin

I love the simplicity! Does this store state in the browser?

Have you considered adding an export/import data option? I was actually expecting "Copy link" to have my months worth of event data encoded in the url after the # (so it would never be sent to the server, but means I could share the month with a friend). Just an idea.


Thanks! Yes, everything is stored locally in the browser — no backend at all.

And that’s a great idea. I’ve been thinking about adding an export/import option, and encoding the data into the URL hash actually fits the “offline + privacy-first” vibe really well.

I’ll explore it — would be super useful for sharing or backup without requiring any server.

Thanks for the suggestion!


A small suggestion that immediately came to my mind, why not try making it a JSON serialized data and base64 encode it just like JWT. So that it can be shared and loaded effectively.

Just thinking out loud here ;)


This is what I would do too but one problem I think there is a max HTTP URL length


If you look at the traffic, it doesn't send anything (I could test) to its server, and there are entries in browser's local storage.


Ho do you find Trailbase compares? Worth the switch?


Switching DBs is very invasive. Switching your application base even more so. As long as you're happy happy with PocketBase and there's nothing you're critically missing, the answer will almost certainly be: no. Is there anything you're looking for?


I've been trying out Pocketbase on a side project idea. I'm super impressed!

Having worked for many years on Django projects, Pocketbase seems like a perfect fit for those small to medium sized projects for which you don't want to create and maintain a traditional backend for.

Happy to answer any questions.


Django has great GIS integration. How does Pocketbase compare here ? Also, can Pocketbase work with PostgreSQL or is it SQLite only ?


SQLite only. I haven't come across any GIS integration. I think you should choose Pocketbase when it "not having features" and being lightweight is the feature you need.


Like Postgres has PostGIS, SQLite has Spatialite. https://www.gaia-gis.it/fossil/libspatialite/index

Unsure about integrating it with Pocketbase but I imagine it is reasonable to do.


How easily can I migrate from an existing sqlite-based backend?


I haven't tried this... but Pocketbase is opinionated in how it's schema is structured - and it needs to be the tool managing your schema.

Therefore if it was me, I would use the Admin UI to create a new db with a similar data structure, and then use a third-party tool to select data and insert into the new database.


is it suitable to maintain internal company KB? small size 15-20 people tech team


It's meant to build apps with. If you want to build a knowledge base, sure. But why would you build a Knowledge Base when you can use Confluence, Notion, https://www.getoutline.com/, https://clickup.com/, etc that already exist? There's free self-hosted ones too.


I’ve been using on a personal side project - but found that LLMs seem to be permanently confused over how to interact with pocketbase - to the point where I’ve even tried creating a Claude Skill to try and reduce the confusion.

Wondering if anyone else has had a similar experience?


From the top of https://pocketbase.io/faq/

> If you don't have the time to at least skim through the documentation and you plan to solely rely on some AI tool, then please do NOT use PocketBase!

It's a niche little product that's alpha-level quality and changes frequently, I don't know why you would expect LLMs to be good at it.


I tried to use LLMs to help me with server-side pb coding, but it was mostly a flop. LLMs don't have an up-to-date state of pb's API. 2 out of 3 times the LLM would give at least a hint how to go about something and the rest is me manually editing the code, reading the docs or looking at pb's source code. All in all, I consider it a nice "pair-programming" type of experience but one can't rely on LLMs to do the pb work for you.


This is what worked for me… clone the pb repo and stick reference to it in my agents.md. I put additional notes in my own addendum.md in the line cloned repo. ChatGPT-codex variants handle it nearly flawlessly and no issues with being out of date. I use the same pattern for all “niche” libraries


Not with Pocketbase - as I haven't found I've needed to look into the docs too much. But I have come across a whole bunch of areas LLM's seem to always answer incorrectly for. For example, ChatGPT has almost never corrected told me how to use the UI in Davinci Resolve.


Instead of redesigning the "pocket" they should just make phones that fit inside regular pockets.


About to switch from stable to beta - purely so I can get get rid of liquid glass and hopefully the other bugs in 26.0.


I’m doing the same - and also for the fact that I can finally turn off the lock screen’s swipe for camera that I seem to activate too often when my phone’s in my pocket


Hot take: iPhone Air isn't about making phones lighter, but to justify making their other models heavier.

iPhone Air is 165g.

The new iPhone Pro 17 is 204g but the 15 Pro was only 187g. iPhone 17 is 7g more than the iPhone 16 which was 170g (only 5g heavier than the new Air).

Their pricing ladding places the Air above the regular 17 and below the 17 Pro.

If Apple didn't make the Air, then the 17 family would have been Apples "Heaviest range of iPhones they have every made".

That said, I am very happy about how Apple are adding more battery to all their phones - which might be were the extra weight is coming from.


Hot take

"Hot takes" are for Reddit.

People on HN are expected to think before they respond.


The Apple Configurator seems like a great tool to setup a phone for your children or tech illiterate elderly parents. Many of us would have people in our lives who might actually understand how to use their phone if the only icons on the home screen where messages and phone. I could imagine ChatGPT would be a good option for them to be able to look up information in the real world.


Whether you think that or not is not the issue - the fix is very obvious once pointed out to you. The arguement the author is making is that a bug like that TS issue can be very difficult and time consuming to track down and is not picked up on by the compiler.


Does anybody have any experience migrating to PlutoPrint from WeasyPrint? Is it seamless? Faster? Any teething issues? Are their reasons to stay with WeasyPrint?


Anybody know how this would work for multiple nginx backends or failover machines - as I assume it's only possible to auto-fetch certificates for the live machine. Is it expected that you would use scp or similar to copy certs from the live machine to the failover / new server?


You don’t need exactly the same cert for failover. You only need a valid certificate. You don’t even need the same cert for every entry in your load balancer. Client will pick a single IP address when resolved, then connect to it and will keep using that TLS connection for the whole session.


But you do need Let's Encrypt (or whatever ACME provider you use) to connect to the same server you are trying to set up the cert on. And they intentionally try to fetch the challenge response from multiple geographically distinct locations.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: