RE: been away long time need some pointers
(Dec. 26, 2013 07:48 PM)JJoe Wrote: [ -> ]I'm thinking about considerable changes to make maintaining and learning easier.
It seems that you've accumulated ideas. What criteria are you using in this goal?
I think maintenance and learning ease would help me.
When both Sidki and Grypen were maintained, I found Sidki about as usable, but I chose Grypen. So I learned with Grypen's filters (actually from many authors)
Then Sidki become the maintained set.
Since Grypen stopped maintaining, including since you've taken on the set, I've tried switching to Sidki but it's immediately disappointing for my use and too different. I'd have to merge too many annoyance fixes from years of Grypen.
I'm still using and mutilating a mutilated Grypen set.
Also I think I'm correct about these:
Sidki set filters use short variable names, which are less memorable to me. So imitating, editing, or other modifying is more difficult for me. So learning and maintaining are issues with customized set.
Javascript
(#$@#!!)
Sidki uses more javascript. Noscript (Firefox extension) lets me add local.ptron to noscript whitelist, so noscript lets Firefox run any javascript that Firefox sees from local.ptron.
This doesn't help me when I want to edit or imitate a filter, because I don't know javascript.
I've considered converting some javascript-based filters to pure Proxo filter, but haven't begun converting any.
Javascript is more widely known than Proxo syntax.
Proxo syntax is native to Proxo, but browsers may process javascript efficiently. Maybe we don't care.
If Proxo users want to adapt to the predicament of Web 1035.0 falling into a javascript security/privacy death spiral, then knowing js is required.
Userscripts.org has become a ghost town, so greasemonkey users' work isn't much of a resource for importing into proxo.
One reason for this may be that javascript has become such a mess that some websites break their own scripts.
... which leads me back to Javascript
(#$@#!!)