シャドーイング練習: PirateSoftware is right, this needs to stop - YouTubeで英語スピーキングを学ぶ
C1
If you're a prolific enough gamer,
292 文
文が短すぎたり長すぎる場合は、Editをタップして調整してください。
1
If you're a prolific enough gamer,
2
you might have noticed that itch.io was down a few days ago.
3
The reason is utter chaos.
4
Throughout my years, I've seen a lot of different ways that a website can go down.
5
I've never seen one quite as weird,
6
dumb, and just worth talking about as this one.
7
Quickly, from their words, itch.io has been taken down by original Funko
8
because they used some trash AI-powered brand protection software
9
that created some bogus phishing report to our registrar who ignored our responses and just disabled the domain.
10
This isn't that simple.
11
This is hilarious.
12
They even called his mom.
13
Yes, the HIO founder and owner's mom got called because they were so upset about the social media.
14
This is chaos and we have a lot to talk about.
15
And I promise you we'll get there right after a quick word from today's sponsor.
16
Zavala, the best place to deploy anything.
17
And I mean anything.
18
They're not joking when they say this.
19
They came from the WordPress world.
20
If you've heard of Kinsta, this is them.
21
They've built a platform to host everything else.
22
And I mean it.
23
From here, I can click one button and deploy a Laravel app,
24
Django app, Vita app, Next app, any of these.
25
And it's not just the app code.
26
It's the database too.
27
It's the CDN with Cloudflare.
28
All the craziness you need to set up a web app correctly.
29
It takes multiple info providers to do it right.
30
Now it doesn't.
31
It's basically like you set up your AWS perfectly
32
and you're using Cloudflare for the CDN because their CDNs are the best in the world.
33
But it actually does all of it for you.
34
I just click the deploy button.
35
It's deploying right now.
36
Cool.
37
Let's deploy.
38
If we go to the overview,
39
we can see all the parts we can see that Cloudflare is in front with DDoS protection.
40
We could even set it up with CDN
41
and edge caching with any of the different deployments that we do doesn't have to be next.js.
42
You can use the cool next features we're used to from Vercel anywhere now with all the fun integrations,
43
everything from automatic builds on pull requests,
44
all the fun GitHub automatic deployment and CI stuff,
45
everything you would need or expect built in.
46
If even I can spin up a full stack Laravel app that effortlessly,
47
you're going to have no trouble.
48
It's a fantastic platform for hosting pretty much anything.
49
And I've had a lot of fun with it myself.
50
Thank you, Savala for sponsoring.
51
Check out today at soydev.link slash Savala.
52
Thankfully, by the time you're watching this video,
53
itch.io is again back online, which is very good.
54
The indie game scene needs itch.
55
If it fails, a lot of indie game dev goes along with it.
56
We need itch.io to survive.
57
These types of things are, to be frank, pathetic.
58
Also credit to Pirate Software for putting this on my radar.
59
Absolute chaos.
60
We need to break this down layer by layer.
61
Obviously, the immediate effect, HIO was taken down.
62
The takedown happened because of I want my name,
63
which is a DNS provider.
64
I have to Excalibur draw this because there's a lot of layers
65
and I want to make sure that we get it right.
66
so if you know anything about software you know it is built on layers
67
if you have something like a dns provider this has to be built on something this is built on registrars
68
and i can't standard shit
69
so on top of the registrars we have a dns provider the dns provider is something
70
that you now use as the like service owner.
71
So when you are the owner of something like ping.gg,
72
hio, whatever, you have built on top of the DNS provider by buying the domain through them,
73
they are buying things through the registrar.
74
In this case, the service is a shop for buying games.
75
So the service has a layer on top,
76
which is users distributing software.
77
So now if you're a game dev,
78
you're shipping things on itch.io
79
so I should label these all itch.io is this layer you have a game dev
80
that is this layer we have I want my name is the dns layer and then you have a whole different layer,
81
which is users buying the software.
82
This is the layer I don't want to talk about the gamer.
83
What's interesting when you're in scenarios like this is how the liability chain works.
84
Let's say you're a separate party, in this case, Funko.
85
And you have identified that somebody is distributing software that violates your trademark.
86
You are Funko, and you've identified that at this layer,
87
a game dev is doing something that is illegal.
88
In an ideal world, Funko would go straight to that game dev doing that and tell them,
89
hey, if you don't stop,
90
we're going to go after you.
91
Because this isn't itch.io violating anything.
92
This certainly isn't I want my name violating anything.
93
This is a game dev supposedly using Funko stuff in an unlicensed way that Funko is now going after them for.
94
But Funko didn't do that.
95
You'd think, okay, the next best thing,
96
they're going to go to itch.
97
Nope.
98
Because Funko is not the one doing it.
99
Funny enough, what happened here is there's a middleman.
100
Funko contracts to Brand Shield to protect their brand.
101
And Brand Shield has their special way of doing this.
102
Brand Shield decided that it's easier to not go to the game dev who's causing the problem,
103
certainly not to go to the service owner,
104
but instead shortcutting all the way to the DNS provider and also in that process,
105
threatening them saying, hey, by the way,
106
if you don't comply with our demands,
107
we're going to go to the registrars that you work with and tell them,
108
by the way, you shouldn't work with this company.
109
They're distributing things that are illegal.
110
And this is where the problem happens.
111
The thing that sucks here is a user on this layer,
112
somebody who is distributing things on your service,
113
is capable of causing something much lower in your chain,
114
in this case, your DNS.
115
Without you being involved at all,
116
it's possible for somebody distributing software on your service to cause the things you're building on top of to get fucky.
117
To give an example for us,
118
because I dealt with this recently with Upload Thing,
119
by the way, if you're not familiar,
120
we built the best way to manage file uploads in your full stack applications.
121
Upload Thing allows users to upload files.
122
We had a similar problem.
123
Instead of registrars, I will call,
124
I'll put ISPs on the bottom, so internet service providers.
125
Then we have our hosting providers.
126
In this case, it's Cloudflare.
127
Then we have service owner, that's us, upload thing.
128
Service customers, which in this case would be a full stack dev.
129
And you have web app users.
130
I'll say this is users of service or users of,
131
I don't even know what to call this, actual end user.
132
Cool.
133
So it's fun here now.
134
Let's say somebody builds a clone of Google Drive using Upload Thing.
135
If you built an Upload Thing clone for Google Drive,
136
now you have users.
137
Let's say one of those users uploads spyware.
138
Now we have hosted on UTFSIO slash f slash spyware.exe.
139
Some end user uploads this file.
140
Now this file exists on Cloudflare's infrastructure.
141
This is key, and this is really dangerous,
142
not because this domain is associated with Cloudflare,
143
but because this file is being served from one of their IP addresses.
144
So because a user all the way up the stack here has uploaded some spyware,
145
this isn't the full stack dev's problem.
146
This isn't even our problem with uploading.
147
This becomes Cloudflare's problem because an ISP now will hit up Cloudflare and say,
148
hey, we're going to block your IP addresses because they're being used to serve malware.
149
And then we get a scary letter from Cloudflare saying,
150
hey, upload thing builders, there is spyware being served from your service.
151
You need to get rid of this ASAP ASAP because if we don't,
152
then Cloudflare's IP addresses get blocked by ISPs.
153
Now we have to go up the chain yet again.
154
So Cloudflare goes to us and says, hey, what the fuck?
155
Fix this.
156
Now we have to go up the chain once more and say,
157
hey, we just deleted this file.
158
Fuck you.
159
Our options now are we can ban this user
160
if we think they are aware of the malicious actions and not doing anything,
161
or they themselves are the malicious actor.
162
Or they now have to go up and they come back to us and say,
163
no, that wasn't us.
164
We had a malicious user.
165
We're sorry.
166
We'll do better filtering for it.
167
And they have to go ban their individual user.
168
So somebody all the way up the chain as a bad actor here can result in an ISP banning Cloudflare's IP addresses.
169
That's why these chains suck and why they have to be addressed as aggressively as they do.
170
But ideally, this would have happened much higher up the chain,
171
which is something we're now working on.
172
We're going to be restricting your ability to host files that are runnable and executable.
173
You won't be able to host bash scripts or CMD files or EXEs on free tiers ever again.
174
That's over now.
175
We've learned our lesson.
176
In the future, we'll be doing more scanning and things like that as well,
177
working on introducing all of that.
178
The fact that these things affect us in these hierarchies sucks
179
because now a user of a customer of our service can cause Cloudflare problems.
180
Thankfully, this was a notification system where we were told this was happening,
181
where in this case, Brand Shield didn't give anyone any opportunity here.
182
They went to I want my name and said,
183
if you don't ban this DNS and ban this domain right now,
184
we are no longer going to allow you to work with ISPs.
185
We will force legal action.
186
We will go to these ISPs.
187
You're screwed.
188
Get rid of this domain.
189
And out of panic, and also I would argue incompetence,
190
I want my name caved and removed one of the most popular domains on the internet.
191
One of the most popular IO domains for sure,
192
because they suck at their jobs.
193
But so does Brand Shield,
194
because Brand Shield should have had any system to notice,
195
oh, itch.io is a service for distributing other people's software.
196
They are the ones we should be hitting up.
197
But they didn't do that.
198
They went straight to I want my name and got itch.io banned from the internet for like over 24 hours.
199
And here's what Brand Shield had to say.
200
You might notice they have replies off and also a lot of community notes on this.
201
We want to address recent reports surrounding a website takedown.
202
Brand Shield serves a trusted partner to many brands.
203
Our AI-driven platform detects potential threats and provides analysis,
204
and in this case, an abuse is identified from an HIO subdomain.
205
We identified and reported the infringement and requested a takedown of the URL in question,
206
not of the entire HIO domain.
207
The temporary takedown of the website was a decision made by the service providers,
208
not BrandShield, because you didn't report it to the right provider.
209
You reported it to the DNS provider, not to HIO.
210
BrandShield remains committed to supporting our clients by identifying potential digital threats and infringements.
211
We encourage platforms to implement stronger self-regulation systems that prevent such issues from escalating.
212
Nonsense.
213
Brands showed these to realize that a subdomain is probably owned by the original domain.
214
And it should probably go to the service provider of the original domain to figure out what is wrong there.
215
And calling itch.io's mom, like that is horrifying.
216
Like I get that you want to get some press stuff
217
and you want to like cool it down and the HIO guy probably wasn't responding to your bullshit Funko Pop requests,
218
but going after his mom is just insane.
219
I would have loved to just blame Brand Shield and say Funko Pop's not the problem,
220
but this alone means all of these companies fucking suck and should be mocked relentlessly for what they've done.
221
They also moved off of I want my name after this because what the fuck?
222
Here's what Pirate had to say.
223
Instead of filing a DMCA claim to itch.io,
224
you sent a takedown request to their registrar.
225
Are you incompetent or are you just lying about your intentions?
226
For those that don't understand why this would set me off,
227
the company Brand Shield is a brand protection company that files infringement claims on behalf of their customers.
228
In this case, they filed an infringement request with Itch's registrar for a user-generated page that contained Funko Pop branding.
229
This led to a complete takedown of the website for the better half of this morning.
230
Sorry, I thought it was a whole day.
231
It was only half a day, I guess.
232
This is the equivalent to Twitch being taken down because a single user was streaming a copyrighted movie.
233
Yep, exactly.
234
And a good link from, funny enough, Twitch staff.
235
HIO's terms of service.
236
Look at that.
237
They have a whole section here for the DMCA.
238
If you believe one of our publishers has violated your copyright,
239
please let us know about your complaint with the required information so we can address the complaint.
240
If you think a complaint was filed in error,
241
you can also contact us to address your concerns.
242
There you go.
243
Technically speaking, since neither Brand Shield nor Funko are customers of HIO,
244
they're not expected to comply with HIO's terms.
245
but you should check them quick to figure out what the right method is for reporting.
246
But since this isn't a human doing a correct method of reporting,
247
this is a crappy rogue AI tool sending threatening emails around.
248
Disgusting.
249
This is what happens when you let AI go without a human in the middle.
250
Absolute fundamental failure.
251
And Brand Shield should at the very least check how popular a domain is before sending one of these bullshit accusations.
252
Ideally, they would shut down.
253
This is bullshit.
254
But like, yeah, God.
255
As Pirate said, Itch has a very easy process for handling DMCA claims and these processes were ignored.
256
It's clear that Brand Shield didn't do any research before firing the gun and they shouldn't be taking actions as such.
257
Brand Protection Company should know better.
258
The Registrar should know better and Funko Pop should know better.
259
To follow this up, Brand Shield has tried to blame the victim here.
260
Yes, they are continuing to try and blame people for doing things right effectively.
261
It's kind of insane.
262
It's like this should be the end of their business.
263
And I would be genuinely somewhat disappointed if people continue to sign up for their service after this.
264
Because I'd hope when you Google search them, this comes up first.
265
At Funko, we hold a deep respect and appreciation for indie games,
266
indie gamers, and indie devs.
267
We're fans of fans, and we love the creativity and passion that define the gaming community.
268
Recently, one of our brand protection partners identified a page on Itch,
269
imitating the Funko Fusion development website.
270
A takedown request was issued to address a specific page.
271
Fungo did not request a takedown of the Itch platform,
272
and we're happy to see the sites back up this morning.
273
He reached out to them to engage with them on this issue,
274
and we deeply appreciate the understanding of the gaming community as the details are determined.
275
Yeah, as the top reply says,
276
it's a lot of words to not say that they're sorry.
277
And on top of that,
278
not admitting that their brand partner,
279
Brand Shield, didn't contact Itch.
280
They skipped multiple steps and went all the way down the chain.
281
I would argue there could be a lawsuit here for irresponsible behavior on a brand with intention to damage.
282
It's pretty absurd.
283
Yeah.
284
This also should have been a DMCA request.
285
If it was actually phishing,
286
like they were trying to look like Funko Fusion when they weren't,
287
a fraud of phishing report might make sense.
288
But again, that should go to HIO, not to their registrar.
289
And I can't give any benefit of the doubt to Funko over any of these steps because of how they've behaved.
290
That's all I got on this one.
291
don't break copyright laws and if you do or you see someone doing it report it the right way please
292
until next time peace nerds
アプリをダウンロード
話したすべての文をAIが採点
TRENDING
人気動画
この動画で話す練習をする理由は?
この動画は、スピーキングスキルを向上させるための素晴らしいリソースです。特に、ゲーマーとしての経験や、特定の状況における反応の仕方が詳しく語られており、リアルな会話のコンテキストが提供されています。英語の発音を良くするためには、他者との対話を模倣することが非常に重要です。このような具体的なシチュエーションでの会話練習は、実際のコミュニケーションに役立ちます。
文法と表現の文脈
- 受動態の使用：
- 時制の変化：
- カジュアルな言い回し：
「itch.ioは元のFunkoによって取り下げられた」というフレーズでは、受動態が用いられています。これを理解することで、自分でも様々な文脈で活用できるようになります。
話者が過去の出来事を語る際の時制の使い方に注目です。「ここ数日、私は多くの異なる方法を見てきた」という表現は、過去完了形が分かりやすく使われています。
日常会話の中でのカジュアルな表現も、スピーキングの練習には不可欠です。たとえば、「これは面白い」というフレーズは、気軽に使える一例です。
一般的な発音トラップ
この動画では、英語の発音において特に注意すべき単語やアクセントがあります。たとえば、「chaos」と「bogus」の発音は、日本語話者にとって難しい部分です。また、特定の単語や表現が話されるスピードによって、発音がわかりにくくなることもあります。shadowing siteやshadowspeaksのようなリソースを使って、こうした単語の正しい発音を練習すると良いでしょう。
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。