129 karma · joined December 15, 2011
Searching within file contents seems to lack good options right now. Historically you had X1 desktop search, Google had a desktop search product, I think copernic. But most seem to be out of date.
Is ZSA's build known to have latency issues compared to QMK?
(I get mine from nootropics depot) -300mcg
https://slatestarcodex.com/2018/07/10/melatonin-much-more-th...
First request would be a way to sync settings across multiple machines, or at least a way to import/export configs.
I did get hit with the issue about having incoming connections blocked by default - realized RDP connections were blocked even from the local subnet, and had to go plug a physical monitor in.
I was a bit surprised I couldn't figure out a clean way to allow inbound connections from the local network, but not from the internet. The docs at https://docs.safing.io/portmaster/settings seem to imply that I can set various settings to different tiers - 7 for trusted, for untrusted, 4 for hacked, but even when I have the developer view tuned on, I just see a binary choice.
Also you can build some small but high powered machines. I've got a mini ATX build with a 12900 ks, and a 3090. Fits in a carry-on, way faster than any laptop.
Also if you're spending that long in each location, it might be viable to just buy monitors at your location, especially if you think of it as the cost for enhanced productivity.
I'm in a similar situation so I've tried to build as capable of the travel setup as possible.
You can also throw desktop monitors in a checked bag, I'm usually only bringing one, but you can fit two to three.
It really depends on how frequently you travel, if you're going to the same locations, if you can store stuff there, and how much additional cost are you willing to pay for a better set up.
The luggage shipping services out there can be fairly reasonable, if you don't want to lug that much gear back and forth with you. Do you have a home base that you go back to, or are you jumping between locations? I used to be fully nomadic, I spent a lot of time optimizing.
Also what would happen if I installed a Windows gateway, using routing and remote access services, and then installed portmaster on that?
Overall this looks pretty awesome, and I'm excited to try it out.
Oh and can I use this in conjunction with wire guard? How does it play with other vpns.
I just realized part of it is not knowing how to vet them, part is figuring out how to find availability for a psych, and then part is me not wanting to call in to set up my initial appointment.
Yes I know I can set up calendar alerts, but odds are I screwed that up somehow, and a call will get through.
Bonus points for telling me not to feel bad and stress too much if I'm late. If it's an hour appointment and I joined 30 minutes in, that should be okay. Yeah I've lost the unused time, but otherwise that would reduce my stress.
Also I'd rather have a change under 24 hours, be accommodated (if it's possible on your end )without an extra charge.
I can definitely see myself the day before "going wait can we move our 3:00 to 5:00 instead? And if that's not possible I may just want to keep 3:00, but if it works for everyone I'd rather have 5pm"
From my 12900ks (its a boosted 12900k) Core 6-7 is rated for 5.5ghz.
Freq MHz DTS C VID mv PC Eff Fr UCcode 0x1f VR Volt Limit 2500 ---------------------------------------------------- 800 24 1307 52 517 Uncore 3600 IA AC LL 0.5999 800 20 1282 52 47 Power 23.465 IA DC LL 1.0996 800 20 1314 52 70 Current Limit 0.0000 SA AC LL 0.0000 800 20 1308 52 69 iccmax 1023 SA DC LL 0.0000 800 20 1303 52 88 PL1 32760 iccmax dis True 800 18 1293 52 69 PL2 32760 TAU 33 800 20 1286 55 39 Memory 5200 PPP_OVR True 800 22 730 55 37 EE_Turbo_Dis True RTH_Dis True 800 22 1377 40 60 Dis_Ring_EE False HWGuidedSch True 800 22 1172 40 73 IA_CEP_Dis True Dynamic_Mem True Full_Range_Multi False SA_Freq_OVR False TSC_Dis_HW False Banding_Ratio 0 PVD_Ratio_thresh 0 SA_CEP_Dis True FLL OC Mode 3
---------------------------------------------------------------------------------------------------------------------------------
Core Voltage Adapt 0 Ring Voltage Adapt 0 Core PLL V 900 Core Voltage Offset 0 Ring Voltage Offset 0 Ring PLL V 900 L2 Voltage Adapt 0 L2 Voltage Offset 0 AVX512 Offset 0 SA Voltage Offset 0 Ring VID 0 MC PLL V 900 AVX Offset 0 AVX2 V Guardband 0 AVX512 V Guardband 0 SA Voltage Manual 1150
---------------------------------------------------------------------------------------------------------------------------------
Turbo Ratio Limit 55, 55, 52, 52, 52, 52, 52, 52 Core OCMB Max Ratio 0 Ring Min Ratio 8 Turbo Limit Cores 1, 2, 3, 4, 5, 6, 7, 8 Ring OCMB Max Ratio 0 Ring Max Ratio 47 Atom Ratio Limit 40, 40, 40, 40, 40, 40, 40, 40 Atom Limit Cores 255, 255, 255, 255, 255, 255, 255, 255Atom OCMB Max Ratio 0 OS Max Ratio 34 HWP Min Ratio 43 HWP Max Ratio 255 Max Possible Core 40 Max Possible Ring 47 UCLK 2600
Num cores: 24 Using RDTSC to measure time: false Num round trips per samples: 5000 Num samples: 300 Showing latency=round-trip-time/2 in nanoseconds:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
0
1 0±0
2 37±6 36±6
3 31±6 37±6 5±5
4 26±6 26±6 26±6 26±6
5 26±6 31±6 26±6 31±6 5±5
6 31±6 31±6 36±6 31±6 26±6 21±6
7 31±6 31±6 31±6 31±6 26±6 26±6 5±5
8 31±6 31±6 31±6 31±6 26±6 26±6 31±6 26±6
9 36±6 31±6 31±6 31±6 26±6 26±6 26±6 26±6 5±5
10 31±6 36±6 31±6 26±6 26±6 21±6 26±6 31±6 26±6 31±6
11 31±6 36±6 31±6 36±6 26±6 26±6 31±6 31±6 36±6 31±6 5±5
12 31±6 36±6 31±6 42±6 26±6 31±6 31±6 37±6 31±6 37±6 31±6 36±6
13 36±6 37±6 42±6 36±6 26±6 26±6 31±6 31±6 31±6 31±6 31±6 31±6 5±5
14 31±6 36±6 37±6 36±6 31±6 26±6 36±6 31±6 36±6 31±6 36±6 31±6 31±6 36±6
15 31±6 31±6 31±6 31±6 26±6 26±6 36±6 31±6 31±6 31±6 31±6 31±6 31±6 31±6 0±0
16 42±6 42±6 42±6 42±6 31±6 31±6 37±6 36±6 36±6 42±6 37±6 36±6 36±6 36±6 37±6 37±6
17 42±6 42±6 36±6 42±6 31±6 36±6 37±6 36±6 36±6 37±6 36±6 37±6 36±6 36±6 36±6 37±6 47±6
18 42±6 42±6 42±6 42±6 31±6 31±6 37±6 36±6 37±6 36±6 42±6 36±6 37±6 36±6 36±6 36±6 47±6 52±6
19 42±6 42±6 42±6 37±6 31±6 31±6 36±6 37±6 36±6 36±6 37±6 37±6 36±6 36±6 42±6 37±6 52±6 47±6 47±6
20 42±6 42±6 42±6 36±6 37±6 31±6 37±6 36±6 37±6 36±6 36±6 42±6 37±6 36±6 36±6 42±6 42±6 42±6 42±6 42±6
21 42±6 37±6 42±6 42±6 31±6 31±6 37±6 36±6 42±6 36±6 37±6 36±6 37±6 37±6 36±6 36±6 42±6 42±6 42±6 42±6 47±6
22 42±6 42±6 42±6 36±6 36±6 31±6 36±6 37±6 36±6 37±6 36±6 36±6 36±6 37±6 36±6 42±6 42±6 42±6 42±6 42±6 47±6 52±6
23 36±6 42±6 42±6 42±6 31±6 31±6 37±6 36±6 37±6 42±6 36±6 36±6 37±6 42±6 36±6 36±6 42±6 42±6 42±6 42±6 52±6 47±6 47±6
Min latency: 0.0ns ±0.0 cores: (1,0)
Max latency: 52.3ns ±16.3 cores: (23,20)
Mean latency: 34.6nsI personally do this all the time. At most you get an extra restart the first time the drive is in a new set of hardware and after that you're good to go.
My main Windows install is probably 8 years old at this point, it's gone between multiple motherboards.
The biggest annoyance is a few pieces of software that tie activation to the motherboard.
If you want to make it even more portable you can install Windows to a vmdk.
And if you want to get a special complicated, you can have that vmdk act as essentially a secondary variant of your main operating system complete with symlinking most of the files and application info, to both save space and so you have most of the same state across both os's, but still can play around and easily roll back any changes.
I found it to be some of the most fun ctfs I played, partially because it was extremely time-bound. Rounds were 20 to 30 minutes each. It meant that you still had the rest of your conference time for other activities, rather than taking over your entire weekend.
If you want to get super crazy, I'll boot a second copy of Windows off of a vhdx file that's stripped down if I want extra performance.
With a little bit of work you can even clone the sid of your main os, and symlink most of your existing files and info, so it's almost identical to your main OS.
Calyp.to's guide is one of the best I've seen for stripping windows down to reduce latency.
https://docs.google.com/document/u/0/d/1c2-lUJq74wuYK1WrA_bI...