| 20 Jan 2023 |
 bkil |
here are some things that we don't allow:
- provide any type of public proxy
- routing internet traffic via envs (tunnel/vpn)
| 22:18:23 |
| bkil | *
here are some things that we don't allow:
...
- provide any type of public proxy
- routing internet traffic via envs (tunnel/vpn)
...
| 22:18:32 |
| bkil | *
here are some things that we don't allow:
- ...
- provide any type of public proxy
- routing internet traffic via envs (tunnel/vpn)
- ...
| 22:18:39 |
 Ali | Yup, saw it, but guessed that they reason for this rule might be to avoid abuse.
Anyway, thanks! | 22:19:34 |
| Ali | * Yup, saw it, but guessed that the reason for this rule might be to avoid abuse.
Anyway, thanks! | 22:19:46 |
| bkil | Abuse is prohibited according to different points within the list. | 22:30:08 |
| bkil | But I have a related question, but for a totally different, legitime purpose. Would it be allowed to operate something commonly referred to as a "CORS proxy" on envs if it was only configured to allow access public pages already hosted on envs.net (via GET method)? This would allow for using a webapp to access the twtxt feeds of others. It should not fall under the second mentioned point, as intra-envs traffic is not "internet traffic". However, it might fall under "any type of proxy", although it is not a "public" proxy in the sense that it can't be used to access general things over the internet and it would mostly be useful for envs users, not for the greater public at large. | 22:33:48 |
| bkil | * I also have a related question, but for a totally different, legitime purpose. Would it be allowed to operate something commonly referred to as a "CORS proxy" on envs if it was configured to only allow access (via GET method) to public pages already hosted on envs.net? This would allow for using a webapp to access the twtxt feeds of others. It should not fall under the second mentioned point, as intra-envs traffic is not "internet traffic". However, it might fall under "any type of proxy", although it is not a "public" proxy in the sense that it can't be used to access general things over the internet and it would mostly be useful for envs users, not for the greater public at large. | 22:34:46 |
| bkil | By the way, an even better solution would be to default unauthorized GET of static pages (or at least some sensible things, such as *.txt, *.rss, *.atom, *.ical, *.json, etc.) to access-control-allow-origin: *. Surely, this could also be worked around if a user serves their feed via a dynamic script that just adds this header before cat'ing the txt file, but each and every user must set this up individually (and correctly!) for this to work, and it would also use way more server resources then.
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin
| 22:39:41 |
|  двійка joined the room. | 23:31:46 |
| 21 Jan 2023 |
|  @unnervingduck:envs.net left the room. | 09:58:22 |
| 22 Jan 2023 |
|  braindead joined the room. | 00:07:38 |
|  nullsh changed their profile picture. | 15:10:14 |
| 23 Jan 2023 |
|  @drake:arcticfoxes.net removed their display name drake. | 12:30:22 |
| @drake:arcticfoxes.net removed their profile picture. | 12:31:09 |
|  VideoToaster changed their profile picture. | 21:19:28 |
 RSS | New post in envs's timeline: root | our gitea is now on version 1.18.3 - https://github.com/go-gitea/gitea/releases/tag/v1.18.3
| 23:11:27 |
| 24 Jan 2023 |
|  @spff:tchncs.de left the room. | 11:00:28 |
| VideoToaster changed their profile picture. | 15:36:00 |
| RSS | New post in envs's timeline: welcome new user ~ad044
| 15:46:16 |
| RSS | New post in envs's timeline: welcome new user ~rcenyl
| 15:46:21 |
| RSS | New post in envs's timeline: welcome new user ~luber
| 15:46:25 |
|  DevHONK(Intel 486 SX) changed their profile picture. | 21:16:54 |
| DevHONK(Intel 486 SX) changed their profile picture. | 21:37:28 |
| 25 Jan 2023 |
|  al1f changed their profile picture. | 07:07:13 |
| al1f removed their profile picture. | 07:07:15 |
| al1f set a profile picture. | 07:07:22 |
 Github | [envs-net/0x0] filip2cz starred the repo | 10:55:34 |
| 27 Jan 2023 |
|  @sycamore:nitro.chat left the room. | 07:26:49 |
| Github | [envs-net/0x0] cremesk pushed
1 commit
to
master: | 22:34:55 |
