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.
2/3… through thousands of instances per toot on the page? A server-side-added 'class' descriptor may help a lot, especially for users whose battery-life is a concern.
At the very least, however it might be safer/more private/faster to serve the tiny file/icons locally?
In it current form, we…2/3
3/3… wonder if the ticker should be opt-in at signup, with a "(note: uses Cloudflare)".
What is the story behind this ticker being on the site? We see it's used on kurage.cc (mentioned in the CSS). Do we know other sites using it?
When im back near some proper internet ill link you to the creator of the tickers so you can ask them. There are quite a few instances that use it.
Reason we cant host the css is because yhe maibtainer updates it fairly often as new instances are added or updates.
We did consider maki g it nondefault but after asking the qoto users the vast majority wanted to keep it as default. That said i think its fair to more prominently notify users that it uses cloudflare in our about page so they can be better informed.
Thanks for your reply.
Yes, stating on the About page that the Ticker is Cloudflare would be is a step forward.
The sheer scale of data that Cf can collect/infer may be high but at least ppl will know.
If anyone wants to "tickr tinkr", a server-side 'class'ification of #InstanceType seems a worthy endeavour.
In considering #selfHost vs Cf, a) does the developer…1/2
2/2… offer files for selfHost? b) when not self-hosting are the remote files integrity-checked (ie 'integrity' attribute)? They should be for when Cf gets attacked (we all know its gonna happen).
It seems the developer updates the CSS every 3-4 months? A script to check for an update each quarter may work well! When #TruthSocial federates though maybe be ready to get that update early :P
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.
At a good internet supply, @freemo? It will be good to know the ticker maker to know the instances using it. Is it @yi0713? When you asked the folks about the ticker and they voted for default, did they know it was Cf-hosted?
Is anyone able to address how on postPages the ticker loaded with JS(?) when JS disabled?
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.
QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.