State of Maranhão and Piauí

The State of Maranhão and Piauí (Portuguese: Estado do Maranhão e Piauí) was one of the states of the Portuguese Empire.

State of Maranhão and Piauí

Estado do Maranhão e Piauí
1772–1775
Flag
Coat of arms
StatusState of the Portuguese Empire
CapitalSão Luís
Common languagesPortuguese
Religion
Roman Catholicism
GovernmentMonarchy
Monarch 
 1772–1775
Joseph I
Governor General 
 1772–1775
Joaquim de Mello e Póvoas
History 
 Established
1772
 Disestablished
1775
CurrencyPortuguese Real
Preceded by
Succeeded by
State of Grão-Pará and Maranhão
State of Brazil

History

The state was created in 1772 by order of Sebastião José de Carvalho e Melo, 1st Marquis of Pombal, the Secretary of the State for Joseph I of Portugal.[1]

The state was created because of the economic success of the State of Grão-Pará and Maranhão. Sebastião José de Carvalho e Melo split that state into two states, the State of Grão-Pará and Rio Negro and the State of Maranhão and Piauí, thinking that this would cause even better economic conditions, though the state split would prove a failure.

In 1775, due to the failure of the new state, both the State of Grão-Pará and Rio Negro and the State of Maranhão and Piauí were merged into the State of Brazil, finally unifying Portuguese America into one colony.

gollark: Thusly, git.osmarks.net is C.
gollark: > Allows visitors to look and download without authenticating. (A+0)Yes.> Does not log anything about visitors. (A+1)No. Your IP and user agent are logged for purposes.> Follows the criteria in The Electronic Frontier Foundation's best practices for online service providers. (A+2)> Follows the Web “Content” Accessibility Guidelines 2.0 (WCAG 2.0) standard. (A+3)> Follows the Web Accessibility Initiative — Accessible Rich Internet Applications 1.0 (WAI-ARIA 1.0) standard. (A+4)Probably not.> All data contributed by the project owner and contributors is exportable in a machine-readable format. (A+5)No idea. There might be an API.
gollark: > All important site functions work correctly (though may not look as nice) when the user disables execution of JavaScript and other code sent by the site. (A0)I think they *mostly* do.> Server code released as free software. (A1)Yes.> Encourages use of GPL 3-or-later as preferred option. (A2)> Offers use of AGPL 3-or-later as an option. (A3)> Does not permit nonfree licenses (or lack of license) for works for practical use. (A4)See above. Although not ALLOWING licenses like that would be very not free.> Does not recommend services that are SaaSS. (A5)Yes.> Says “free software,” not “open source.” (A6)Don't know if it says either.> Clearly endorses the Free Software Movement's ideas of freedom. (A7)No.> Avoids saying “Linux” without “GNU” when referring to GNU/Linux. (A8)It says neither.> Insists that each nontrivial file in a package clearly and unambiguously state how it is licensed. (A9)No, and this is stupid.
gollark: > All code sent to the user's browser must be free software and labeled for LibreJS or other suitable free automatic license analyzer, regardless of whether the site functions when the user disables this code. (B0)Nope!> Does not report visitors to other organizations; in particular, no tracking tags in the pages. This means the site must avoid most advertising networks. (B1)Yes, it is entirely served locally.> Does not encourage bad licensing practices (no license, unclear licensing, GPL N only). (B2)Again, don't think gitea has this.> Does not recommend nonfree licenses for works of practical use. (B3)See above.
gollark: > All important site functionality that's enabled for use with that package works correctly (though it need not look as nice) in free browsers, including IceCat, without running any nonfree software sent by the site. (C0)I think so. Definitely works in free browsers, don't know if it contains nonfree software.> No other nonfree software is required to use the site (thus, no Flash). (C1)Yes.> Does not discriminate against classes of users, or against any country. (C2)Yes.> Permits access via Tor (we consider this an important site function). (C3)Yes.> The site's terms of service contain no odious conditions. (C4)Yes.> Recommends and encourages GPL 3-or-later licensing at least as much as any other kind of licensing. (C5)I don't think it has much on licensing, so suuuure.> Support HTTPS properly and securely, including the site's certificates. (C6)Definitely.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.