spaceapi / directory Goto Github PK

View Code? Open in Web Editor NEW

58.0 22.0 166.0 335 KB

The Space API directory, modification through Pull Request

Home Page: https://spaceapi.io/directory/

spaceapi hackerspace

directory's People

Contributors

Stargazers

Watchers

Forkers

dnet muellermartin vspaceone mazxim initlab jomat jon-adair bodems niklaushofer gcmalloc pherjung tasomaniac xhain-hackspace astro chankster enko krav dbrgn dromer melbournemakerspace mart-ffbsee makefu nog3 s3lph suicider berendwouters makespacemadrid frubi profpatsch wattnpapa stevenc99 ansgarschmidt cccc tbnobody alexdor niklasdoerfler jabelone mkfink legion151 franzt peponi h3krn phragment flashfingaz fridtjof sa007 mittelab clonejo fnordeingang elberfeld centzilius dingfabrik crimier luxeria fablab-wue danidask albancrommer ruum42 g5pw mcules jhaand segmentationvault creolis qwaxys royassas cyroxx warddr makerspace-gt madonius maschinendeck dhavlik revspace iooner abitrolly machquadrat c3wien c3re d3vl0per silent88 brodo bene64 alexboegl nalxnet nurdspace lomanic markus-be askarel raumzeitlabor brixel mm-chen cat-ion not7cd d33tah harmoniemand mkmakerspace lesander hacksburg compdecon larssjogreen poweredbysugar

directory's Issues

new url for LeineLab

the url in use for leinelab is not working anymore, please update that to:

http://status.leinelab.org/api/spaceapi.json

thanks

Remove update_spaces.py from Travis config

Currently the update_spaces.py script is run from the TravisCI config:

https://github.com/SpaceApi/directory/blob/master/.travis.yml#L8

Can we remove it? It fetches all spaces, which is not necessary at all. Travis should only validate that the directory itself is valid.

Move this repository back to the SpaceApi organization?

Many thanks to you guys to take care of the space directory while the SpaceAPI project was inactive!

Since then we reactivated the project and would like to keep it alive with a core team consisting of multiple people from multiple hackerspace (https://github.com/orgs/SpaceApi/teams/core).

Would it make sense to move the repository back to the SpaceAPI organization and keep it up to date there? Also would one of you guys want to participate in the SpaceAPI core team?

cc @dbrgn @gidsi

Add documentation about the directory

Currently I can't find documentation about the directory anywhere, not even on how to retrieve the directory. I'm I just blind or is it really not documented anywhere?

Please add Melbourne Makerspace

http://spaceapi.net/new/space/melbourne_makerspace/status/json

That's what we have currently.

remove_unresponsive.py triggers DOS protection on some hosting providers

In some cases, a denial of service protection is triggered when using the remove_unresponsive.py is used.

Currently, it is not clear if this happens due to repetitive scanning, arbitrary user-agent sting or scanning invalid (sub-)urls.

The result is that the hosting provider denies all traffic which looks like an offline server to the scan tool.

See my comment on a commit

Decentralize directory

I would like to propose an addition to the directory to maybe make the repository obsolete in the future and get us out of the picture.

I would leave the directory.json as it is for now, but would like to enable spaces to provide the endpoint file in a standardized place (e.g. https://spacewebsite.com/spaceapi.json, comparable to the robots.txt)

I would also give them the opportunity to change the default either in a meta tag or as an http header on their main site, e.g.

As part of html

<html>
  <head>
    <meta name="spaceapi" content="https://example.com/myspaceapi/status.json">
  </head>
    ...
</html>

As a http header

< HTTP/2 200
< content-type: text/html
< server: nginx
< x-spaceapi-endpoint: https://example.com/myspaceapi/status.json

Also it would be necessary to introduce a new field in the schema, something like this

{
  "connectedTo": [
    "https://chaospott.de",
    "https://example.com",
    "https://chaosdorf.de",
    "https://c3l.lu"
  ]
}

This way we could crawl through the different endpoints and spaces won't have the need to create a pull request (i would like to automatically create pull requests to the ones we find to have them in the static file too).

I would use a default position so spaces won't need to have the endpoint of the space they want to link (it changes sometimes and then they would have old and stale data that would need to be updated), also that would mean that you could add spaces to the list (that you know) and we could automatically add them the moment they provide one.

The static file could become irrelevant and we would have a network instead (the data itself would also be quite interesting), and if this doesn't work everything would kinda like stay the same so the risk is low in my opinion.

Also something like a "meta organization" would be possible in some way too.

It might be easier for people to join since you can contact a space that will add you, you won't need a github account anymore and you don't know how to work with git.

What do you guys think?

spaceapi / directory Goto Github PK

directory's People

Contributors

Stargazers

Watchers

Forkers

directory's Issues

new url for LeineLab

Remove update_spaces.py from Travis config

Move this repository back to the SpaceApi organization?

Add documentation about the directory

Please add Melbourne Makerspace

remove_unresponsive.py triggers DOS protection on some hosting providers

Decentralize directory

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent