I had added that key as a plain fido security key and it didn't let me add it as a passkey. So, I removed that key from the list of security keys and added it as a passkey.
136 karma · joined September 8, 2017
I had added that key as a plain fido security key and it didn't let me add it as a passkey. So, I removed that key from the list of security keys and added it as a passkey.
They perform quite well even in direct sunlight(47C temperature) and rain. Low light performance is not super great but I can't blame the camera for that.
The only thing missing is the lack of IPv6. I like everything else about it. I have the 510A, 810A and duo 2 poe
https://paste.debian.net/plain/1282885 (Zoom out a bit to see it properly)
I also created a few measurements on RIPE Atlas.
Ping from all probes in India to api.fastmail.com: https://atlas.ripe.net/measurements/55469007/
Traceroute from all probes in India to api.fastmail.com: https://atlas.ripe.net/measurements/55469042/
Fastmail's clients are mostly online only and dont cache much information.
It takes ~5-10 seconds to go from clicking on a notification to actually being able to read anything. It's really not a good experience.
That's not the point of discussion. I didn't say Gitlab doesn't lie about it or heck, That it doesn't have worse uptime than Github.
My argument is that a company erasing 300GB production database once is not a stain on their competency and that it can not be compared to a company which has very frequent outages which also happens to lie when they have outages.
I don't see how the two situations are comparable
This is so obvious in my head. I can't think of a single good reason where a SFN makes sense here.
Same thing also happened few months back.
It feels like they do this manually and it's only done when enough people are effected.
I came across this post which presents an example using rust's transmute and it's incorrect behavior when the alignment is different. https://andrewkelley.me/post/unsafe-zig-safer-than-unsafe-ru...
Is this issue still present? I tried to figure it out the other day using latest rust's nightly but the llvm ir output has so much going on that I didn't _really_ understand what was going on
I knew fastmail was building JMAP but I didn't think to look at JMAP when I was trying to find fastmail's API that can be used to integrate this in other services. This is really nice compared to the SOAP/XML monstrosity I stumbled upon, heh.
2. Terrible, Inconsistent UI.
3. Push notifications are broken and Their apps are broken. I dont get notifications in clients configured with IMAP and their apps also dont send notifications. I have to manually refresh in both cases.
4. Relatively minor issue but I am against Zoho's founder's political alignment, and that is putting this issue mildly.
I have been trying to move away from Zoho. I tried protonmail for the last month but it's not for me. E2E is great but the loss in functionality is a bit much.
I switched to fastmail today but I have ran into some issues there as well[1] and so far I have seen a lot of recent reddit posts criticizing the extremely slow response time(2+ days) in support tickets. So, now I am not sure if fastmail is a good option.
Migadu has been recommended to me in the past, maybe I should try that out
[1] https://reddit.com/r/fastmail/comments/m4rj0g/_/h3tq036/?con...
I have been trying to figure out the filter whoever created the channel is using but no close to figuring it out. :(
It would be really awesome if people can share a filter they believe works better. :) I am trying to reduce the number of meh quality posts from HN in my freshrss(rss.ishanjain.me) instance.
I made 4 changes in Rust version.
1. Moved up the line that gets a value from cache[j+1] before any calls are made to cache[j]. This removes 1 bound check. (Improvement from 182,747ns down to 176,xyzns +-4800)
2. Moved from .chars().enumerate() to .as_bytes() and manually tracking current position with i/j variables. (Improvement from 176,xyz ns down to 140,xyz ns)
3. Moved to the standard benchmark suite from main + handrolled benchmark system.(File read + load + parse into lines was kept out of benchmark)
4. Replaced hand rolled min with std::cmp::min. (improvement from 140,xyz down to 139,xyz but the std deviation was about the same. So Could just be a fluke. Don't know)
In Go version, I made three changes.
1. Doing the same thing from #1 in Rust actually increased the runtime from 190,xyz to 232,xyz and quite consistently too. I ran it 10+ times to confirm)
2. Replaced []rune(source), []rune(target) to []byte(source), []byte(target). (Improvement from 214817ns to 190152 ns)
3. Replaced hand rolled bench mark system with a proper bench mark system in Go. (Again, File read + load + parse into lines was kept out of benchmark)
So, At the end of it, Rust version was about 50k ns faster than Go version.
Edit #1:
In rust version, I had also replaced the cache initialization to (0..=target.len()).collect() before doing anything els.. This also gave a good perf boost but I forgot to note down the exact value.