Full stack web developer currently working mostly with #PHP / #Laravel, Vanilla #Javascript and #SCSS. Love learning more about (almost) anything, but particularly #MySQL and #InfoSec. Currently learning Arabic. Husband, father of two boys, Christian.
My point here is that this is something you can’t control, because 1) scrapers will scrape it anyway and 2) 99% of spammers don’t get your email address from scraping.
Today the Swiss Army is landing the FA-18 fighter jets on the highways. It's an exercise to train the pilots at landing on "decentralized" infrastructure in case of degraded airbases. #AlphaUno
It’s been almost 3 months since #Threads joined the Fediverse family. A quick overview of what changed since then:
The hordes of Nazi/homophobic users from the outside world into our safe islands are nowhere to be seen. I was insulted multiple times a couple of months ago, along the lines of “if you don’t proactively defederate Threads then you’re an asshole who does nothing to protect the marginalized minorities on the Fediverse from the outside world!“. Well, guess what, it turns out that not everyone outside of our comfort zone is a pathological jerk craving for psychological abuse. It turns out that the minorities police over-reacted. And it turns out that the whole Fedipact thingy was probably collective hysteria.
The Threads-Fedi sync is still an opt-in feature, and only available to accounts in selected countries. And posting responses from the Fediverse to a Threads post isn’t supported yet. I’m not sure if they are ever going to change that, but given the lack of announcements in these months I’m wondering if anybody at Meta is even bothering to work on this integration, or if it was just about another loud announcement for what was a time-bound experiment with no follow-ups.
Threads itself, after reaping the initial novelty benefits, is losing momentum. No E-E-E on the horizon for now.
Result: I added a couple of Threads accounts to my list, I see their content on my timeline every now and then as if they were just another Fediverse instance (but one that I can’t directly interact with), end of the story.
I agree with Dan Mall here: if you want something from me, if you make me guess what it is, there’s a higher chance I will say no, just, because we all have tones of things to think about. Make it easier for people to say yes to you, by asking direct questions, and being very specific.
Microservices aren't a silver bullet. Rewriting your monolith into microservices because you think it's unwieldy or difficult to maintain will not solve your problems. Thanks for your attention.
@louis I do not think you understand what this PR is about or what is does. It does not collect anything about what you search for, and there is no personal data involved here. You can see this as "improved web logs”. OpenTelemetry is an open protocol to collect technical traces of request to have a better overview of their performance.
It is disabled by default, and only useful for admins who want to work on improving Mastodon's performance.
There's a huge advantage to choosing a boring stack over the new shiny: the boring stack has years if not decades of people talking about it on places like blogs, Stack Overflow and more, to help guide you when things go wrong.
Building exciting things doesn't require the new shiny.
"Boring", battle-tested tech can be lots of fun, too. And easier to fix, to boot.
I gave Jira AI a try. So I typed this into AI to see what would happen. Was not disappointed. Well alright I was. Haven't found it give a useful or correct answer yet.
Is it just me or is #phpstorm getting worse by the day?
I'm runnig 2024.1 (Build #PS-241.14494.237, built on March 27, 2024) but have to constantly restart the IDE to fix bizarre errors like PHPStorm claiming a property or parameter isn't used while highlighting the very use a line later, inconsistently resolving asserts with instanceof checks - e.g. claiming a method doesn't exist in the class referenced in a different assert and not seeing a parameter that is clearly there... #fail#ensh11n
Have you ever stood up, from scratch, a completely new version of your application in a production-ready state?
If you haven't, you should.
You may never need to fully stand up a complete production instance, but what happens if a part goes down like your database, your webservers, or your jobs? Are you prepared for emergencies?
For those who aren’t aware, Microsoft have decided to bake essentially an infostealer into base Windows OS and enable by default.
From the Microsoft FAQ: “Note that Recall does not perform content moderation. It will not hide information such as passwords or financial account numbers."
Info is stored locally - but rather than something like Redline stealing your local browser password vault, now they can just steal the last 3 months of everything you’ve typed and viewed in one database.
It’s interesting to note that many of the AI suggestions for PHP code (in IDEs) use older syntax and practices, such as using a string for the fully-qualified class name, instead of ClassName::class, which is the modern and generally-accepted best practice today.
So, if AI was trained on all the publicly-available code it found on GitHub and the rest of the web, and if MOST code is shit code, then does that mean AI is recommending the worst practices to new developers?
Please, web app developers, consider how your users will upgrade. If your upgrade process is "remove the old one, unzip the new one", then it's not an upgrade process. It's an encouragement to never upgrade.