These sites look very similar to the ones I see mentioned in user agents scraping our website or API.
A few years ago there would be about 20 bespoke user agents in a day, generally closely related organisations/universities who have embedded one of our widgets or similar.
Yeah, I had a similar reaction looking through the directory. Then I started clicking through. Some of those sites are new products from established companies. Others are side projects by people who’ve already built things I recognize.
If this site had been around in 2004, I’d probably have described Facebook as "a directory for Harvard students" and kept scrolling. That’s what I’m curious about: which projects am I scrolling past today that I’ll recognise in a few years?
I believe the answer will be tenacity. It's so easy to start a new project, and so so difficult to keep it going in the right directions for 10 years. The "top of the funnel" for these projects has exploded with AI, but the survival rate will be interesting to watch.
I am curious about that too. I put a traction section to track what changed on listed websites. You can clearly see how many projects start with landing page, then add appstore download link or reference to client.
Tried it out, this does not seem to work well. A codebase that runs fine on MiniStack could not be emulated with this official AWS emulator.
Specifically it does not support certain SFN fields (like `Assign`) and Lambda Python code was not fully supported, so SFNs and Lambdas did not work and the test had to stop there.
Wondering if you thought about the effects that AI exposure can have on a young brain? Adults are experiencing brain rot, do you think kids could have it even worse?
Honest question, I don’t mean that sarcastically. Wondering if AI exposure will be compared to doomscrolling social media in the future.
It's a line I've been trying to balance. I don't think outright bans are helpful. AI is going to be there in some shape or form in the future and we need to know how to use it to our advantage. Getting hooked onto it is a problem. I know I experience that myself.
My main barrier against this has been to talk with him regularly about this. Amplify the positives rather than warn about the negatives so that the first gets done more and the latter gets atrophied.
Way to minimize cheating. Describing it as a “moment of weakness” makes it sounds like it’s a minute of lapse of judgement, meanwhile we’re talking about pre-mediated, long-term cheating.
Ah yeah, a .dmg installer that asks for sudo permissions is much safer /s
Why do people get hung op on this so much? You can just read the script before running it. Of course you won’t though, just like you don’t read the source of the .dmg installer.
Also a very early subscriber; similarly no clue what 'early adopter drama' there was. Maybe it was the free shirts? I really had no complaints with that and the shirts made for good walking billboards. Several people have asked me what "Humanize the web" meant.
If you're not working on something highly secretive and valuable (with a salary to match) then they're doing you a favor by flipping out over something so stupid.
Forgejo did and will in the future, same as GitLab.
The only difference is the architecture/moving parts/featureset which roughly corresponds to the attack surface, which then roughly corresponds to how many CVEs will be found, though that's also affected by how big a given target is.
That's not to say that Forgejo is some perfect piece of software, just that it builds on some of the past experience of Gitea and just has both less features than GitLab, is simpler, and also a smaller target. It will probably get >100 per year too soon, but I'd reckon that the totals will remain than GitLab for the foreseeable future.
I mean I knew this was the case, I just didn't realize the extent yet
reply