Unlike Instapaper, which focuses on saving full articles for reading, PostPocket is designed for quickly saving and organizing content via share extension from any mobile app, allowing seamless capture without interrupting your scrolling. PostPocket saves links and associated metadata rather than the full content to ensure privacy and data security.
It deleted 100s of files, most of which were Jest test files, and potentially all of which were a mistake. I restored them all with `git restore $(git ls-files -d)`.
I then ran `tsc` on the remaining _modified_ files and `Found 3920 errors in 511 files.`
Obviously at that point I had no choice but to discard all changes and unfortunately I would not recommend this for others to even try.
You need a valid tsconfig that defines the scope of the project and it seems renovate’s tsconfig doesn’t meet this requirement. You can always --skip manually as an alternative option.
Renovate's TS tooling seems to work fine otherwise, and for ts-remove-unused as a new tool wanting to get adoption then you should be aiming to work the way your users already work, and not fail + tell them that they are the ones which need to change.
BTW the VSCode extension which someone else linked to discovered everything perfectly, which is another hint that your tool needs to improve, not your users.
Even if tsconfig.json was very important, and the users are all wrong and you're right, the only thing your readme says is: "The CLI will respect the tsconfig.json for loading source files." which is insufficient.
Most transformations like this are not possible with pure static analysis and require some domain knowledge (or repo-specific knowledge) in order to pull off correctly. This is because some code gets "used" in ways that are not apparent i the code.
I'm surprised to find there's not more demand for "back to back" travel wifi routers, e.g. so you can connect once to a hotel wifi and immediately all devices are connected via the router's own wifi. This is useful not just for working around device limits but also for simplicity of setup when you have kids.
I own one and tried it for a business trip.
It's a cool nerd-toy. It's not cheap and not always easy to setup for anyone who is not technically savvy.
I like it, but I wonder if I want to carry it when I go carry-on only in Europe. I guess most people will trade some privacy and inconvience for weight- and cost-savings.
If you have a non-artificially-limited android phone (i.e. rooted), you can just open a hotspot with everything going thru your wireguard vpn back to home.
If you have stock android or IOS, then the real owners of your device won't allow you do this, since they get location data from your network on all those devices.
Visicom really pumped the ManyCam lifetime upsells. I found 15 emails over an 18 month period in 2020-2021 with them pitching lifetime (which I eventually bought). An example email text they used is:
> Upgrade now to ManyCam Studio Lifetime for only $39 and get access to all the future versions and updates, forever!
What they presented to the user was unequivocal. In a just world, the company who sold ManyCam (Visicom Media) should not be able to get away with this.
> On June 30, 2022, we entered into a License Agreement with Visicom (the "License
Agreement"), pursuant to which we agreed to distribute, at the discretion and
direction of Visicom, a specified number of ManyCam software updates to certain
license holders to whom Visicom has previously granted a "lifetime" license to
ManyCam software. As consideration for distributing the software updates,
Visicom paid us an initial upfront nonrefundable payment of $65,000. The License
Agreement provides that Visicom may purchase additional licenses at prices
specified therein. Other than providing a one-time, limited license to Visicom
for the distribution of ManyCam software updates pursuant to the terms of the
License Agreement, we do not have any obligation to provide support or service
to the licensee end users.
That pumping might have been seen as a warning that the company either does not intend to support the product much longer, or has doubts that it will be able to do so. And while I agree with your final sentence, unless Visicom was careless, the actual license agreement, which supersedes the promotional claim, will have permitted what happened and so essentially revoked the offer. Caveat emptor!
Renovate is indeed AGPL, but if you're just running it as a CLI, do you think there's anything to "watch out for"? It does not make any project you run it against AGPL, that's for sure.
Also you should be aware that dependabot-core, which dependabot-gitlab wraps, is not technically Open Source at all: https://github.com/dependabot/dependabot-core/blob/main/LICE...
Wrapping a non-open source project in another project which claims to be MIT licensed does not change the underlying license. I'm not a lawyer but question the validity of them doing this without larger disclaimers.
However, I think that it's likely not something to "watch out for" either. Likely both licensing approaches were intended as a way to forbid or discourage competing services and each project welcomes people self-hosting.
In short I don't think that the license of Renovate or Dependabot is likely material for anyone planning to run it for themselves.
Thanks for weighing in, and for drawing attention to the wrapped nature of dependabot-gitlab -- I didn't drill down into their implementation
As for the "watch out," I apologize if that came across as scolding or whatever, but in my company, and likely quite a few others, AGPL software is forbidden. Thus, maybe I have said "be aware" instead of "watch out," so I'll try to choose more neutral advisory language next time
Your "but it's just a CLI" is the nuance of the AGPL that I don't want to pay lawyers to disambiguate since this very thread was about running a GitLab bot, over the network, or in CI which is hosted on runners that connect over the network
Maybe I just need to stay out of these threads and let people do their own license homework, but I certainly do get value when someone else makes me aware so I can dismiss the tooling. No good deed goes unpunished, I guess
This is interesting. It would be fun if one day contract negotiations were two people in their respective browsers moving HTML sliders back and forth across the “permissive” scale for each term (days termination notice, SLAs, etc).
That is definitely a future a lot of people can see. And there’s nothing stopping anyone from screensharing Fast Path and talking through the questions with a vendor or customer.
For the old school, here and now, Fast Path downloads include not just terms but a term sheet listing out all the questions answered, the answers chosen, and the other options available. It’s perfectly possible to send that across to the customer and get a markup back.
If there end up being this-not-that changes, say from no patent indemnity to one of the other options, the seller can just go back to the site and generate new terms per the finalized term sheet.
Yarn’s offline support is not directly tied to PNP. Yarn v1’s support for “offline” installs was a day one requirement, and as I understand it one of the primary drivers for Facebook engineers (at the time) to drive the creation of Yarn.
If offline installs is what you want, I don’t see any advantage of node_modules compared to this feature - only disadvantages (size, noise, and cross-platform incompatibilities).
reply