Readit NewsEnshittification happens because to a certain extent, the market demands that firms maximise returns. Companies that don't do this get weeded out.
Climate change is a challenging co-ordination problem because nobody wants to tank their economy more than they have to, there's no real enforcement for "cheats" and even agreeing on an accounting basis is politically fraught. Politicians that don't grant concessions to powerful existing vested interests are less electable.
AI safety is predictably going to be a secondary priority when competition gets tight.
Many literary utopias have non-capitalist systems but usually some sort of circular sharing system (some are outright communist, but others more slow living).
Greed must always be checked by a society. But since Calvinism we've had a dual moral reasoning (was that Charles Taylor or Hegel, can't recall). Through Calvinism capitalism attained the moral good of earning more than you need, to deploy greed for God.
Humans are naturally greedy (natural egoism is not immoral just a biological drive) and our political system should balance that out somehow.
ssh-keygen(1): generate Ed25519 keys by default. Ed25519 public keys
are very convenient due to their small size. Ed25519 keys are
specified in RFC 8709 and OpenSSH has supported them since version 6.5
(January 2014).
Previously, if you didn't specify "-t", you got RSA keys; now you get Ed25519, and if you want RSA you have to ask for it.
NIST's publication of FIPS 186-5 in February (2023) added Ed25519 and Ed448 as approved (? allowed?) algorithms:
* https://csrc.nist.gov/publications/detail/fips/186/5/final
* https://en.wikipedia.org/wiki/EdDSA#Standardization_and_impl...
Partly one of the reasons given for the default switch:
* https://lists.mindrot.org/pipermail/openssh-unix-dev/2023-Se...
Curious to know if/when the OpenSSH folks will add Ed448 (RFC 8709, like Ed25519).
I've taken `fx` back to the drawing board and completely rewritten it from the ground up. Excited to share what's new:
1. *Going Big*: `fx` now gracefully handles even the most massive JSON files.
2. *A New TUI Look*: Dive deep into your data with a revamped terminal interface—now with themes!
3. *Swift Navigation with Dig Fuzzy Search*: Feeling lost in JSON? Just type `.` and navigate with ease.
4. *Powerful Regex Search*: Scan across your entire JSON content with precision.
5. *Elegant Long String Wraps*: No more cut-offs. Your strings wrap beautifully now.
6. *All Things JSON*: Added love for comments, trailing commas, and JSON streams.
Pouring my heart and soul into this rewrite has been a journey to make `fx` faster and more powerful. If you find value in what I've crafted and want to support its future, consider sponsoring on GitHub.
Would love to hear your thoughts and feedback!
I never could get used to jq's syntax so instead I've just been grepping. But this looks to be for jq what htop is to top, which is great for exploring response data.
If you have any interest in recording & want to maintain the part where you stay away from the computer/workbench while you play music, I cannot more strongly recommend a digital 8-track recorder. It's been life-changing for me.
When you import a module, Python executes it. For instance, `def` isn’t syntax that says “hey compiler, this is a function!” It’s a statement that’s executed at runtime to define a function. You can put any code you want at the top level of a module and it’ll get executed when the Python interpreter gets to that line.
This is why people use the `if __name__ == "__main__"` so the majority of people will address it in all their scripts even if they don't know the reason why.
It's a feature not a bug IMO. You can use importing a .py file as a singleton hack. You can also use `refresh` to re-load a module, to clear it of any runtime overrides.
I keep seeing people wanting to build distributed this and distributed that. According to Wikipedia, usenet was already distributed. Why did it die?
Edit: follow-up question, what about freenet? Are they the same thing? Are they different, compatible, implementations of the same protocol? Are they incompatible but share some properties? Etc
Web crawlers indexed online forums too, so you could find the content right away through the same search engine instead of having to search the BBS discussions for hours or post a request on the local BBS and wait (days) for replies. Your technically illiterate aunt could browse the search results for posts containing the recipes she wanted from a number of disparate forums, and choose to read anonymously (and print out) or login and contribute. All you need is an email address.
This accessibility and semi-transparency created a major shift in where you go for content, effectively forcing the tech literate to follow suit as well. It fits in the general trend of democratizing the internet, and IMO was a good thing for tech. (I blame the monetizing and large commercial entities for the current state of fragmentation.)
I still login to a local BBS about once a year to say hello. Although I have a shell account now so I don't need to telnet over the net. It's still very alternative and hacker friendly.