profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Qyriad/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.
Qyriad Qyriad 1BitSquared she (singular) / they (plural) Embedded software engineers

Qyriad/fusee-launcher 1296

A reference implementation launcher for the Fusée Gelée Tegra X1 bootROM exploit

916253/Kurisu-Reswitched 8

[Deprecated] Fork of Kurisu for Reswitched.

Qyriad/dotfiles 4

My own personal dotfiles. MIT license if it ever really matters

Qyriad/hexyl 2

A command-line hex viewer

Qyriad/Facedancer 1

modern FaceDancer core for multiple devices-- including GreatFET

Qyriad/libsigrok 1

Read-only mirror of the official repo at git://sigrok.org/libsigrok. Pull requests welcome. Please file bugreports at sigrok.org/bugzilla.

1bitsquared/blackmagic 0

In application debugger for ARM Cortex microcontrollers.

ktemkin-archive/libgreat-old 0

library for doing Great things

Qyriad/Atmosphere-NX 0

This is a repo for a work-in-progress customized firmware for the Nintendo Switch.

startedBurntSushi/bstr

started time in 14 hours

startedphiresky/ripgrep-all

started time in a day

startednccgroup/Sniffle

started time in 3 days

startedMunifTanjim/tmux-suspend

started time in 4 days

push eventQyriad/Seance

Iris Johnson

commit sha e6378f061d27917ae8b128be5ce2a17bb3869338

Make example service default enable features that are required for proper operation under systemd Additionally default to suggesting the bot be run under a specific user.

view details

Iris Johnson

commit sha 4cc46a03be867b7e71dd6cc01d1305851eec2121

Give clear install instructions for systemd service user

view details

Qyriad

commit sha c9c0d1b6fe6c1c7045ba3ba3d0650751a3e94c84

Merge pull request #1 from modwizcode/systemd-tweak Slight tweaks to suggestion systemd service

view details

push time in 5 days

PR merged Qyriad/Seance

Slight tweaks to suggestion systemd service

Now the default configuration for environment and arguments matches what the bot expects when running under systemd.

Additionally there's now a suggestion (and assumption in the service) that you run it under an unprivileged "seance" user, which is a general best practice. (More tweaks in the future to further lock down the service are probably worth considering since it needs only network access at the moment).

+11 -2

7 comments

2 changed files

modwizcode

pr closed time in 5 days

pull request commentQyriad/Seance

Slight tweaks to suggestion systemd service

Alas, if only global pip installs installed to /usr/local by default; then we wouldn't have any of these problems in the first place.

modwizcode

comment created time in 5 days

pull request commentQyriad/Seance

Slight tweaks to suggestion systemd service

That works~

modwizcode

comment created time in 5 days

startedsoenkehahn/cradle

started time in 5 days

startedpemistahl/grex

started time in 5 days

pull request commentQyriad/Seance

Slight tweaks to suggestion systemd service

Installing globally on Linux tends to lead to some messiness, since it can interfere with the system package manager. On the other hand, it's the preferred approach on macOS. That's why I had plain pip3 install in the readme — with recent versions of pip, it'll suggest --user if you run it without sudo.

You could have it be agnostic in the readme, something like:

Such a user can be created usually with sudo useradd seance, possibly with something like --home-dir=/srv/seance if you want to install Séance with pip3 install --user.

modwizcode

comment created time in 5 days

pull request commentQyriad/Seance

Slight tweaks to suggestion systemd service

The suggested useradd command creates a regular user with the home directory as /home/seance; it might be better to change it to something like useradd --home-dir=/srv/seance, and if you're going to explicitly put running as a special user in the service file, then it should probably also mention that if Séance is installed with pip3 install --user, that that command will need to be run as the Unix user running Séance.

modwizcode

comment created time in 6 days

push eventQyriad/Seance

Mikaela Szekely

commit sha 03e0baf5d08563a3f3c015116576877d772089f1

flushing stdout after writing to stderr is probably not the most helpful

view details

push time in 6 days

PublicEvent

starteddtolnay/bootstrap

started time in 7 days

startedthepowersgang/mrustc

started time in 7 days

startedthepowersgang/mrustc

started time in 7 days

startedbb4242/sdnotify

started time in 8 days

startedrockowitz/ddcutil

started time in 8 days

push eventQyriad/dotfiles

Mikaela Szekely

commit sha 9f395ab03e69f8a024db0ec9e72f31361231c522

xonsh: add `tmuxman` alias

view details

push time in 8 days

startedrust-embedded/not-yet-awesome-embedded-rust

started time in 9 days

startedsixtyfpsui/sixtyfps

started time in 9 days

startednot-yet-awesome-rust/not-yet-awesome-rust

started time in 9 days

issue commentxonsh/xonsh

Running swaymsg sometimes fail in xonsh

I have this issue too with Xonsh in Sway on Archlinux, though curiously it seems like sometimes the swaymsg command actually works, even though it prints that error?

g33kex

comment created time in 9 days

startedjaparic/rust-cross

started time in 16 days

startedc-bata/go-prompt

started time in 18 days

startedwez/EleDo

started time in 19 days

startedservo/font-kit

started time in 19 days

startedmhagger/git-imerge

started time in a month

startedhecrj/iced

started time in a month