×
扫码关注【爱吃馍】
获取最新脚本和技术支持！
关注公众号，获取最新地址
This software renders syndication feeds as XHTML; It supports Atom Activity Streams (Friendica, Nostr, OStatus), Atom Over XMPP (Blasta, Libervia, Movim, Rivista), BitTorrent RSS, JSON Feed, OPML, RDF (DOAP, FOAF, RSS, XMPP), RSS-in-JSON, Simple Machines Forum (SMF), Sitemap, The Atom Syndication Format, and Twtxt; and it also supports navigation (RFC 5005).
< Feedback on Newspaper (Syndication Feed Reader)
It's a bad idea.
Most people don't even want to install a single script, imagine many scripts just for 1 script to work...
I recommend that you remove most comments from your script, like the TODO list. It doesn't make your script better or adds any value, its something personal only for you (the dev).
That would already help reduce the size of the script.
Also, do like my AI everywhere script.
Split .css and .html, etc, into their own pages and store them somewhere, then just call them as resources.
Your userscript should only contain @//resources (a single line in TM) and plain JavaScript or jQuery.
Yes. I intend to separate the CSS, and also to provide a selection of CSS stylesheets to select and configure.
Perhaps a script for syndicated documents (ActivityStreams, Atom, DOAP, OPML, RSS, SMF, and Twtxt), and another for other XML data.
That makes more sense.
But if you split the CSS and HTML and store that somewhere else, I bet that you can leave the full JS in Greasyfork directly.
I might do so, when Falkon would support that function also.
Split extension by formats.
This extension has exceeded 200KB (500KB with 300KB documentations which are attached to it), so I consider to split it into multiple parts, and to set the documentation only to a single version of Atom 1.0, RSS 2.0, and Twtxt.
Should we to split this extension by formats?
et cetera.
@hacker09 What do you think of it?