Forgejo has a package registry that handles 23 ecosystems. Packages are uploaded directly -- there's no pull-through cache from upstream registries like npmjs.org or crates.io. git-pkgs/proxy is a standalone caching proxy for 16 ecosystems that already solves this problem. The question is what can be reused.
This has been requested multiple times in the Gitea tracker (forgejo inherits these):
| # Per-project history | |
| function _set_project_history() { | |
| local project_id="" | |
| # Check if we're in a git repository | |
| if git rev-parse --git-dir > /dev/null 2>&1; then | |
| # Try to get the remote URL (origin by default) | |
| local remote_url=$(git config --get remote.origin.url 2>/dev/null) | |
| if [ -n "$remote_url" ]; then |
g.co, Google's official URL shortcut (update: or Google Workspace's domain verification, see bottom), is compromised. People are actively having their Google accounts stolen.
Someone just tried the most sophisticated phishing attack I've ever seen. I almost fell for it. My mind is a little blown.
Someone named "Chloe" called me from 650-203-0000 with Caller ID saying "Google". She sounded like a real engineer, the connection was super clear, and she had an American accent. Screenshot.
They said that they were from Google Workspace and someone had recently gained access to my account, which they had blocked. They asked me if I had recently logged in from Frankfurt, Germany and I said no.
I asked if they can confirm this is Google calling by emailing me from a Google email and they said sure and sent me this email and told me to look for a case number in it, which I saw in
This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1
This document descrives the process of setting up headscale with swag, using letsencrypt certs.
This assumes you have a subdomain (e.g. wg.example.com) pointing to your SWAG instance and want to use it as a reverse proxy.
Add the subdomain for your desired headscale domain to your .env file.
For example:
SWAG_EXTRA_DOMAINS=wg.example.com
In programming languages, literals are textual representations of values in the source code. This is a syntactical concept.
Some examples:
7 # integer literal
| 0810 b' from ' | |
| 0678 b' ssh2' | |
| 00d8 b'%.48s:%.48s():%d (pid=%ld)\x00' | |
| 0708 b'%s' | |
| 0108 b'/usr/sbin/sshd\x00' | |
| 0870 b'Accepted password for ' | |
| 01a0 b'Accepted publickey for ' | |
| 0c40 b'BN_bin2bn\x00' | |
| 06d0 b'BN_bn2bin\x00' | |
| 0958 b'BN_dup\x00' |
| name: CI | |
| on: push | |
| jobs: | |
| brakeman: | |
| name: Brakeman | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/checkout@v4 | |
| - uses: ruby/setup-ruby@v1 | |
| with: |
| create_table :stowaway_records do |t| | |
| t.string :record_type, null: false | |
| t.jsonb :record_attributes, null: false, default: {} | |
| t.timestamps | |
| t.index :record_type | |
| end | |
| class Stowaway::Record < ActiveRecord::Base | |
| def self.preserve(record) | |
| create! record_type: record.class, record_attributes: record.attributes |
Official website: https://2023.euruko.org
Agenda: https://2023.euruko.org/agenda
Place: Vilnius, Vilnius Gediminas Technical University, 🗺️ → https://2023.euruko.org/map
