Bart de Water

This also seems to mess up copying gems from a remote Ruby SDK in RubyMine.

I'm having the same problem. I've tried to add a UIBarButtonItem to the navigation bar like this: ``` UIBarButtonItem *barButtonItem = [[UIBarButtonItem alloc] initWithBarButtonSystemItem:UIBarButtonSystemItemAdd target:self action:nil]; [barButtonItem setStyle:UIBarButtonItemStyleBordered]; [barButtonItem setNuiClass:@"BarButton"];...

This will also require https://github.com/ruby/openssl/pull/119 to expose the required OpenSSL APIs in Ruby or an extra gem like https://github.com/RubyCrypto/ed25519 To my knowledge no manufacturer is supporting this at the time...

I stand corrected, Yubikeys have started shipping with EdDSA support around that time: https://www.yubico.com/blog/whats-new-in-yubikey-firmware-5-2-3/ I started poking at this in https://github.com/cedarcode/cose-ruby/pull/55 but we'll need some work in the OpenSSL gem...

I believe this is caused by the filename in your app as you mentioned. Zeitwerk is used to (re)load your Rails app code, not gems. From https://guides.rubyonrails.org/v7.0/autoloading_and_reloading_constants.html: > Idiomatic Rails...

@excpt I'd appreciate any feedback you'd have 🙂

I think updating once per day might not be precise enough to determine whether a session was recently active or not. How about writing an update if the last_seen_at field...

> Conditionally updating based on "last_seen_at" means that on each request you are adding one SELECT query as well as a potential UPDATE query. I am not sure I understand...

Tracking last_seen_at once per day would not provide enough information for the smart device and IoT use cases mentioned in this issue IMO. I'd very much like precision down to...

I recently came across [WeTransfer's measurometer](https://github.com/WeTransfer/measurometer) via one of their other gems which seems close to @Senjai's idea.