Deep Dive Analysis: Complete flow from routing to rendering
Source: Next.js repository (vercel/next.js)
Analysis Date: October 15, 2025
| const { google } = require("googleapis"); | |
| const fs = require("fs"); | |
| // You need to go to Google Cloud console (console.cloud.google.com), then APIs | |
| // & Services -> Credentials. There, create a new service account (or reuse | |
| // existing if you have one). Click on a service account, go to Keys, and create | |
| // a new key, and download JSON for it. You'll use path to that JSON for | |
| // SERVICE_ACCOUNT_FILE var. | |
| // | |
| // Then, go to Google Play Console, then "Users and Permissions" on the left |
| const fetch = require("node-fetch"); | |
| const fs = require("fs"); | |
| const jwt = require("jsonwebtoken"); | |
| const util = require("util"); | |
| // To get the private key, go to App Store Connect (appstoreconnect.apple.com), then "Users and Access" | |
| // at the top. Then go to "Integrations" -> "App Store Connect API", under "Team Keys" create a new key, | |
| // and you'll be able to download the private key for it. | |
| const PRIVATE_KEY = fs.readFileSync("AuthKey_F2BLAHBLAH.p8", "utf8"); |
This is an attempt to take a step back and summarize all proposed approaches to private messages (DMs, group chats, and general-purpose nostr-within nostr, including for large groups of people) for the purpose of building a secure, feature-complete, interoperable solution.
This topic has come up repeatedly over nostr's history, and has entered the limelight again because of HRF's e2e encrypted group chats bounty. The hope here is to get everyone on the same page and hammer out one or more NIPs that can incorporate the best parts of all proposed solutions so we can finally get secure messaging on nostr.
Please comment with thoughts, criticisms, missing proposals/implmentations, and I will update the gist as we go along.
| // ignore_for_file: curly_braces_in_flow_control_structures | |
| /* | |
| * Performance benchmark of different ways to append data to a list. | |
| * https://gist.github.com/PlugFox/9849994d1f229967ef5dc408cb6b7647 | |
| * | |
| * BytesBuilder | builder.add(chunk) | 7 us. | |
| * AddAll | list.addAll(chunk) | 594 us. | |
| * Spread | [...list, ...chunk] | 1016446 us. | |
| * Concatenation | list + chunk | 1005022 us. |
| import 'dart:math'; | |
| import 'package:flutter/material.dart'; | |
| class SliverAppBarStatus extends StatefulWidget { | |
| const SliverAppBarStatus({Key? key}) : super(key: key); | |
| @override | |
| _SliverAppBarStatusState createState() => _SliverAppBarStatusState(); | |
| } |
When I click on links from Slack or Outlook on MacOS they open in seemingly random browser windows/profiles. This is annoying.
Open links in a particular google chrome profile window. Be less annoyed.
- In Chrome, visit
chrome://versionand find the desired profile name. Mine wasDefault. Copy that profile's directory name, likeProfile 2orDefault, not the profile's vanity name you see when you click on your profile icon in the browser. - Install Finicky:
brew install finicky. After install it should be running and you should see the icon in the upper toolbar. - From the Finicky Toolbar Item, click
> Config > Create New - Edit the new file
~/.finickyand make it look something like this, filling in your profile name:
| --- | |
| version: "3.8" | |
| services: | |
| master: | |
| image: chrislusf/seaweedfs:latest | |
| command: master -mdir=/data | |
| networks: | |
| - weed |
| # frozen_string_literal: true | |
| require 'progress_bar' | |
| require 'json' | |
| require 'open-uri' | |
| namespace :pseudo do | |
| desc 'Pseudonymize user data' | |
| task :perform => :environment do | |
| count = User.count # get count of users currently in DB | |
| bar = ProgressBar.new(count) # prepare some nice output |