896 karma · joined April 6, 2020
1. The Windows (end-)user base is much larger than Linux (not counting Android), so a Windows exploit enables more potential victims.
2. Windows has been the de-facto corporate OS for a long time, so a Windows exploit offers more high-value targets.
Thank you for this. No more second thoughts about pointing cloud.example.com at our local HPE rack.
I've recently worked with some of D-Links consumer IP cameras, DCS-8302LH and DCS-8000LHV2. They offer an app and optionally cloud storage but they ship with ONVIF support. No web interface afaik, but what I found was that I just needed to start interacting through ONVIF to get going with a local-only setup (this would automatically disconnect the camera from the app as well).
These cameras are some of the cheapest available, but they have been solid.
The article links to their paper 'Petabit-per-second data transmission using a chip-scale microcomb ring resonator source'[1]
> We experimentally demonstrate transmission of 1.84 Pbit s–1 over a 37-core, 7.9-km-long fibre using 223 wavelength channels derived from a single microcomb ring resonator producing a stabilized dark-pulse Kerr frequency comb.
I'm running 165hz + 240hz on Xorg with i3vm or KDE Plasma (kwin). OpenGL compositor with Nvidias drivers. Everything works fine.
I think the philosophy of the capsuleer/ship mechanics is a refreshing one, and there's a cyberpunk feel to being wired up into that hull.
> “two models trained on the same data but with different algorithms will behave much more similarly than two models trained on different data with the same algorithm. That’s because the training data contains the patterns in user behavior that algorithms mine and use when recommending new content.”
Do we know how ‘true’ this statement is? Or how much % an algorithm must deviate to cause a % change in results? What about difference in data? If someone can point to somewhere to read up on this, I'd like to know!
edit: Which I feel is closer to prompt engineering than software engineering.
What I don't get is why Spotify didn't prepare this arrangement in their contracts with their people when they joined the company. Then all cards would be on the table, the contract would be referred to as “the standard type”, less drama.
The idea that a larger corpora == better was quickly established, but I hit a ceiling quite soon on early RPi's.
It was possible to seed a start word for text generation, a Baby prompt we might call it?
Nice feature was being able to make a mini chain (model) of the user input sentence, then merge that statistics into the bots chain. The verbatim record of what had been said was obscured but some words and their relations —the experience— was kept. So I imagined, at least.
* I recommend giving the 'markovify' README a view: https://github.com/jsvine/markovify#basic-usage
edit: LLMs still can't deliver an as convincing display of an Aleister Crowley-persona, but I can barely handle a prompt so we're even.
Edit: Realized arguing for CSS properties defeats my point on plaintext. You are right, plaintext is problematic.
| Type | Host/Name | Value/Points to |
| ----- | ------------- | ------------------------------- |
| CNAME | s1._domainkey | s1._domainkey.example.com |
| CNAME | s2._domainkey | s2._domainkey.example.com |
| TXT | _dmarc | v=DMARC1; p=quarantine; adkim=s |
Even .csv formatted stuff fares OK in plaintext.But I agree with you on context and having data visible right there in the email. It's often the case that people forgo using email as the functional communication technology it is and settles with attachments only and the canned byline.
I want to see full markdown, mermaid and the like in email.
https://rogue.dev/content/media/2023/04/coordinated-html-ima...
2 x 32GiB (SDDR4 3200MHz) can be had for 170€ and probably less than that if doing the research. Took a bit of faith and a lot of impulse decision-making as this device was/is specified for up to 32GiB RAM only - but it went through.
This is precisely the use case I had in mind
*Lenovo 16ACH6H
“The cartel lowered operational costs and worked to standardize the life expectancy of light bulbs at 1,000 hours (down from 2,500 hours)..”
In my solely own opinion:
an ADR documents a strategic choice and ties accountability to it's author. The quality of the document (and the content) should work in their own best interest.
Another kind of documentation could be used to record e.g. details of implementation or describing APIs. The latter is focused on building a knowledge base for co-workers, onboarding or end users. edit: I call them REFs.
edit 2: Filling out superfluous forms which ends up of no use to anyone is a waste of time. Cut back on documentation until people starts asking for more of it.
I meant that I don't agree with your sense of the word 'system', as clearly and obviously referring to software development. Of ourse, if paired up with the words 'development' or 'programming', the association is there.
Still, the following titles reads to me as very different occupations:
- Systems Programmer (low-level, bare metal)
- Systems Engineer, (e.g. aeronautics, robotics, banking, requirements)
- Systems Developer (business domains, processes & people, services)
biases all mine
Everything programmed are systems but not all systems are programmable