profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/l1ving/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
liv l1ving frogg.ie they/them - queer who makes things by breaking them

l1ving/bot-kt 13

Easy to use Kotlin Discord bot framework

l1ving/vasya 12

it's vasya, what more would you want to know

l1ving/fs-over-http 11

A filesystem interface over http, with extras and docker support

technically-functional/heartbeat 9

A service to keep a live heartbeat (ping) on multiple devices

l1ving/discord-invite 6

A CSS recreation of the Discord invite

l1ving/what-commit 6

Generate pseudorandom names for commit. Supports git flags

l1ving/discord-emoji-extractor 4

Extract sent emojis from your Discord messages, and download them

l1ving/srp-go 3

Serve random pictures on a domain, with upload and browse support

l1ving/github-discussion-api 2

Kotlin data classes for Github requests

l1ving/holybible.guru 2

A redirect to archlinux.org

issue commenttechnically-functional/heartbeat

Switch to GH Containers

Another alternative is switching away from Docker entirely, to Kubernetes. As long as the user experience is mostly the same, I do not see an issue with this, and it would be preferable given my complaints with docker (excess image size, lots of required steps to solve the former, pushing consumers towards a subscription model).

l1ving

comment created time in 2 hours

push eventtechnically-functional/heartbeat

lv

commit sha 791103b8a78cd22ad0faf557be639853f1efc69f

fix: Add temporary templates to fix Docker build

view details

push time in 2 hours

issue openedtechnically-functional/heartbeat

Switch to GH Containers

Github has support for storing your Docker images on Github, instead of Docker Hub. The GH Action that we're using currently does not need you to change much to add support for this.

The reasoning behind this is that Docker now only allows 1 personal access token for pushing your containers, and org plans are paid. Given this push to pay for Docker Hub (which enforces poor security practices), it would be better to switch to GH for hosting the images.

  • [ ] Switch Action and Makefile
  • [ ] Update update.sh script

created time in 2 hours

issue openedl1ving/srp-go

Switch to GH Containers

Github has support for storing your Docker images on Github, instead of Docker Hub. The GH Action that we're using currently does not need you to change much to add support for this.

The reasoning behind this is that Docker now only allows 1 personal access token for pushing your containers, and org plans are paid. Given this push to pay for Docker Hub (which enforces poor security practices), it would be better to switch to GH for hosting the images.

  • [ ] Switch Action and Makefile
  • [ ] Update update.sh script

created time in 2 hours

issue openedl1ving/fs-over-http

Switch to GH Containers

Github has support for storing your Docker images on Github, instead of Docker Hub. The GH Action that we're using currently does not need you to change much to add support for this.

The reasoning behind this is that Docker now only allows 1 personal access token for pushing your containers, and org plans are paid. Given this push to pay for Docker Hub (which enforces poor security practices), it would be better to switch to GH for hosting the images.

  • [ ] Switch Action and Makefile
  • [ ] Update update.sh script

created time in 2 hours

push eventtechnically-functional/heartbeat

lv

commit sha 35e079547de3ed7861be77e8cd75dcd36ef842fb

cleanup: Remove unnecessary flags

view details

lv

commit sha d007495809260ab23c08037ca9eb91240a7be352

chore: Update build files to support qtc

view details

push time in 2 hours

push eventl1ving/dotfiles

lv

commit sha 3ad9818844804413d57344b0affce122a0e14225

impr: Make `~/.paths` relative

view details

push time in 3 hours

issue commentbeemdevelopment/Aegis

Android Keystore key invalidated after device unlock on Pixel 4

Are we sure this happens because of the face matching improvement? What if it's caused by a hardware defect? You're the first person to report this issue.

I suppose it's entirely possible that some sort of hardware defect causes it to regenerate the keystore after an unlock instead of properly updating the face data.

Is there anything I can help provide to debug this?

l1ving

comment created time in a day

issue commentsignalapp/Signal-Desktop

Don't delete debian packages on new releases

My local configuration was broken - can confirm that this is now resolved. Thank you for bringing your attention to this issue :)

captn3m0

comment created time in a day

push eventl1ving/dotfiles

lv

commit sha 07ad6d8b012e09483d9ff0ee02db1240df4fa045

impr: Add android sdk paths

view details

push time in a day

startedbenjojo/ssh-key-confirmer

started time in 2 days

startedseemoo-lab/AirGuard

started time in 2 days

push eventtechnically-functional/heartbeat-unix

lv

commit sha 3b687ba912a29749a21a13b7203d3329e1164bc4

fix: curl does not follow links, so use the full link

view details

push time in 2 days

push eventtechnically-functional/heartbeat-unix

lv

commit sha 22ccb16a80acc013d0b07d3f14797011b5a3ae48

docs: Reword warning about dir

view details

push time in 2 days

push eventtechnically-functional/heartbeat-unix

lv

commit sha aa3250b345416c6d3c8b70bbf123c92aa4035446

docs: Fix typo in header title

view details

push time in 2 days

push eventl1ving/dotfiles

lv

commit sha 3357d489f16787c79bff8ef561a1abeadc02b89b

impr: Add `gp` alias

view details

push time in 2 days

push eventtechnically-functional/heartbeat-unix

lv

commit sha 6813f2bb83673c5403c1810634b5b86a9e4602f7

docs: Fix typo in `wget` command

view details

push time in 2 days

push eventtechnically-functional/heartbeat-unix

lv

commit sha cfbb8764034579718ff88c440a2e600f58d17efe

fix: Re-add systemd service files and instructions

view details

push time in 2 days

issue commentsignalapp/Signal-Desktop

Don't delete debian packages on new releases

This issue has not been resolved.

captn3m0

comment created time in 2 days

startedDiscordTauri/discord-tauri

started time in 3 days

issue commentbeemdevelopment/Aegis

Asking for password each time

Are you sure Aegis is showing that message after every single device unlock? To test, could you perform the following steps a couple of times?

I have tried this, and it doesn't happen every single time, but it does happen frequently. It's closer to a 1/3 chance.

This morning, when I wrote the issue, it happened 3 times in a row, so I am guessing the face match "improvement" could rely on certain light conditions or angles, I'm unsure.

Once that key is wiped, the only way to decrypt your vault is with the password, so Aegis has no other option but to ask for that.

I wasn't aware it worked that way, I suppose that complicates things.

l1ving

comment created time in 3 days

issue openedbeemdevelopment/Aegis

Asking for password each time

Info
  • Version: 2.0.2
  • Source: Google Play
  • Vault encrypted: Yes, with password and biometric unlock
  • Device: Pixel 4
  • Android version and ROM: Android 11 stock
Steps to reproduce
  • Unlock phone
  • Open Aegis with biometric (face) unlock
What do you expect to happen?

I do not get asked for my Aegis password

What happens instead?

Aegis "detects a change in biometric security" and asks for my password again.

The Google Pixel 4 (and probably newer Pixels) will "improve" the face matching with each successful device unlock, and so Aegis detects that the biometric security "changed", even though it's still the same face that is saved.

Ideally, being able to detect whether face unlock has been removed entirely and re-added would be a better alternative, but I don't think that's possible through whatever API Android exposes.

As a second proposal, an option to turn off this detection (with a warning of what it means, of course), would be nice to have, as I store my Aegis password on an air-gapped computer and it is inconvenient to not be able to access my 2fa tokens when not at home.

created time in 3 days

push eventtechnically-functional/heartbeat

lv

commit sha c25a51cceb690ee1eec32683db120693d8eae375

chore: fix module link and bump deps

view details

push time in 3 days

push eventtechnically-functional/heartbeat-unix

lv

commit sha e26f93f9a1f40b2942cb8a98cb63a5fe5f9bb287

fix: `heartbeat-linux` -> `heartbeat-unix`

view details

push time in 3 days

push eventtechnically-functional/heartbeat

lv

commit sha 40a20364293e283865fafa983536c928e3578698

fix: `heartbeat-linux` -> `heartbeat-unix`

view details

push time in 3 days

push eventtechnically-functional/heartbeat

lv

commit sha 3aa7a47c74dfd631bd573cb51fbddd0ebff90ce0

docs: Remove first person, cleanup instructions

view details

push time in 3 days

push eventtechnically-functional/heartbeat-linux

lv

commit sha dd3cd6fa96a0583738c263e72a5b6613ed00598f

impr: Make `ping.sh` POSIX compatible

view details

push time in 3 days

push eventtechnically-functional/heartbeat

lv

commit sha 022e40046ffb3dcf98caef8510bc6af7f482ec2b

docs: Add note about `heartbeat-linux`

view details

push time in 3 days

push eventtechnically-functional/heartbeat

lv

commit sha dabf417f853457dc2fa778ac6ef05ddb1f710652

docs: Fix wakatime and docker pull badges

view details

push time in 3 days

push eventtechnically-functional/heartbeat

lv

commit sha abb1fc68be1879a89277a6bed93ca54e6e057b65

cleanup: Remove files that are now in `heartbeat-client`

view details

push time in 3 days