Welcome to the staging ground for new communities! Each proposal has a description in the "Descriptions" category and a body of questions and answers in "Incubator Q&A". You can ask questions (and get answers, we hope!) right away, and start new proposals.
Are you here to participate in a specific proposal? Click on the proposal tag (with the dark outline) to see only posts about that proposal and not all of the others that are in progress. Tags are at the bottom of each post.
Post History
I don't think this is realistic. How many companies still honor contracts from 1923? There's no way to guarantee that it will survive through all the possible mergers, acquisitions, bankruptcies...
Answer
#3: Post edited
- I don't think this is realistic.
- * How many companies still honor contracts from 1923? There's no way to guarantee that it will survive through all the possible mergers, acquisitions, bankruptcies, wars, and countless others calamities.
- * If you are doing periodic renewals, it would be difficult to set up a simple, "passive" way of storing the funds (consider inflation as well, or currency changes like Franc to Euro).
- * Automated renewals would run into issues as the registrar's interface is bound to change.
- * Web technologies will evolve and make your site unusable. For example, 20 years ago HTTP was largely acceptable. Today, browsers are beginning to even blanket-refuse non-TLS sites. In 2043, who knows what will change?
* Internet infrastructure may change too dramatically that a continuation of present day hosting arrangements will be impractical.* The internet may be replaced by some other network.- I think your best bet would be to do what some private landmarks/museums do: Establish an estate/trust to provide funds, appoint some sort of officer (a lawyer) to periodically renew the domain, and possibly authorize him to hire IT professionals to update the website. All this will not be cheap, and you will have a good amount of work to do on writing instructions that are at least somewhat robust to the above risks, but if you really need the website to be up in 2123, I would say that this is the way.
- I don't think this is realistic.
- * How many companies still honor contracts from 1923? There's no way to guarantee that it will survive through all the possible mergers, acquisitions, bankruptcies, wars, and countless others calamities.
- * If you are doing periodic renewals, it would be difficult to set up a simple, "passive" way of storing the funds (consider inflation as well, or currency changes like Franc to Euro).
- * Automated renewals would run into issues as the registrar's interface is bound to change.
- * Web technologies will evolve and make your site unusable. For example, 20 years ago HTTP was largely acceptable. Today, browsers are beginning to even blanket-refuse non-TLS sites. In 2043, who knows what will change?
- * Internet infrastructure may change too dramatically that a continuation of present day hosting arrangements will be impractical. For example, what if in 10 years everyone decides to start using [Gemini](https://en.wikipedia.org/wiki/Gemini_(protocol)) instead? (They won't, but it's just an example)
- * The internet may be replaced by some other network. For example, what if we start using wifi meshes instead of traditional internet infrastructure?
- * It is very difficult to devise security measures that would be robust on such a long time. There is a high risk that after a while, hackers would use currently unknown exploits to take over your valuable domain and/or website.
- I think your best bet would be to do what some private landmarks/museums do: Establish an estate/trust to provide funds, appoint some sort of officer (a lawyer) to periodically renew the domain, and possibly authorize him to hire IT professionals to update the website. All this will not be cheap, and you will have a good amount of work to do on writing instructions that are at least somewhat robust to the above risks, but if you really need the website to be up in 2123, I would say that this is the way.
#2: Post edited
- I don't think this is realistic.
- * How many companies still honor contracts from 1923? There's no way to guarantee that it will survive through all the possible mergers, acquisitions, bankruptcies, wars, and countless others calamities.
* If you are doing periodic renewals, it would be difficult to set up a simple, "passive" way of storing the funds (consider inflation as well).- * Automated renewals would run into issues as the registrar's interface is bound to change.
- * Web technologies will evolve and make your site unusable. For example, 20 years ago HTTP was largely acceptable. Today, browsers are beginning to even blanket-refuse non-TLS sites. In 2043, who knows what will change?
- * Internet infrastructure may change too dramatically that a continuation of present day hosting arrangements will be impractical.
- * The internet may be replaced by some other network.
- I think your best bet would be to do what some private landmarks/museums do: Establish an estate/trust to provide funds, appoint some sort of officer (a lawyer) to periodically renew the domain, and possibly authorize him to hire IT professionals to update the website. All this will not be cheap, and you will have a good amount of work to do on writing instructions that are at least somewhat robust to the above risks, but if you really need the website to be up in 2123, I would say that this is the way.
- I don't think this is realistic.
- * How many companies still honor contracts from 1923? There's no way to guarantee that it will survive through all the possible mergers, acquisitions, bankruptcies, wars, and countless others calamities.
- * If you are doing periodic renewals, it would be difficult to set up a simple, "passive" way of storing the funds (consider inflation as well, or currency changes like Franc to Euro).
- * Automated renewals would run into issues as the registrar's interface is bound to change.
- * Web technologies will evolve and make your site unusable. For example, 20 years ago HTTP was largely acceptable. Today, browsers are beginning to even blanket-refuse non-TLS sites. In 2043, who knows what will change?
- * Internet infrastructure may change too dramatically that a continuation of present day hosting arrangements will be impractical.
- * The internet may be replaced by some other network.
- I think your best bet would be to do what some private landmarks/museums do: Establish an estate/trust to provide funds, appoint some sort of officer (a lawyer) to periodically renew the domain, and possibly authorize him to hire IT professionals to update the website. All this will not be cheap, and you will have a good amount of work to do on writing instructions that are at least somewhat robust to the above risks, but if you really need the website to be up in 2123, I would say that this is the way.
#1: Initial revision
I don't think this is realistic. * How many companies still honor contracts from 1923? There's no way to guarantee that it will survive through all the possible mergers, acquisitions, bankruptcies, wars, and countless others calamities. * If you are doing periodic renewals, it would be difficult to set up a simple, "passive" way of storing the funds (consider inflation as well). * Automated renewals would run into issues as the registrar's interface is bound to change. * Web technologies will evolve and make your site unusable. For example, 20 years ago HTTP was largely acceptable. Today, browsers are beginning to even blanket-refuse non-TLS sites. In 2043, who knows what will change? * Internet infrastructure may change too dramatically that a continuation of present day hosting arrangements will be impractical. * The internet may be replaced by some other network. I think your best bet would be to do what some private landmarks/museums do: Establish an estate/trust to provide funds, appoint some sort of officer (a lawyer) to periodically renew the domain, and possibly authorize him to hire IT professionals to update the website. All this will not be cheap, and you will have a good amount of work to do on writing instructions that are at least somewhat robust to the above risks, but if you really need the website to be up in 2123, I would say that this is the way.