137 karma · joined October 21, 2016
Socials: - hackernews@jawne.info.pl
---
When exporting Gmail and hitting an execution timeout, I would implement partitioning by date. Google Apps Script has a lock mechanism ( https://developers.google.com/apps-script/reference/lock ), and you can use user properties for progress tracking ( https://developers.google.com/apps-script/reference/properti...() ). Therefore, you can schedule a task every x minutes to pull x days of data and keep the cursor in user properties.
Google Apps Script is such an underrated tool. I use it all the time to link up different services, and it’s truly “serverless” in a way that makes sense. No added complexity—just webhook handling and periodic tasks, which is usually all I need to sync ticket systems with Slack, pull in data from Sentry, and so on. Plus, it’s straightforward, no extra layers to worry about. LLMs are actually pretty handy for getting these scripts going too.
I use Google Calendar’s scheduling and think it’s great, but it does have limits. I still have to scrape calendar events to keep an ongoing list in a spreadsheet, which helps for billing clients by month. Google Apps Script makes all this work reliably without extra cost or maintenance.
There are other options, sure, but asking someone to set up PostgreSQL, Next.js, or Docker just for a personal scheduling link seems like overkill. For a solution that just works without needing constant attention, Apps Script is more than enough.
Limited access control (e.g. CI pass required), so not very useful for end users. For machine-to-machine it's an additional layer of abstraction when a regular tarball is fine.
There is market of professional use of them.
Autosharing can be easily solved by simple Google Apps Script. I scan my personal calendar and share recording to Slack channel when I detect group meeting with recording available. Mail me, so I can arrange something for you.
Autorecording - yeah, this is missing. There is paid Chrome Extension which do that, but I have never tested it.
- one using a hostname match, low rule priority, requiring authentication
- the second one uses a hostname and ClientIp match, high rule priority, bypassing authentication
Regarding AWS, I would also add Firecracker for AWS Lambda, which uses KVM.
The key thing about Postman is that I was able to configure my own script to refresh the API token. For the internal API, we have a short-lived "access_token" token (~1 minute) and then a long-lived "refresh_token" (~1 day) based on the user's email address and password. When renewing the token, you receive information about its lifespan. You cannot create a new scratch token every time because you will be rate limited. I put all that logic in Postman hook script.
Making these HTTP requests in Curl – due to token refreshing – is painful.
Will Bruno support this use case?
You also want to learn about GitHub "rulesets" (if your GitHub plan offers it) because they enable central management of branch protection rules across all repositories. Using them, you can specify once at a level that branch protection rules are to be enabled, and then only add exceptions to this rule if needed, so you have security by default.
What is the criteria for selecting a session? These are not all the sessions, because there are some missing that interest me, for example: https://fosdem.org/2024/schedule/event/fosdem-2024-1652--new... and https://fosdem.org/2024/schedule/event/fosdem-2024-1651-data...
> proseable.com has not completed the Google verification process. The app is currently being tested, and can only be accessed by developer-approved testers. If you think you should have access, contact the developer. If you are a developer of proseable.com, see error details. Error 403: access_denied
Regarding selling it as an API. In Europe, PSD2 is the standard to provide third-party read-only access to banking data. I am using this to make my business bank account accessible to accounting SaaS. PSD2 requires renewal access every 3 months. At the same time, I have a summary of transactions in my e-mail every, so I would rather set forwarding once than keep to renew PSD2 (I set it, it expired and I do it manually).
This organization is in the Google Workspace ecosystem, but Google doesn't have documentation as accessible as Notion. We could try to implement Notion, but this will scatter the data storage and then there is the problem of archiving if the experiment fails. This looks like a plug-in solution to our problem of having Notion-like lightweight documentation and not scattering data.
Do I understand correctly that you charge a fee per organization regardless of the number of seats? This is important for this organization because it is a non-profit association, so there are many members, the board must provide access to information to all members, some members are minimally active, so per seat licenses seem to be often a blocker due to the large loss on inactive members.
However, it smells like self-made crypto.
* The cost of an IPv4 address in the market is constantly increasing
* We have recessions, so giants are looking for savings and profits by using their market position.
In addition, some providers are making IPv6 available more and more (there is no reason to consider IPv4 granted then), and others built on someone else's infrastructure are starting to be charged, so they pass this cost on to consumers.