As above, to reflect on the policy change as of yesterday.

Mind me asking, but what kind of policy ?

Well, even I'm not sure about it. I know that all links were taken down, but I'm not quite sure of what we CAN link the users to right now(like DLC) .

Mind me asking, but what kind of policy ?

 

The no more posting links to DLC/cod related stuff policy.

Mind me asking, but what kind of policy ?

 

The no more posting links to DLC/a popular FPS series related stuff policy.

 

Staff not linking to them is okay. But the community can still do it, right ?

Doesn't matter who posts them, this domain (server even?) may not host nor link any compyrighted files from atvi.

We could use a parallel site to help our users with everything wich is copyrighted. Also to teach them stuff such as "d.w." (different from "zone") folder.

Make FourDeltaOne.net as clean as possible, and then leave all the dirty work to some website ment to get killed by atvi and later respawned without affecting our users experience.

What about pictures of a link ._.?

What about pictures of a link ._.?

Lol. Don't think that there's a difference...

What about pictures of a link ._.?

Lol. Don't think that there's a difference...

 

That is still considered linking. Can't you just make a dns referal link that links to it from a different domain to a direct media fire hosting or something like that?

The only way is to just put the links in the IRC topic title

The only way is to just put the links in the IRC topic title

 

FlaCCidCookie mentioned magnet linking, what about that ?

Or tell them to google fourdeltaone IW5M repository like we always do with IW4M.

 

Or tell them to google fourdeltaone IW5M repository like we always do with IW4M.

 

The problem is that the content is still being released and there's more to share like the bypasses.

We really need an autonomous domain to support this one.

What about pictures of a link ._.?

Lol. Don't think that there's a difference...

 

That is still considered linking. Can't you just make a dns referal link that links to it from a different domain to a direct media fire hosting or something like that?

 

Isn't that still linking ;p

 

 

Or tell them to google fourdeltaone IW5M repository like we always do with IW4M.

 

The problem is that the content is still being released and there's more to share like the bypasses.

We really need an autonomous domain to support this one.

 

Oh, what about my mufffin site.

Oh wait.

Oh, what about my mufffin site.

Oh wait.

I do know about your mufffin site. I was even thinking about it when I wrote this.

But the question is, are you willing to take all the legal responsabilities yourself?

 

Also, I've been thinking about these "Steam checks" and it's bypasses...

This thing of "creating a d(censor)w folder" to bypass the Steam checks is too much obvious. We can still be easilly blamed, since the bypass is on the code.

We should have a client built in a way that clients wouldn't be able to bypass Steam checks that easy. Then, some site like "4d1.jeremych.com" or "mufff.in" would distribute a universal bypass. A dll that would hook the function on any 4D1 client and disable Steam checks. The client released by 4D1 would be completely clean. Then some "external" dll would do the hooking and disable the function. That hook would work even if an update is released, since the client files aren't being modified, unlike the old iw4m.dll patcher.

It would be harder to point a finger at FourDeltaOne.net that way. Legally, FourDeltaOne would really enforce the Steam ownership checks, but would also be a victim of some external site piracy, just like atvi is a victim of skidrow, reloaded, etc

I think the current steam checking method is fine, and doesn't involve me hosting any bypassing tools, something I'm not willing to do.

 

The current DLC files are hosted using zerobin, so that means nobody knows who made those pastebin's (technically). I'm not hosting the DLC files, so that's good. I don't expect myself to get into trouble.

I think the current steam checking method is fine, and doesn't involve me hosting any bypassing tools, something I'm not willing to do.

 

The current DLC files are hosted using zerobin, so that means nobody knows who made those pastebin's (technically). I'm not hosting the DLC files, so that's good. I don't expect myself to get into trouble.

 

But I am o: ohshitwhatnow

I'm hosting the files on my MF and I'm sure Acti put a complaint already for my files.. so um gonna take them down.

I'm hosting the files on my MF and I'm sure Acti put a complaint already for my files.. so um gonna take them down.

quite certain a complaint would be followed by an immediate takedown

I'm hosting the files on my MF and I'm sure Acti put a complaint already for my files.. so um gonna take them down.

quite certain a complaint would be followed by an immediate takedown

Yep, the files are taken down and your account gets flagged.

 

tbh you should just send a counter-claim with fake info, wait 2 weeks, then contact mediafire to get your account un-flagged

I'm hosting the files on my MF and I'm sure Acti put a complaint already for my files.. so um gonna take them down.

quite certain a complaint would be followed by an immediate takedown

Yep, the files are taken down and your account gets flagged.

 

tbh you should just send a counter-claim with fake info, wait 2 weeks, then contact mediafire to get your account un-flagged

Eh whatever I deleted them before anything could happen. Just hope they don't flag me for IW4M files or I'm gonna be pissed.