Comments (12)
Forgot to say that you are only required to store and make your source code accessible if you modified the original project (with the exceptions noted in the OP). If your public instance runs vanilla code* then you don't have to store it and the Source Code link can point to the original project.
***** If my public instance is a non-modified copy of a modified Searx public instance AGPLv3 compliant (such as search.privacytools.io), my instance's code is considered vanilla so there is no need in storing it and changing the Source Code link.
<script type="text/javascript">
var _paq = window._paq || [];
/* tracker methods like "setCustomDimension" should be called before "trackPageView" */
_paq.push(['trackPageView']);
_paq.push(['enableLinkTracking']);
(function() {
var u="https://stats.privacytools.io/";
_paq.push(['setTrackerUrl', u+'matomo.php']);
_paq.push(['setSiteId', '2']);
var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
})();
</script>
<noscript><p><img src="https://stats.privacytools.io/matomo.php?idsite=2&rec=1" style="border:0;" alt="" /></p></noscript>
it looks very poor!!!
from searx-instances.
Btw @nibbleidea privacytools.io openly states in their Privacy policy that they do track you. Ironic I know 🤦
from searx-instances.
This makes sense but for some instance, only one image and one CSS file are different. I don't know if it can considered as publication, since the browser downloads it ?
Some instances have published a link to their source code at the bottom of the index page, for example https://spot.ecloud.global/
An idea:
- the settings.yml (in searx) configuration file contains a link to the source code.
- the theme uses that settings to display the right URL for "source code"
- the /config URL contains the source code URL ( should be in https://spot.ecloud.global/config for the spot.ecloud.global instance)
Then searx-stats2 can fetch this information and display it.
Brain storming / enhancement: searx.space could clone the git repository and compare
from searx-instances.
According to the license, you have to publish the full source code if you modify or add anything (except in the case of non-specific secrets as stated before).
I understand that it would be a PITA having to store separately the full source code if you change only one color from a CSS sheet (and make sure it stays up to date with any other modifications), but this is the way the license works.
Though it may seem that storing just a diff in your instance (and presenting it as Source Code) will yield the same result while saving space and being more convenient when tracking the changes, there is an issue in this approach: If my modified Searx instance is based on another Searx instance and the latter goes down, my modified Searx instance would have a diff file that might fail when applying it to vanilla code. This is assuming that the diff file was created from the changes made to code from a non-vanilla public instance. But even if we decide to create a diff based on vanilla code, it may happen that the vanilla code disappears or changes, thus having the same problem as before.
So the code should be stored in its completion and should be publicly accessible.
from searx-instances.
Also I believe that searx.space, apart from comparing the public instance's code with the vanilla code, it should also compare the stored instance's code with the actual webpage presented by the public instance to prevent people from lying or forgetting about updating their public source code.
from searx-instances.
By the way, I suggest that an announcement or something should be presented on https://github.com/dalf/searx-instances requiring the public instances to be compliant with the AGPLv3 license, and contact the public instance owners listed on searx.space asking them to make their source code public within a month (for example) or their instances will be removed from searx.space for violating the license.
from searx-instances.
Forgot to say that you are only required to store and make your source code accessible if you modified the original project (with the exceptions noted in the OP). If your public instance runs vanilla code* then you don't have to store it and the Source Code link can point to the original project.
* If my public instance is a non-modified copy of a modified Searx public instance AGPLv3 compliant (such as search.privacytools.io), my instance's code is considered vanilla so there is no need in storing it and changing the Source Code link.
from searx-instances.
@nibbleidea care to explain your quote? I am not affiliated with privacytools.io nor I did write that code :)
from searx-instances.
@nibbleidea care to explain your quote? I am not affiliated with privacytools.io nor I did write that code :)
this code is tracking users
from searx-instances.
this code is tracking users
I saw it but what does it have to do with what I said?
from searx-instances.
any update?
from searx-instances.
About new instances:
- See : https://asciimoo.github.io/searx/dev/makefile.html?highlight=brand#makefile-setup
- GIT_URL is exposed in
/config
: a public API in each searx instance. - Related to searxng/searx-space#34
About the existing instances, this is issue is related to dalf#45
from searx-instances.
Related Issues (20)
- Edit https://start.paulgo.io
- Add https://putin.agency
- Delete https://searx.monicz.pl/
- Add https://search.fedi.life
- Edit searx.prvcy.eu
- Add https://searx2.zackptg5.com
- Add https://searx.theanonymouse.xyz
- Add https://www.webrats.com
- Edit https://www.webrats.com HOT 2
- Add https://search.modalogi.com HOT 4
- Add https://sx.catgirl.cloud/
- Add http://4n53nafyi77iplnbrpmxnp3x4exbswwxigujaxy3b37fvr7bvlopxeyd.onion
- Add http://searxbgetrkiwxhdwi6svpgh7eotopqyxhbqiokrwzg7dcte44t36kyd.onion/ HOT 2
- Edit https://searx.tiekoetter.com
- https://searx.akusov.xyz HOT 8
- Delete https://searx.silkky.cloud HOT 2
- Add https://searx.sadblog.xyz HOT 2
- Delete https://searx2.zackptg5.com
- Add https://serx.cf HOT 1
- Add https://swivro.net HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from searx-instances.