Yea I tried, same issue
Yea I tried, same issue
so don’t ever send anything you don’t absolutely have to.
Hmm I was thinking that after I’ve establish a base and was going to optimize, I think that setting the multiplayer nodes to be manually updated should be ok rather than having them done periodically, since a card game game state progress at fixed events rather than being real time.
but I generally personally prefer modifier parent nodes because the tree is very efficient and it seems to allow for more flexibility.
One downside with nodes that I noticed is that if we store the cards in the deck as nodes under a deck node, it becomes rather annoying to manipulate them, eg shuffle them, as compared to list. Would that be enough a drawback to reconsider using a list instead?
Or, maybe just tell them the JWT they’ve got is expired, and ask them yes or no if they want the new (current) price instead, and update it transparently if they say yes.
Based on this, it seems like you’re suggesting to move the logic closer to the frontend and leave the auto-refetching logic out of the backend?
The more I look at the responses, the more I feel this is a front-end problem to be solved rather than the backend’s.
I think the idea was that if they managed to get the private key, we have away bigger problems on our hands than them submitting fraudulent orders. Even with server-side tokens, the same could happen if someone get access to your machine.
Actually, we are controlling both ends. But the issue is that frontend have rather limited bandwidth most of the time (sadly the truth is that despite that your own team wants to make things clean, other teams may not have the same stance).
I think the idea was that as long as it is within 5 min, our service can be certain that the price shouldn’t change and thus we can save the computation cost of having to compute the price.
It also is a user requirement, cause within that 5 min, even if the price is supposed to be changed, we will still use the price in the JWT.
What are the alternatives to a JWT. I know it is a bit bloated and we could just use the HS256 signature itself, but that doesn’t really change the core problem of expiry vs auto-refetch
Oh, ticks are rare in my region, that’s why I have no prior experience with them.
I was thinking in the context of us slapping the mosquito would be equivalent to slamming a thumbtack into your skin which could increase the damage dealt and penetration depth.
Oh, I didn’t knew you can pass 2 i
s. I was depending on the tab completion from pacman
, but I didn’t see that it says you could specify i
’s
Ah, it worked. I thought Qi
only works for packages that are already installed.
Didn’t knew it worked for things that are synced as a new dependency of a package
ok, here you go https://pastebin.com/uPc5S1LU
Tried the settings on the GitHub, doesn’t seem to work, and it also made the stuttering worse
opengl-pbo=yes
opengl-early-flush=no.
video-sync=display-resample
ok, here you go
Yea, it seems to be using 200% CPU.
But I have vo=gpu
though, so I’d thought the GPU would’ve taken some of the load.
If I am strapped for CPU resources, how do I make it so that MPV buffer or something instead of dropping the audio when this happens? Cause it is strange the even though the visuals are acceptable, it is the audio that fails before the video
are you running it from a tty on login
Yea, directly on tty
.
I imagine these are two separate issues.
I’d think they are related since mpv
is working fine on Xwayland
but not when I launch alacritty
instead
Can you dump your installed packages with pacman -Qe and post it here? I’ll compare it to mine.
alacritty 0.12.2-1
ani-cli 4.6-1
archlinuxarm-keyring 20140119-2
base 3-1
base-devel 1-1
bat 0.23.0-3
cage 0.1.5-1
dhcpcd 10.0.2-1
dialog 1:1.3_20230209-1
linux-rpi 6.1.54-1
lobster 4.0.0-1
man-db 2.11.2-1
neovim 0.9.1-1
net-tools 2.10-2
netctl 1.28-2
noto-fonts 1:23.9.1-1
opendoas 6.8.2-1
openssh 9.4p1-4
pacman-contrib 1.9.1-1
raspberrypi-bootloader 20230921-1
raspberrypi-firmware 20230921-1
ripgrep 13.0.0-3
socat 1.7.4.4-1
tmux 3.3_a-7
vi 1:070224-6
which 2.21-6
wireless-regdb 2023.09.01-1
wireless_tools 30.pre9-3
wpa_supplicant 2:2.10-8
xorg-xwayland 23.2.1-1
That shouldn’t be the problem since I’m using pipewire
and it is working in the Xwayland session.
When I launch into alacritty
, I also checked that pipewire + wireplumber
were both active
I tried with cage + Xwayland
and that works perfectly, so I highly doubt that is the issue.
Maybe it is something to do with cage + alacritty
that is causing it, but I’m not too well versed in the Wayland stuff to know if spawning a terminal application may somehow not support audio.
I would suppose so, cause I used
nmcli d WiFi connect SSID password PASSWORD
, and the PASSWORD is displayed correctly.My password is alphanumeric, so that shouldn’t be the issue. My SSID is alphanumeric +
()
, but I don’t think that’s the issue either cause I cannot connect to my password protected hotspot that is only alphanumeric.