WEBVTT

1
00:00:00.580 --> 00:00:14.480
What's up everyone? Welcome to Next in Dev. In this episode, I cover Payload's modular dashboard, new AI lawsuits, and the ability to bring your own keys to JetBrains IDEs. The Payload team released version 3.69.

2
00:00:14.520 --> 00:00:20.200
The crowning feature of this version is the ability to use modular dashboards and widgets.

3
00:00:20.300 --> 00:00:28.240
I think I'll take a look at this feature in more detail in a live stream next week, but be sure to check that out for more details on how this beta feature works.

4
00:00:28.300 --> 00:00:36.940
The team added some new AI development resources to their templates as well. All templates now have agents.md and cursor rules by default.

5
00:00:37.020 --> 00:00:43.740
This should improve how your favorite AI tools interact with fresh Payload projects. Payload released a couple key bug fixes as well.

6
00:00:44.200 --> 00:00:56.160
First, the MCP plugin now adds the collection slug and strategy to the user when using MCP operations. This fixes an issue where the user came through as undefined in MCP operations.

7
00:00:56.800 --> 00:01:07.340
The second key bug fix was in the S3 storage adapter. This is a simple fix that uses encodeURI component to ensure the plugin generates properly formed URLs.

8
00:01:07.700 --> 00:01:19.840
There's been some discussion in Discord and on GitHub about using TanStack for Payload. It's early on in the discussion, but a few members of the community are working on creating a TanStack start core for Payload CMS.

9
00:01:20.220 --> 00:01:24.820
I'm excited for the doors this opens for Payload as they become more and more flexible.

10
00:01:24.860 --> 00:01:34.840
Since the release of version sixteen point one, the NextJS team has focused on making their tools more reliable by releasing version sixteen point one point one and several Canary updates.

11
00:01:34.880 --> 00:01:42.520
They fixed specific issues with how Turbopack handles files on Windows and updated the code to stay safe from newly discovered security risks.

12
00:01:42.750 --> 00:01:54.060
They also polished the new bundle analyzer tool to help developers see exactly what makes their websites slow or heavy. Cloudflare has declared code orange. First, OpenAI's code red, now this.

13
00:01:54.340 --> 00:02:04.020
Basically, Cloudflare wants to stop breaking the internet. To accomplish this, Cloudflare will start testing setting changes slowly instead of sending them out to everyone all at once.

14
00:02:04.060 --> 00:02:15.450
This is also a part of a modernization push to get their emergency tools fixed and in better working order. This effort should keep most apps and websites working even if small parts of Cloudflare's systems break.

15
00:02:15.980 --> 00:02:23.859
You'd think that this would have been their plan from the start. A soft and slow rollout of new features just seems like a good idea when you're a large corporation.

16
00:02:24.120 --> 00:02:31.320
The internet experienced another major outage on December twenty-fourth. No one is taking responsibility for this one, but signs point to AWS.

17
00:02:31.780 --> 00:02:39.480
They've since denied it, but it seems that users in the US and India reported issues accessing Fortnite, Ark Raiders, and other games.

18
00:02:39.760 --> 00:02:46.930
As of the time of this recording, the status page for AWS appears to be all clear, so I don't think we'll know what happened with this one for a while.

19
00:02:46.960 --> 00:02:55.920
An investigative reporter is leading a group of authors to sue essentially every AI company for using copyrighted books without permission to train their models.

20
00:02:56.440 --> 00:03:07.520
Perplexity claims that they do not and have not used books to train their AI, and this follows an already settled claim against Anthropic. This is the first case, though, that names xAI as a defendant.

21
00:03:07.530 --> 00:03:14.780
The suing group is not organizing in a class action lawsuit, similar to what we've seen in previous lawsuits against AI companies.

22
00:03:14.820 --> 00:03:25.100
The key difference here is that if AI companies want to settle, they'll need to settle with individual authors, not a class of authors. That means settlements will most likely be larger and spread across fewer people.

23
00:03:25.440 --> 00:03:30.860
I'm interested to see where Anthropic ends up in this, as they've already settled a large class action lawsuit.

24
00:03:31.160 --> 00:03:40.140
Saying a settlement didn't go far enough to protect authors is not really a defense, but it is within the rights of authors who did not join the class action lawsuit to sue on their own.

25
00:03:41.100 --> 00:03:50.400
This will likely drag on in court for years, but I'll do my best to keep up with the news. OpenAI plans to put ads inside ChatGPT to earn more money. I mean, they have to, right?

26
00:03:50.810 --> 00:03:58.890
How else will they turn a profit this century? I just hope they label these clearly, otherwise it's going to be impossible to trust any answers that ChatGPT gives us.

27
00:03:59.340 --> 00:04:10.640
Trust will erode fairly quickly for the more technical users, while others may take a while to recognize what's happening. On the other hand, developers and marketers will have another paid channel to target.

28
00:04:11.090 --> 00:04:20.440
They'll be able to show products that ideally answer questions for people using ChatGPT. Ads always find a way into platforms, but let's hope ads stay in only the free plan.

29
00:04:20.990 --> 00:04:28.120
Attackers continue to hit OpenAI's Atlas browser with prompt injection attacks, so their team is using AI to attack its own system.

30
00:04:28.130 --> 00:04:37.100
The goal of this exercise is to find and patch vulnerabilities before a bad actor gets to it. Hidden text on websites can trick AI agents, and this is not an easy problem to fix.

31
00:04:37.560 --> 00:04:45.200
You'd think that companies would attempt to fix this issue before launching a product, but it just goes to show that these companies would rather be first to market than safely in it.

32
00:04:45.260 --> 00:04:51.460
Cursor released its last update of the year. First, it's now easier to customize your layouts across workspaces.

33
00:04:51.640 --> 00:04:58.900
I primarily use JetBrains products, so it's been difficult for me to understand how to use Cursor's interface. Maybe this will help me understand it better.

34
00:04:59.780 --> 00:05:10.680
Other than that, they released some stability improvements and fixed some bugs. Not a very exciting update, but it was a very necessary update. Google released a few new Gemini features this month.

35
00:05:11.080 --> 00:05:22.200
First, you can draw or type onto an image to prompt Nano Banana to make precise changes to an image. Second, Gemini now allows you to bring Notebook LM notebooks into Gemini.

36
00:05:22.210 --> 00:05:32.650
This new feature means you can have better context and less hallucinated responses from your source materials. The last new feature I'll cover is a new way to use Gemini's Gems.

37
00:05:32.960 --> 00:05:45.020
Gems are personalized custom AI assistants in Gemini. Google is testing a beta feature that allows you to use Gems to create interactive apps for your tasks. Railway unveiled a new homepage.

38
00:05:45.030 --> 00:05:53.740
According to the team, this change attempts to explain what Railway does for you instead of you having to fumble around for the words. I have to say, it does look nice.

39
00:05:54.180 --> 00:06:06.652
After releasing Railway Dev last week, the Railway team released a new terminal user interface, or TUI.This interface provides tabbed service logs, service information shown at a glance, and keyboard-driven navigation.

40
00:06:07.132 --> 00:06:16.812
Developers rejoice! The service logs provide all relevant information for all your services in one place. They're organized neatly into tabs for easy navigation.

41
00:06:16.912 --> 00:06:23.252
The service information shows status information, such as local URL and number of environment variables loaded.

42
00:06:23.752 --> 00:06:37.052
To navigate through all this new information, the Railway team implemented keyboard navigation, so you don't need to scroll through anything with your mouse. It's meant to be as convenient as possible.

43
00:06:37.092 --> 00:06:47.672
The team also released a high-availability Postgres template and template metrics. The Postgres template is available now and uses a Patroni-based Postgres cluster.

44
00:06:47.682 --> 00:06:56.912
This provides automatic failover and load balancing out of the box. It's simple to set up, so you now have this option if the default Postgres options don't cut it for you.

45
00:06:56.952 --> 00:07:09.972
Template creators can now see how their templates are doing. You can see how many deployments there are, what usage looks like, and most importantly, how much you're earning from Railway's template kickback program.

46
00:07:10.292 --> 00:07:18.632
Railway had a busy year this year, and I'm looking forward to what they implement next year. You're now able to bring your own keys to JetBrains IDEs.

47
00:07:19.112 --> 00:07:31.411
This allows you to use your preferred models, locally hosted models, and more. Even better, you don't need a JetBrains AI subscription. Your machine stores and manages your keys and is never shared with JetBrains.

48
00:07:31.452 --> 00:07:42.442
JetBrains will continue to add more providers such as Gemini, Azure, and Bedrock. Currently, JetBrains only supports Anthropic and OpenAI API-compatible providers. What did I miss?

49
00:07:42.792 --> 00:07:49.232
There's so much happening in modern web dev that I'm sure I have missed something. Please share your thoughts in the comments.

50
00:07:49.792 --> 00:07:57.632
I want to hear from you, and I want to address your suggestions and may include them in future newsletters. Thanks for watching or listening. See you next time.

51
00:07:59.292 --> 00:08:10.372
[outro music]