; the complainer owns the copyright for the item in question.
>
> However, your host may not be passing on all the details to you, that's
> a matter of discussion between yourself and your host.
>
> On Tue, Aug 23, 2016, at 11:12 AM, Sarah Alawami wrote:
>> No, the DMCA
our host may not be passing on all the details to you, that's
> a matter of discussion between yourself and your host.
>
> On Tue, Aug 23, 2016, at 11:12 AM, Sarah Alawami wrote:
>> No, the DMCA was not specific. That's all they told me was that copyright
>> material were g
No, the DMCA was not specific. That's all they told me was that copyright
material were going through the vps and I was breaking the TOS.
> On Aug 22, 2016, at 5:19 PM, Mike Perry <mikepe...@torproject.org> wrote:
>
> Sarah Alawami:
>> Hello to all. Sadly I have to shut do
mir <miri...@riseup.net> wrote:
>
> On 08/21/2016 09:33 PM, Sarah Alawami wrote:
>> Actually, no ip complained. It was the VPS I am hosting this thign on. I'll
>> keep an eye on logs I gguess when I have the time.
>
> Well, presumably someone complaine
Actually, no ip complained. It was the VPS I am hosting this thign on. I'll
keep an eye on logs I gguess when I have the time.
> On Aug 21, 2016, at 3:26 PM, Mirimir <miri...@riseup.net> wrote:
>
> On 08/21/2016 04:13 PM, Sarah Alawami wrote:
>> Well I could be nasty and r
>> access), and ports 110, 143, 465, 587 for email access. It rejects
>> anything else.
>>
>> This should stop your copyright infringement problem or at least reduce
>> it to almost nothing since the users would be restricted to stuff they
>> can get on regular we
tart Tor after you modify the file.
> If you're using Ubuntu just issue a
>
> service tor restart
>
> Good luck!
>
>
> On 8/20/2016 6:53 PM, Sarah Alawami wrote:
>> Ok, I modified it. We'll see what happens I guess. Bleh I have to start over
>> with th
t;anth...@cajuntechie.org>
> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 8/20/2016 5:47 PM, Sarah Alawami wrote:
>> Hello to all. Sadly I have to shut down my tor relay after less
>> then 24 hours, as I received a copyright violation and I
Ok, I modified it. We'll see what happens I guess. Bleh I have to start over
with the tor cycle. Oh well, it's all a lyearning process. Eh?
> On Aug 20, 2016, at 4:39 PM, Anthony Papillion
> wrote:
>
> ExitPolicy accept *:80
> ExitPolicy accept *:443
>
ent problem or at least reduce
> it to almost nothing since the users would be restricted to stuff they
> can get on regular websites (no torrents, USENET groups, etc).
>
> Hope this helps!
>
> Anthony
>
> On 8/20/2016 6:29 PM, Sarah Alawami wrote:
>> Well I'm no coder.
<pa...@web.de> wrote:
>
> Made the same experience this week within 24 hours as well on Bit Torrent
> Changed my Exit-policy - never had that before...
>
> Go on...
>
> All the best
>
> Paul
>
> Am 21.08.2016 um 00:49 schrieb Anthony Papillion:
>> On 8
Hello to all. Sadly I have to shut down my tor relay after less then 24 hours,
as I received a copyright violation and I don't want any network restrictions
placed on me as I want the 150mbps speed.
Sorry to all who were using it, but yeah there it is.
Blessings.
--
tor-talk mailing list -
and happy Friday
Sarah k Alawami: Owner of Alawami Productions, where quality is key.
Check us out at http://alawamiproductions.com/listen
and for the itunes page go here.
https://itunes.apple.com/us/artist/sarah-alawami/id268693059
Welcome to the tffp podcast. For more info go to our website:
http
Oh, I'd donate a relay, however I really don't feel like logging onto my
virtual private server, spinning another one up only to have it compromised in
some odd way.
Good job on the network guys. Keep it up.
> On Jun 26, 2016, at 1:38 PM, Jonathan Wilkes wrote:
>
>> I am
Actually this is why I'm using tor. They are throttling my bandwidth that comes
from a site for the blind to nothing. I can browse but that's about it. I
can't dl from there. But with tor and my cellphone tethered to my laptop I can.
Also if I bypass my isp and use tor as a proxy such as I'm
Thanks for this. Hopefully it will make it to homebrew for when I run my update
script in a few weeks.
Happy Thursday.
> On Jun 15, 2016, at 10:00 AM, Nick Mathewson wrote:
>
> Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
> If we find no new
>
> I'm not sure what google has against tor.
>
>
> On 6/6/2016 7:03 PM, Sarah Alawami wrote:
>> Oh good, I'm not theeonly one seeing the error then. Well I guess I will
>> have to not do my google searches when using the tor network then I guess. I
>> use the
n 6, 2016, at 1:33 PM, Kevin <kevinsisco61...@gmail.com> wrote:
>
> Well I tried it and it gives me that error. It seems that google is blocking
> tor. At least that's how it seems to me.
>
>
> On 6/6/2016 4:10 PM, Sarah Alawami wrote:
>> I can try it out, but if
AM, Cecilia Tanaka <cecilia.tan...@gmail.com> wrote:
>
> On Jun 6, 2016 1:47 AM, "Sarah Alawami" <marri...@gmail.com> wrote:
>
>>> I was just on the tor network and launched google to do a google search.
> I got a 403 forbidden when trying to search for
. It works though. I can
always do my searches when I get out of tor assuming I remember to exit out
when I'm done that is. Lol!
> On Jun 6, 2016, at 10:56 AM, Not Friendly <notfrien...@riseup.net> wrote:
>
> On 2016-06-06 13:19, Sarah Alawami wrote:
>> I'm no lawyer, I'll
I'm no lawyer, I'll let someone else deal with this. But I thought I'd let
someone on the list who might be better at letter writing than I know.
Blessings and happy Monday
> On Jun 6, 2016, at 8:49 AM, Not Friendly <notfrien...@riseup.net> wrote:
>
> On 2016-06-06 00:46, Sara
Hello to all. I was just on the tor network and launched google to do a google
search. I got a 403 forbidden when trying to search for something. I know this
might not be fixable, but Can this at least be noted somewhere? Here is the
contents of the error.
403. That’s an error.
Your client
22 matches
Mail list logo