Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Patrick (patrickoftheg@mastodon.social)'s status on Saturday, 24-Aug-2024 05:32:51 JST Patrick

   I don't know why I need to tell you this: If all your candidates are pro ethnic cleansing, or at least pro the money ethnic cleansing will bring, and so you choose a candidate that is less bad when it comes to other subjects?

   Your democracy is a failure.

   In a better world you would be voting from the rooftops at that point. You would be praying for a disease to wipe clean the whole political class.

   You don't live in a civilized world though. You live in one where Kissinger died of old age.

2. Embed this notice
   Futurist Jim Carroll (jimcarroll@futurist.info)'s status on Wednesday, 22-May-2024 19:19:09 JST Futurist Jim Carroll

   Daily Inspiration: "A Gentle Reminder: One person's concept of success is another person's idea of failure" - Futurist Jim Carroll

   A few days ago, I finished the book "After Steve: How Apple Became a Trillion-Dollar Company and Lost Its Soul."

   It was a good read, and so after I was done, I went to Amazon to find another book about Apple or Steve Jobs. The algorithm threw me a book titled "Tim Cook: The Genius Who Took Apple to the Next Level."
   So let me get this straight: according to one book, Apple in the post-Steve Jobs era has been a failure, 'losing its soul,' while at the same time, Tim Cook is a business genius.

   Got it.

   This got me thinking though - how can a company or an individual at the same time be a failure and success?

   In essence, one person's success is another person's failure.

   In the case of Apple, both can be true. The book I read emphasized that while Tim Cook is a genius at maximizing the operations of Apple, becoming an efficient streamlined superpower, the company saw few great product innovations under his reign. Notably, only AirPods and the Apple Watch emerged as entirely new product lines, and so from that viewpoint, it was a product innovation failure. At the same time, he masterminded issues related to supply chain, production, manufacturing, and more, leading it to become an efficiency powerhouse. Failure and success wrapped up in one!

   The fact is, this conundrum of different viewpoints is important to your personal development. That's why you should never obsess over how others might think you are doing - what matters is how YOU think you are doing. What doesn't matter is the judgment of others - what matters is your judgment of yourself.

   The definitions of success and failure are often very different, and so this should guide you in the value you place on those assessments by anyone other than yourself!

   Original post: https://jimcarroll.com/2024/05/daily-inspiration-measuring-success-a-gentle-reminder-one-persons-concept-of-success-is-another-persons-idea-of-failure/

3. Embed this notice
   NEETzsche (neetzsche@iddqd.social)'s status on Thursday, 29-Feb-2024 17:37:58 JST NEETzsche

   >Before the server died, if I had an hour to kill before lunch and didn't wanna do anything too heavy, I could go play with the monitoring scripts or ask Postgres what the long-running queries were and see if I couldn't tweak it to make the DB run smoother

   I did this except with forensics. One thing I think is (mostly) a flaw with Pleroma's implementation is that Lain used Postgres like a document store in the objects and activities tables. It's great for doing things like generating top ten lists from scrobbles but my gut tells me that actually processing the ActivityPub objects/activities into third normal form tables would have made the program might lighter on system resources.

   >see if I couldn't get the 5xx rate down

   I have some hilarious hacks going on on this instance to keep it from shitting the bed. Every few days, Pleroma used to peg the CPU at 100% and stay there in perpetuity until restarted, so I wrote a script that checks if the CPU is at 85% or higher, and if it is for five runs in a row, it restarts Pleroma. I ran this in a cron job every minute lol

   >Well, to be fair, I can see url field looking way too much like the url field in AP objects, and the Audio type having something like that around, and externalLink fits a little better.

   The url field in AP objects is not really defined at all. You can put basically anything you want in there and it's valid AP. Audio objects can be an MP3 file or a page that's about the track, as explicitly listed examples in the AP Vocabulary document lol. That's why I maintain that externalLink is stupid. It's pointless. url is for whatever you want it to be, as long as it's a URL that's somewhat on topic, and if it's not, this is user error. I did ultimately acquiesce to this externalLink desire. but I didn't like

   >Bunch of stuff about Alex Gleason being a shitbird

   I used to really like Alex, and in some ways I still do. He can be a lot of fun. He's a subscriber to the zine. That being said, he does have a habit of being a bit of a drama llama, although I can't really cast stones in this respect, and in a lot of ways I am full of regret for my contribution to e-drama in the last few years. I kind of want to dip my toes into technical FOSS discussions again but if I do I'll likely start my own shit from scratch specifically so that I don't have to clear every little thing with a PR process. I know you like this process and respect it, but if you disagree with the project maintainers about what the project should fundamentally be about in the first place? It's a recipe for failure.

   In the context of fedi, I want to try new things, experiment, create new features, and treat AP like the free-for-all pseudo-protocol it is, which should explain why I did shit like rice out my instance's FE with randomly-generated /mu/ playlists with WebAmp and changed the background based on one of the 20 most recent @papes posts every few minutes. I get the impression that most other techies here, yourself included, want to spend their time doing efficiency tinkering and playing whack-a-mole with subtle bugs and security holes. There's plenty of merit in that sort of thing, but it's not really what I want to do, and I think it's self-explanatory why efficiency/security tinkering would come into conflict with experimentation and feature expansion, since doing the latter in a way that doesn't take months and months for every little thing entails quite a bit of risk.