To see the fetches use F12 for the Network tab.
It gets CSS from miy.pw, one Cf website, and that CSS gets icons for each instance type at https://34.wtf, another Cf, based on HTML content.
Aside from inefficient couldn't this track/out users to Cf?
Good question. This comes from the instance tracker feature added to some of our themes (its how we add a banner to posts that show what instance users are from using unique colors and icons for each instance).
We specifically provide theme versions for most of our themes that are o-ticker versions that wont fetch this css or add the tickers. This is specifically for people who dont want to use the tickers third-party css.
So if anyone is worried about this I'd suggest users simply switch to one of the no-ticker themes.
@zleap I cant view it since im in egypt and internet is god awful slow here. But we should find a good spot to put it for people to find it in the future.
@freemo Good point, it is still transcoding at the moment. I have a few similar videos, so could be useful for tutorials etc.
Hi zleap and Freemo (et al),
Thanks for the prompt reply and a video even, @zleap! Unfortunately, we're unable to watch videos at this time, also.
There are, to us, peculiarities to this ticker plugin. It seems to use JS (node.js) on some pages despite us having JS disabled in Tor? @torproject.
is it worth this being brought up on the forum, partly as this is a matter of choice for end users but also something that admins can make clear as to the options the end users have, and the pros vs cons of this.
Yea i think the forum would be a good spot to elaborate on the details and inform users. The about page should briefly mention it and then link to the forum for more info.
Since i am in egypt with a broken leg it might be a bit before i get the chance though.
I will likely be back around good internet in a day or two if all goes well. Can you remind me then.
@miyon is the ticker maker i think.
It was quite some time ago we voted about the default theme, pretty sure cloudflare was known at the time of the vote as i had mentioned it when i first put the theme together. I need to search for the vote for and verify.
Even better if it could be scheduled. Then no remind needed.
Thanks for including @miyon
Cloudflare are only getting more monolitthic/dangerous. It might be interesting to see what your users discuss in a fresh RFC.
We'd be willing to devote time to improving the ticker in future (uses a lot of screen space in addition to being a possible client-side CPU drainer). Ideas @eugen?
Despite the fact that my users didnt seem to care too much about cloudflare in the past i will say its a service i myself like to avoid using when at all possible. So if we can get cloudflare out of the picture and keep the tickers going id personally find that to be preferable.
@zleap @lupyuen @msaunders @witchescauldron @strypey @MitiGator @torproject @eugen @miyon @dsfgs @freemo If you’re going for honest transparency, why not go a step further & refer people to this article so people learn why #Cloudflare is a bad idea → https://git.disroot.org/dCF/deCloudflare/src/branch/master/subfiles/rapsheet.cloudflare.md
I think the intent here is to just quickly mention it in our about page with a link to a more detailed forum article explaining it. In the forum we can add that link (after review it) so people can be informed. In the end they jave the option to use themes without css hosted on cloudflare so im good with that. All for links to help people be informed but im not trying to make a political issue out if it. As long as people are informed im ok with them deciding for themselves if they care. Some people dont want to be tracked, others really dont care, im ok with either group.
It worth mentioning, knowingly exposing users to Cloudflare tracking by default, in today's age, is political already. They're absorbing the internet. On this occasion its nothing that can't be solved with a 'wget', 'sed -i' and some checks. We admit a server-side solution would be better.
Greetings from Australia. Do you offer a selfHost option for ticker out of the box? May you be so helpful as to provide a list of instances that are using miy.pw or 34.wtf as they are (now?) Cloudflare-surveilled, your help would be greatly appreciated.
Please wait for @weepjp 's reply.
Maybe there is one thing you can help with. How was the decision made to become Cloudflare? Was there extreme difficulty with the requests?
We are trying to understand how websites become cf'd in the first place.
Thanks @dsfgs ,
1) I am currently preparing a "Non CloudFlare version" of #InstanceTicker.
2) This version will replace all reference images with dataURIschemes instead of externalURLimages. This will increase the capacity of the CSS.
3) Due to the nature of customCSS, I have decided that all images need to be converted to webp format to optimize size and data volume.
Sounds like a project!
In the interim is there a version of the current ticker for selfHost? Not to be too alarmist but everyday is another day Cf are gathering data on Fedi.
Which instances are currently running it?
What is currently being done to trick Tor into loading content dynamically(?) on Post pages?
Other technical matters discussed below without tagging others.
OTHER TECHNICAL MATTERS:
You mentioned embedding images in CSS via #dataURLs yes? Will you consider testing this in Tor browser and FOSS browsers generally first?.
Maybe an #imageMap will work better (for all users). Then depending on the icon you want to use you offset the background image in a ':before' element?
There's a way to address this server-side and we think it would likely improve UX. If updating ticker, maybe think about going server-side?
Congrats on producing a non-Cloudflare option, @weepjp. We look forward to seeing good instances like qoto using it?
In what places other than login page does qoto use hCaptcha? Maybe a FOSS and non-proprietary #captcha can remedy this?
We only use it for registration, not needed for login. Didnt know it was cloudflare based though.
I will look into switching to the non-cf version of the ticker for the next update. I am ok switching captchas too if someone wants to submit a pr, i didnt implement the captcha code myself.
It seems that another person made something similar.
> Which instances are currently running it?
Display ticker list:
Custom server (Req ranking): https://miyon.miyon.org/@InstanceTicker/107271136119363709
I have no knowledge of Tor.
I can't improve for Tor.
From now on, if you have a lot of questions and requests, I will close #InstanceTicker.
I am not as vigilant about it as you. Like i do try to avoid it on any services i host, mostly because i know some of my community cares and i want them to feel safe and protected. But its not a big fight for me other than avoiding them where i can. Like i dont invest much time in spreading the word and all the things that a more active person like yourself might do. For me its just common sense to avoid it.
QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.