Did anybody ever play with the parallela manycore boards?
You can buy 16 core (+2 normie cores) boards pretty cheap.
They had 64 core boards for sale at one point, and they developed 1024 core board too, but I don't think it ever went on sale.
This page on VM side channel attack mitigations is scary: https://github.com/firecracker-microvm/firecracker/blob/master/docs/prod-host-setup.md
Using the Linux KVM API seems easy enough, but we have all this hidden danger now.
@bixmediocre @fraying I used to live a couple of blocks away from freight train tracks that happened to be a stopping point for them, and it was slightly downhill to boot. The result was a 30 minute long opera of gently squealing brakes at ever decreasing pitch, each wheel slightly different from the next. It was the most beautifully haunting thing to listen to at night. It's been 20 years and I still miss it.
Imma make this clear: I'm not building software for developers.
I'm working to building tools for people.
You shouldn't have to know to maintain and secure a server to have your own independent identity online. You shouldn't need to know what libsodium or similar library to be secure online.
That's my objective.
@jalcine Oh my gosh, can you make every open source developer like this? The unusable nature of OSS drives me nuts.
It's terrible that most isps prohibits residential customers from hosting servers. The result is that it's really difficult to sell host stuff legally without getting your service shutdown. There's always that you have to pay a few bucks a month for a VPS when you could just take an old computer hook it up to your home network and that would be fine for a low traffic applications, like most Mastodon servers
Interesting perspective comparing Usenet clients to modern social media clients by @gcupc
Clearly modern clients are designed to suck users in with simplicity. Not clear why they don't give power users more tools. Even here on Mastodon. I'd love for my timeline to grey out the toots I've already read, across clients of course.
“Some thoughts on Social Networking and Usenet”
This reminds me, I should finish writing that “apps that should exist but don’t” blog post. A best practices social media consumption app is one of them.
"Big Tech's problem is Big, not Tech" by Cory Doctorow (video) https://archive.org/details/decentralizedwebsummitmedia-2018-courtyard-2?start=509
I missed this when it came out a few months ago, but this is a great talk. I'm becoming more and more convinced that the problems of technology centralization can't be solved without antitrust. Tim Wu's recent book "The Curse of Bigness" also comes to mind here.
Brutal to see this article on HN. I was an engineer at XCOR 2003/4 and it was a great place to work.
I remember the day they decided to take upfront $ for tickets: they had been against it as a matter of principle, but funds were too tight. I recall thinking "wait, I thought we didn't do that"
This article is like the worst possible obit we could have imagined on that day.
Lesson: don't abandon your principles.
This might well be the creepiest #Google page ever: All the purchases a user has ever done. If the user receives a confirmation email for a purchase they made, the user is not notified that Google collected and displays this piece of information in this page. There is no explanation why they are collecting all the purchases in one page, and apparently there is no way to opt out of this or even delete the purchases from the list.
- A simple text-only page would render to the screen using only a small amount of RAM, because all the other stuff need not be present at all, anywhere.
- typical documents would leverage widely-used (and hence lcally-cached) modules, while heavy applications would ship their own WASM modules, such that you do not need for the platform to do everything for everybody.
- Imagine the convenience of Electron but without installing an application, and with reasonable RAM usage.
The problem we have now is we have high-level standards and APIS that try to respond to every need possible, and the result is it's all very bloated and you end up with Chromium-rules-all kind of situation.
If we had lower-level APIs and plug-ins to bridge the gap between the low-level stuff and the higher level page language, we would be able to innovate faster, and be more responsive to user needs.
WASM makes this possible (maybe).
I got this wacky idea during a sleepless night that the web platform should not be a platform at all, it should be more like a shell.
So instead of having web browsers baked with all the tech of the platform, it should just be a small utility that offers low-level APIs for painting on the screen, showing text, emitting sounds, etc... and the ability to load WASM modules that can leverage these APIs.
"web pages" specify the WASM module they want to use and provide the data for them.
Seeking refuge in a distributed world. Web, future programming. Building things.
One of the first Mastodon instances, there is no specific topic we're into, just enjoy your time!