#2213 closed defect (wontfix)

Restore open4you home page link

Reported by: lg Owned by: zzz
Priority: minor Milestone: n/a
Component: apps/console Version: 0.9.34
Keywords: User-friendliness Cc:
Parent Tickets:

Description

I protest against the removal of the website "open4you - i2p web hosting" from the section Hidden Services of Interest.

At the meeting on April 3, 2018, where I was not present, the following reason was given:

<zzz> 4) Proposed removal of open4you.i2p and git.repo.i2p from console home page (anonymousmaybe)
<zzz> ok anonymousmaybe reports that those two sites have been down for weeks or months and recommends that they be removed from the router console

This was not contradicted, but the truth content was also not investigated.

Already before it came to individual inquiries to the accessibility of open4you. However, it turned out that the accessibility differs from node to node:

i2p.log:[Freitag, 23. März 2018] [11:55:27 CET] <tmpuser> strange. cannot connect http://open4you.i2p/
i2p.log:[Freitag, 23. März 2018] [12:00:39 CET] <trolly> do not use open4you tmpuser, I would not trust it
i2p.log[Freitag, 23. März 2018] [12:18:51 CET] <trolly> I used open4you many years ago, and weird things happen then
i2p.log:[Freitag, 23. März 2018] [12:57:05 CET] <MuadDib?> http://inr.i2p/search/?q=open4you.i2p

I don't want to believe at first that the unfounded gossip from the rumour mill has been included in the decision.

After all, we have two search tools at our disposal:

Besides, I can't understand why this thing is going through in such a hurry if on the other hand definitely dead links remain on the I2P web pages for years.

Open4you is online since January 2014, a long time for local conditions, if necessary short interruptions should be considered. Unless an important reason can be given, this error must be corrected.

Subtickets

Change History (11)

comment:1 Changed 14 months ago by zzz

  • Milestone changed from undecided to 0.9.35
  • Owner changed from str4d to zzz
  • Status changed from new to accepted

ok, looks like it's back up, I'll add it back for 0.9.35 if it stays up.
I did check it several times over the preceeding weeks to verify it was down as reported, so it was "investigated".

comment:2 follow-up: Changed 14 months ago by anonymous maybe

i want to comment on this subject.Actually its not recommended ever to keep one service which is not working or functioning inside I2Pconsole why?

because this is effect i2p image for new comers, giving bad sign that i2p is semi dead or their developers r too blind or lazy or no big community behind it...etc. and we dont forget that these website r popping up for all users once they run i2p inside any platform for the first time. So allowing websites to be there for facial reason is really have bad influence to i2p.

I also want to disagree on rebacking servers which r dead for long time and came back again just because someone noticed oh hey its back again! , why not ?

because there is a possibility that the original server went to be unmaintained so a hacker hacked the server and used it to target the new users who thinks that the server back for good.Or actually the server back again but actually no more maintainer behind it anymore ..etc. so my suggestion is that the admin of the server request a new order inside zzz forum then the request reviewed by him & the community and later deciding to add the server back or not. by that we make sure at least one of the ppl who are working on the server is still alive.

in the end i dont want to make it a fight , but i hope this is the last time that we allow a dead server getting back to the list by us. it should be by the server admin requesting that again.

Regards,

Last edited 14 months ago by anonymous maybe (previous) (diff)

comment:3 in reply to: ↑ 2 Changed 14 months ago by lg

Replying to anonymous maybe:

i want to comment on this subject.Actually its not recommended ever to keep one service which is not working or functioning inside I2Pconsole why?

You can't break the rules[1] that easily. Once a website has been accepted, it requires valid reasons that lead to exclusion. In this case it would be the documentation of downtime over a longer period of time. And there must certainly be no suspicion that people are mumbling behind closed doors.[2] Simply ignoring the principles of togetherness and moving straight to "why" is not honest.

By the way, we have the same interest, only our approach is different.

[1] http://zzz.i2p/topics/236-how-to-get-my-eepsite-added-to-the-router-console-home-page
[2] http://zzz.i2p/search?type=posts&query=open4you&commit=Search

comment:4 follow-up: Changed 14 months ago by zzz

It's not clear whether the OP is the operator of the site or not. Would you please let us know. Also, it would be helpful to get a report from the operator of open4you:

  • was the site down for an extended period of time or not?
  • if so, how long and why, and have the issues been resolved?

comment:5 in reply to: ↑ 4 Changed 14 months ago by lg

Who should be meant by OP (original poster, I guess)? – I have already written to the operator, at least until her statement, the procedure for reversing the burden of proof should be postponed.

comment:6 Changed 14 months ago by anonymous maybe

so then its better to wait for the operator reply if no reply then its simply dead service. and by just being hanging online again doesnt give legitimacy to prove its functioning again.

Hope the admin/operator will answer.

comment:7 Changed 13 months ago by lg

Final report. I wrote to the operator again at the beginning of this discussion and have received no reply to date.

My personal views on a hoster, who is not available even after a long weekend, should not play a role here. The rules established by the project (zzz in person) are decisive. Finally I can only emphasize once more that the pages of the operator were continuously accessible for me.

Basically I consider the mixing of project pages and external service providers on the router homepage and the recommendations made by the project as questionable. Especially because the project makes the pages its own by mixing them and not distancing itself from them. It is also not the task of project management to be the referee on "bad stuff" or "really bad stuff". (What's that supposed to be, what's tax evasion, for example, is that okay?) External providers are clearly separated from the project, including disclaimer. Better still, in order to rule out a competitive advantage, external providers should regulate this among themselves.

If the management wants to do something good for the project, they set up a search engine.

comment:8 Changed 13 months ago by Reportage

As has been suggested before, adding the option to categorize links to allow sorting by sub-section would address some of lg's issues by allowing separation of official and unofficial links. A symbol overlay that indicates the category would further enhance the sub-category classification.

In terms of the overall impression the homepage gives, and its usefulness, as a list of console and external links it's not a very compelling introduction to I2P. The majority of the eepsites listed are technical in nature and only reinforce the notion that I2P is, by and large, an academic exercise without much in the way of an active community. planet.i2p, which has the potential to showcase I2P content, does more to showcase Tor updates, and otherwise serves as a bug report and torrent feed, and that's when it's available (currently down).

Sub-categories aside, adding the ability to pull curated lists of links from 3rd parties, with the ability to embed icon links that are then imported into a sub-dir in the themes directory, might go some way to improving the usefulness of the sites of interest section.

comment:9 Changed 12 months ago by zzz

tested several times today, got 'connection reset'

comment:10 Changed 12 months ago by echelon

tested several times, no connections today, aka down.
No need to (re)add a service which is down.

comment:11 Changed 11 months ago by zzz

  • Milestone changed from 0.9.35 to n/a
  • Resolution set to wontfix
  • Status changed from accepted to closed

still down

Note: See TracTickets for help on using tickets.