poop
poop copied to clipboard
claustromaniac
Not an issue
that lil pink turd looks so cute on mah toolbar!
the v1 update is quite a piece of work ... now i'm gonna have to update my FF guide :(
the v1 update is quite a piece of work ... now i'm gonna have to update my FF guide :(
You can thank/blame @crssi for that, since like more than half of the features were his idea. :grin:
Thanks, but nah. If the poster wanted me to reply he would be asking me.
I updated the documentation to explain in some more detail (without extending myself too much) why I consider this extension safe. I guess many people won't even bother reading that, but I don't care.
thanks for that claus! however i think i have a new (potentially dumb) question...
if one is using uBO and/or uM to filter all 3rd party requests (except CSS and images in my case), and FPI is enabled, is poop still desirable?
i'm guessing the answer is 'yes' because when i look at uM and poop for this page here on github, where i allow requests for github.com and githubassets.com in uM, i see poop is altering 5 requests
Well, you have answered with:
except CSS
There are also CSS leaks to be seen. Not very often, but still are and I would wild guess that in the future we could see even more leakages over CSS requests.
Otherwise, if you block all 3rd party's in uBO/uM, then you would not need PooP IMHO. But there are always some 3rd party allowed to make the visited page work. :wink:
i'm guessing the answer is 'yes' because when i look at uM and poop for this page here on github, where i allow requests for github.com and githubassets.com in uM, i see poop is altering 5 requests.
Well, in this particular case it doesn't matter, since github already knows that you are at github. :wink:
But, even when PooP does alter request, it will (most likely) not lead to breakage.
In case of breakage, you can drop the following to exclusions: *.github.com *.githubassets.com or *.github.com *.github*.com
The only breakages so far found is google and youtube (so google in both cases) and only for XHR (if you enabled also XHR). In that case drop the following into exclusions:
*.youtube.com *
*.google*.* *
Cheers
Well, yeah. The more third-party requests you block, the smaller the surface will be, but as long as there is any surface left you can still potentially benefit from this.
But there are always some 3rd party allowed to make the visited page work
exactly
The only breakages so far ...
dailymotion.com
*.dailymotion.com *.dmcdn.net
tankz!
@atomGit would you be so kind and drop here your PooP configuration and describe what breaks at dailymotion.com, since I just can't find the breakage.
Thank you
i was gonna re-test that before i popped back in, but i can't get vids to play at that ultra-shitty site at all at the moment and no time to troubleshoot
poop: aggressive, exclude roots ... and that's it, except for the exception i mentioned earlier
no sir - hadn't done any more testing - you can close this and i'll let you know if i find any issues in the future
I mean, it puzzles me that you had to add *.dailymotion.com *.dmcdn.net in order for video to work at dailymotion, since I cannot reproduce.
Can you try it again without *.dailymotion.com *.dmcdn.net?
finally got that crappy site to play videos - no idea what i did now that i didn't do before
anyway, yes, vids WILL work without *.dailymotion.com *.dmcdn.net
sorry for the trouble
No problem my friend... OT: I would advise you to set into relaxed mode, additionally (beside font and css) you can check script and XHR. Check Exclude Root domain matches and add exclusions a few posts up.
Cheers
poop wasn't the problem - i had it in aggressive mode when playing the video actually
I know...
OT = off topic :wink:
I am just telling you what is the best setting by my standards.
FYI: I am not a fan of poop related jokes, but it's a solid number two
also: https://www.ghacks.net/2019/01/19/privacy-oriented-origin-policy-for-firefox/