Imagine Parker Schnabel borrowing one of these for a season, that’d be something.
Readit Newsdimman commented on Overburden Conveyor Bridge F60 en.wikipedia.org/wiki/Ove... · Posted by u/fahrradflucht
Have you looked at the documentation or are you just guessing? When you realize how impenetrable OpenSSL or any TLS lib documentation looks to people untrained in cryptography, you would gain a new appreciation for Git man pages!
Kind of makes you think that the subject at hand is quite complex in its nature, thus untrained people might do best to steer away until properly trained.
dimman commented on In 2019 RX470 were $70, RX580 $100 postadio.com/PC_Master_Ra... · Posted by u/albxxdx
Are there any reliability issues with used mining cards?
AFAIK most miners undervolted their cards to maximise profitability vs. power/cooling requirements. Would applying new thermal paste + replacing fans on the cooler be enough?
Not necessarily more than any other card. As long as it's been running within component specs (especially temperatures), I wouldn't be worried.
It's obviously been running fine under high loads, so why would it just decide to stop working fine?
I think the major issue is that many cards have been running outside of specs for a long time. High loads tends to increase the risk of that, so the problem lies in figuring out the case for the card you're interested in.
As someone who used this feature every single day, for every single text input on the phone: I 100% agree.
The replacement method works, but it is indeed subpar. It annoys me that my 3 generation newer phone is a downgrade in this regard, but I can live with it.
dimman commented on What they don't teach you about sockets macoy.me/blog/programming... · Posted by u/zdw
I definitely used to think TCP was more “high-level” than it actually is. Yes it does much more than UDP but still, its job is to get a sequence of bytes from A to B. You can tune it for higher throughput or more sensitive flow control but anything concerning message passing, request/response, … is beyond the scope of TCP.
Sure, but from a "high level" or "sockets" perspective, especially as a beginner it shouldn't be something you need to care about. A bit simplified, the basic stuff you need to know is:
1) UDP uses packages/messages which may or may not reach its destination. If it reaches its destination the data is intact. Normally connectionless.
2) TCP is a stream protocol. There is no package/message boundary unless you create it yourself (my tip is to do a simple binary TLV (type length value) protocol using say a fixed 4 byte header). Requires a connection to be setup first.
3) Network byte order - really important to read about.
4) Nagles algorithm (TCP_NODELAY) and SO_KEEPALIVE - those are a couple of things to read about.
5) Start with the simple select() approach to handle the socket activity.
You can then go ahead and get more advanced by doing nonblocking I/O or do blocking I/O with each client in its own thread, figuring out pros and cons for your use case. You can add SSL/TLS on top of your TCP connection etc.
EDIT: The SO_KEEPALIVE part is perhaps least important thing to start reading about. I'm a bit biased due to NAT traversal problems as I wrote a secure remote access solution for a major company several years back, utilising STUN/TURN servers, public key authentication (basically certificate pinning), TLS etc.
dimman commented on What they don't teach you about sockets macoy.me/blog/programming... · Posted by u/zdw
Interesting read. I’m quite curious of where all the initial misperceptions about sockets comes from.
I can highly recommend Beej’s guide to network programming: https://beej.us/guide/bgnet/
That together with Linux/BSD man pages should be everything needed, some great documentation there.
dimman commented on Deprecation of OpenGL and OpenCL (2018) developer.apple.com/docum... · Posted by u/ddtaylor
OpenGL can't be deprecated, just like IPv4 or HTTP.
That combined with the fact that VAO that came in version 3 is the last feature makes all threats to force you to update weak at best.
As hardware peaks you can stop worrying about new things and write software that never goes bad.
The wheel has not been rediscovered for a long time. Focus on the vehicle instead = bike.
I think there's a confusion of terms, there's a big difference between 'deprecated' and 'obsolete'. They sure can be deprecated, which can be read as "not recommended for use and _may_ be removed in a future release", but that doesn't mean it has been removed/made obsolete.
Thanks. Nit-picking here but ground is usually abbreviated GND, not GRD.
So DX12 support has not been deprecated in newer drivers (as the page states), it has actually been completely removed.
As for the SPI flash size: they are almost always given in Mbit, so 16Mbit is 2MB hence the confusion if I were to guess. You would be looking for a 128Mbit one to get 16MB.
Nice work and keep on tinkering!