yolo42

> I've wondered about how to exfiltrate all of my accumulated links I've put into Pocket over the past ~7 years or so.

Yeah, this is what has prevented me from moving away. I was a premium user and used to use their search. I’m not anymore but I still want to keep the list around. I still go back and find references that Google doesn’t show anymore.

There are some apps that move data from pocket to kindle or such, but having an import from pocket in a new product would be really nice.

Somewhat tangentially related. Pocket seems like a dead product. I have been using it since it can out but it feels old, slow and quite behind.

I use it extensively to capture a reading list and then trim it occasionally. Any recommendations for alternatives?

Offline web-rendered article views are a must - something pocket can’t do. And their text mode misses quite a few important details when there are equations or illustrations in the content.

Yes. Please take a look at grpc-gateway. You write your specs as proto files and then get handlers and middlewares to implement the endpoints.

This is exactly what I started using in my new open source project (not announced yet) and the experience has been amazing. I was wary about it in the beginning but it quickly became clear that this is the easiest and probably the fastest way to get this job done. The community and tooling has come far ahead.

I've adopted the doc of docs method and it has made my life incredibly easy! I was in a position where I'm a bottleneck of information because no one else in the company new about the product other than me. I wrote a ton of documentation for employees and users but I still was spending upwards of 20 hours every week just answering questions. I built the doc of docs in 2 hours and that has helped significantly. Combine this with always replying with a link instead of a dedicated explanation has been extremely fruitful!

Same here!

It is simple, searchable and extremely flexible.

I have a list for each date in a Logbook list and keep dumping all my completed TODOs at work there. It has come in useful a few times already to recall when did I do thing X.

I also have an Inbox list to keep all my thoughts in there, which get groomed once a couple of weeks. The mobile app is a little slower than I'd like but it is the best tools I've found to organize my thoughts.

I also get daily emails from Workflowy which provides a nice timeline of everything I've done or recorded at any point.

Indeed, this realization is hitting me slowly.

They could surely fork it and take it from there. They would rather want that they own the code-base so that their enterprise customers can be assured that it is a product that they control and own.

My product, unintentionally, solves a lot of problems for the enterprise product that my company sells.

Thank you for the comment! I totally get what you and other threads are trying to say and I don't disagree with what you are saying.

I probably should have cleared this out in my original post (my bad) that I do not wish to pursue the legal route. I personally feel that in my case, it will just drain everyone's energy for not much gain at the end. Also, personal relationships matter to me as well.

I'm trying to find ways to get compensated for the time and effort I've put into it. If not financially, then in some other forms. But I don't have any ideas.

> What kind of outcome do you want?

I wish I knew myself better.

Maintenance and taking the product forward will naturally become part of my job, so that's a given (and I'm happy about it).

What can I ask more for is what I'm trying to figure out and having a hard time.

I'm generally creative with software and products but I'm really bad when it comes to negotiations and figuring out a good barter.

I absolutely don't want to take the legal route and want to work something out mutually.

It is not that they want me to spend work time on it. They want me to transfer ownership of the project to them. That's the part that I do not wish to do.

The way things work at this place, I'll probably end up maintaining the product until I leave my job.

The reason for not transferring over is that once I do that, they will essentially not let me create features that I think can be done better using my product, because they exist in some other product.