You can set Firefish and Misskey to use fewer workers. It can work with as little as one, for maximum RAM savings.
You can set Firefish and Misskey to use fewer workers. It can work with as little as one, for maximum RAM savings.
If I’m not able to self-host it a la VS Codium, then it’s very much a honeypot.
I mean, not even I knew that Ethereum could be run in an intranet via Proof of Authority, today I learned something new!
Fair enough that! I’m surprised to see so few companies saving up their money and processing time, and just using a private distributed ledger among all parties (plus maybe an arbiter node or two). Probably because Ethereum is better supported commercially (guess why!)
Blockchains are only useful in cases where non-repudiability (the ability to prevent users from denying that an event happened) is more important than any other factor. And there are preciously few cases where this is the case, the vast majority being related to audit - tracking receipts, votes, certificates, or similar attestations in an environment where no single party can be trusted. Disclaimer, I’ve worked in the past in projects related to the aforementioned - fortunately all of them related to the field of audit.
Thanks for the TLDW - I could ogle a bit of the article but since I was at work, I couldn’t just play the video out loud.
Fair enough, but at least there should be a way for OverflowAI to list which contributors had the strongest link to the given answer, right?
Stack Overflow is unique as a page, in the sense that its contributions are under a license that allows for reuse (Creative Commons Share-Alike) as long as the individual users are properly credited. Does this mean that OverflowAI keeps the credit metadata and knows who wrote each individual part of an answer?
See, this is what happens when we let a single provider monopolize the development of web engines - one party can essentially impose the standards, as it can be clearly seen here.
I’m impressed with what developers could do with what amounted to an electrical typewriter on a budget (down to the color limitations being based on the device being text-first). Kind of what happens when a cheap, mass-produced, simplified version of a technology finally lands in the hands of a lot of people. A bit sad that nothing of the sort seemed to happen with the Raspberry Pi…
Sure, this is the configuration file used by Firefish: https://github.com/misskey-dev/misskey/blob/develop/.config/example.yml
Generally it’s stored in
/var/www/firefish/.config/default.yml
and you want to change these lines:clusterLimit: 1 deliverJobConcurrency: 64 inboxJobConcurrency: 8
That way the system will use a single thread and process fewer inbox / outbox requests in parallel. This of course may impact performance, but for a single-user server it will work well enough.