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

I'm really struggling to see who this phone is aimed for. Why would someone pay a subscription for their "own" phone that is cut off from the major app stores?

More like "you are what you think".


No, literally the opposite of that. That's the model which is being refuted.


I migrated to raindrop.io[1] few months back and IIRC the file downloaded from Pocket did have tags. I again tried following the same steps and the CSV does have tags so I'm not sure why they save the export will not have tags?

[1] https://raindrop.io/integrations/pocket


Not sure if you have seen this? https://layoffs.fyi/



Why would someone do this? Isn't it basically asking to get the account deactivated due to piracy concerns esp given that now Amazon has the whole trail of things you have pirated?


People do it because documents that go through the e-mail thing sync across devices like Amazon purchased books.


> Doesn't mention the hardest part ... dealing with pages whose content is mostly dynamic and generated client side (SPA's)

Given this is from 2004 I'm not surprised.


That was about when I was writing my crawler (not for search but for rules-based analysis). Even in 2004 a lot of key DOM elements were created/modified client side.


Though I do remember now that we solved it by having a separate mechanism for accessing pages that required logging in or had significant client-side rendering by allowing the user to record a macro that was played back in a headless browser. Within a few years though it was obvious a crawler would need to be able to automatically handle client scripts.


What's the relation between this tutorial and the "hands on rust" book? Overlapping content or contains bits and pieces from the book?


Good stuff; approximately how long did this project take to develop?


Hi, approximately it took my two months, including the documentation, without a full-time strict calendar. But before it, I worked on development of a browser-based video conferencing system (using open-source modules, with some other languages except Go), so I have enough know-how about the domain, since the start of the pandemic (of course not deeply as this project).


These need not be the only two options. App developers could charge money for updates made i.e. new versions while the old versions keep working as advertised.

Instead of "cloud storage" which might incur ongoing charges, apps can very well hook onto my GDrive/OneDrive to persist data. Also, games have done this "free updates to this app I paid" for years now.


Yes, "pay for a major new version" was the industry model for many years. Office, Photoshop, etc. In the end you're sort of forced to upgrade by file compatibility every two or three years, so it's a subscription with a slightly uneven payment schedule.

There are still some apps that do this, Things is a good example. But that creates all kinds of other challenges when a big part of the product is a service (like ours) if you want to support all versions of the client in perpetuity.


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

Search: