> As far as I know, this is how CSGO runs on vulkan: valve did package the game with the DX(11?12?)->vulkan translater.
CSGO has a builtin DX to OpenGL translation layer. They're not using Proton or DXVK, it's Linux native OpenGL. Hopefuly we get Source 2 and native Vulkan sooner than later ..
As far as I'm aware, the updated versions of Source games made for Steam Deck release are in fact using DXVK instead of their old ToGL. Not sure if that includes CS:GO though.
The topic often comes up. Can't say I share the experience. My servers have never been put on a blacklist in the 7 years they've been running, and one of them operates from my residential DSL connection. Standard postfix+dovecot stack on an Archlinux VPS, I log in once a year to update the packages and make sure there is enough disk space left.
Essentially all residential IPs are blacklisted for email servers, at least on port 25. Many ISPs blackhole any traffic on port 25 to residential IPs. Do you have port 25 working on your residential connection?
Isn’t port 25 used for unencrypted traffic as opposed to port 465? I’m pretty sure I had a working mail server back in 2012 behind an ISP that blocked port 25.
French Brittany, was sunbathing this morning at 10:00 at 15°C on the beach, with bees flying around. These are summer temperatures, and even in summer it's usually colder than that at this time of the day. Felt completely unreal.
Makes sense, and I know a lot of people are like "4K ultra or nada" but I grew up in a world where 480p was watchable and good enough that you would invite friend over and have a freewatch party. So I guess it depends who is watching right?
I tried a couple of screen recording tricks and it appears that Netflix is easily captured on Chrome....
At 6 cents/SMS, I find Twilio and similar services way too expensive. Compare that to the unlimited SMS plan that I can get for 2€/month here in France, and setting up a gateway like that becomes very attractive.
In my experience it's very unstable however. Sending and receiving SMS can take anywhere from 5 to 30 seconds, and the modem can't do both at the same time. I tried configuring gammu's timeouts, loop delays and whatnot, but couldn't get something that's reliable enough for production.
Free's €2 per month is probably one of the best mobile deal in the world :). Beware though, last I checked using their SIM card in something not a mobile phone was against Fred's ToS. I don't know if it have since changed.
Ignoring cost, there's two things preventing me from watching content legally in acceptable quality: DRMs and connection speed.
The day streaming providers allow downloading high quality, DRM free video files to watch for later, I'll happily pay 3 bucks per movie.
As it stands, I can't play anything >720p because of DRMs. If you're willing to prevent paying customers from watching what they're paying for, just for the sake of reassuring your shareholders that you're combatting piracy (though failing miserably), then I have no remorse torrenting your content.
> As it stands, I can't play anything >720p because of DRMs.
Should be able to play 4k via the official Netflix app on Windows, assuming you have the relevant chain of DRM protection (ie. TPM might be required, along with HDCP cables and monitors).
> (though failing miserably),
I'd argue that they're winning, actually - torrenting these days requires some upfront costs (hard drives and a media server) and an initial time investment (dedicate $xx hours to learning and managing a media server + media library software). It's much easier to punch in your credit card to the 3 streaming services you want to use that month.
This is on top of the fact that most media giants contract out a service to automatically send DMCA takedown requests to the ISP of every torrent peer. If you're in the U.S. doing this, you're most likely going to get a letter from your ISP asking you to stop torrenting illegal content. Xfinity in particular has a 3 (or 6?) strike system for DMCAs, after which they'll terminate your service. Any torrenting effectively must be accompanied by a VPN that is torrent-friendly and ignores DMCAs.
Yes, but those are all non problems for anyone remotely tech-savvy. The point is, DRMs are hurting paying customers and do not even make it more difficult for pirates: when you download a torrent, DRMs are already completely stripped, so the only people prevented from consuming DRM'd content are paying customers with non-HDCP compliant hardware. That's insane.
Eh? I'm pretty sure at least 80% of pirates just delete the movie/show from their PC/laptop when they're done watching it, maybe casting it to a TV in the process.
> on Windows, assuming you have the relevant chain of DRM protection (ie. TPM might be required, along with HDCP cables and monitors).
Load of bollocks. The requirements are difficult to figure out and hard to fulfil. The standards in the ecosystem do not help at all either. Cables or monitors shouldn't be certified HDMI-compatible when they don't do HDCP for example.
The "just try and find out, and hope the situation won't change" approach is so customer-hostile I have no sympathy when someone moans about pirates yet again.
What sucks the most about I2C for me is the fact that the bus can get stuck if the master device resets during a transmission. In which case the slave device will keep the SDA line busy while waiting indefinitely for clock pulses. Yes, you can probably send dummy clock pulses to finish the frame and get SDA released, but that's just a pain to code properly.
SPI is so much more reliable with just two extra pins, I usually don't even consider I2C anymore.
Yeah that's pretty disappointing. Gotta implement a "bus clear" feature in any system that relies on I2C working consistently.
Slave devices that rely on clock stretching are a total pain in the ass, as well. Tend not to play nice with other normal devices.
https://www.i2c-bus.org/clock-stretching/
The main thing I use I2C for in recent designs is multiple channels of power monitoring, e.g. using the INA226. I agree that SPI is preferable for sensors that support it.
And I'm currently working with the INA229, its SPI cousin I guess :) Those chips are really nice, I'm trying to use the alert feature as a configurable overcurrent trip protection, as well as overvoltage device protection.
SPI requires 3 wires plus a Chip Select for each device on the bus. That 30 device network under discussion suddenly needs 33 pins. That's more pins than any processor I've used in the last couple of years.
I mean I guess we could use an i2c GPIO expander to get extra lines. I bet that would be "fun" to get right.
Many MCUs also don't handle SPI well (via DMA) or have bugs in peripherals. So the only viable way is bit banging and that is difficult to make faster than I2C.
I am considering implementing SPI on FPGA to connect with devices and then transmit to/from MCU using "SPI" dialect that works with that MCU.
What kind of issues have you found with SPI peripherals? I've rarely found issues with SPI, certainly it's a peripheral which is far less buggy on average than I2C, where there are some absolutely awful implementations.
You can use a demultiplexer to turn e.g. 4 pins into 16 chip select. But the fact that the number of wires has to grow at all to accomodate additional devices is certainly a big downside compared to I2C, and for wired networks that basically makes it impossible to daisy chain devices.
If you had 30 SPI devices, you'd probably use a small FPGA to address them all (produce all the chip selects as needed). Basically, write an integer (e.g. 5 bits would do for 30 selects) and a strobe and you're good to go. No address conflicts, ever. And very fast.
This can be detected and usually just mux scl to a gpio and cycle until the bus is recovered. The real issue is if a device decides to hold scl low forever. At which point it's recommended to power cycle devices on the bus until it recovers.
SPI is however not useable as a bus. You need a specific chip select pin line for every chip you communicate with. But yes I like SPI much better as well.
I find Wayland is great already for my usage, and has been for the last two years. If Xorg works for you and Wayland doesn't, that's perfectly fine too.
Don't get me wrong - I would love to not deal with certain X warts. (I see substantially fewer warts than other people do, but that's just me.)
It just seems Wayland's combination of technical requirements and political entanglements make it a sort of Zeno's Project, doomed to asymptotically approach peoples' expectations and desires, but never reach them.
Yes, it is active with many recent contributions. The goal was to show how much opportunity is there for making things more optimal from running perspective. Imagine how much of cpu power and electricity wasted
CSGO has a builtin DX to OpenGL translation layer. They're not using Proton or DXVK, it's Linux native OpenGL. Hopefuly we get Source 2 and native Vulkan sooner than later ..