█ █ █▀█ █ █   █▀▄ ▀▀█     sysInfo    FAQ     HowTo    ToS    contact    signUp 
█ █ █ █ ▄▀▄   █▀▄ ▄▀                               
▀▀▀ ▀ ▀ ▀ ▀ ▀ ▀▀  ▀▀▀                                               users: !
===============================================================================

By creating an account and using UNX.BZ's services you agree to the following Terms of Service, Privacy Policy and Code of Conduct, Culture, Values & Focus. Failure to abide by these terms can result in penalties, including service bans and potential legal action, depending on the severity of the violation. UNX.BZ may investigate suspected violations and will cooperate fully with law enforcement agencies as necessary. Read these terms carefully.

===============================================================================

Terms of Service +

UNX.BZ is open to people 13 years old or older. If you are younger than 13 you may not create an account on UNX.BZ


You are responsible for regularly checking your local mail account. This email address is our primary means of communication and any warnings or notices regarding your account or service status will be sent there.


UNX.BZ is a shared system and as such, users must be mindful to use resources efficiently and with respect for the other users on the system. We monitor usage and habitually abusive usage patterns will not be tolerated. Having said that, we understand there are times when you might need to use a lot of CPU or RAM for some period of time. That's OK provided it is intermittent. The system is MEANT to be used! Just make sure the workload isn't some kind of multi-day job. Minutes, even up to a handful of hours is OK if a task is running "nice". A task that runs more than a handful of hours, hogs a lot of CPU and RAM and thrashes the storage for hours is NOT OK. Using excessive network bandwidth is NOT OK.


Examples of things that are potentially resource intensive but OK

  • Manually compiling complex software
  • Converting / scaling / re-compressing a batch of images for your web page.
  • Processing 1GB of text to reformat it or extract data.
  • Web pages that run a simple PHP or CGI script every time they are hit.


Examples of things that are resource intensive and NOT OK

  • A 3D render that takes days to complete and sucks up all the CPU resources.
  • Cryptocurrency mining.
  • Using the server for bulk data storage and delivery.


There are cases between those extremes of course, and many of them are OK provided the usage is intermittent/transient, you run the tasks as "nice 19" and you don't use excessive network bandwidth.


Exhibiting a pattern of abusive resource usage with no regard for the quality of service to other users will lead to your account being banned.


But wait, there's more!


Prohibited activities include, but are not limited to:

  • Deliberately defacing or tampering with other users' accounts.
  • Intentionally disrupting or attempting to disrupt UNX.BZ's servers.
  • Using UNX.BZ as a platform to attack or disrupt other servers or services.
  • Using UNX.BZ to impersonate websites, individuals, or businesses for malicious or criminal purposes.
  • Hosting or distributing pornography of any type or medium, especially child pornography.
  • Storing, distributing, or promoting content that defames or slanders any individual or entity.
  • Promoting racial, ethnic, religious, political, or other forms of bigotry.
  • Storing, distributing, promoting, or encouraging the use of pirated or cracked software, unauthorized license keys, or any software or scripts intended to bypass security or disrupt network services.
  • Mining cryptocurrencies.
  • Sending spam or unsolicited messages through forums, mailing lists, IRC channels, newsgroups, or other communication channels.
  • Leaking, distributing or publishing private or identifying information about any individual without explicit consent. (Commonly known as "doxxing")
  • Using UNX.BZ services for any illegal activity or purpose.
  • Using UNX.BZ services for commercial purposes or profit-making activities.
  • Running servers or network services (such as web, mail, game, file-sharing, VPN, or proxy servers) without explicit permission.
  • Virtualized/subsystem OSes (docker, junest, vagrant, etc.)
  • Eggdrop (or similar) bots.
  • Reselling or subletting access to UNX.BZ services under any circumstances.
  • Using UNX.BZ storage resources for file backups or bulk data storage.
  • Allowing or contributing to frequent attacks or disruptions targeting your account or hosted content.
  • Sharing your login credentials. One login ID, one user. If you have a friend that wants to use UNX.BZ they can sign up for their own account!
  • "Farming" login IDs. (making more than one login for yousef) One user, one login ID.
  • Usage patterns that disrupt the quality of service for other users of the system. (Inordinate use of CPU, RAM, Storage and/or network resources)


Additional Conditions:

  • UNX.BZ backs up server data routinely but users are responsible for maintaining their own backups of data they care about.
  • Support provided by UNX.BZ is volunteer-based; mutual respect and patience are expected at all times.


Copyright infringement and distribution of illegal content are strictly prohibited. Users must respect copyright laws and obtain explicit permission from content owners or valid license holders before sharing any material. Content hosted for external storage purposes must also comply with all relevant copyright laws.


To request the removal of copyrighted material you own from UNX.BZ, please use the contact page. Clearly identify your relationship to the copyrighted content, specify the exact files or links involved, and provide detailed contact information, including a reply-to email address or phone number.


Repeated or severe violations of these Terms of Service may result in immediate account removal. These terms apply to all communication platforms hosted by or associated with UNX.BZ, including forums, mailing lists, IRC channels, newsgroups, and similar services.


If you notice any violations, please report them through the contact page.


===============================================================================

Privacy Policy +

UNX.BZ collects the minimum amount of data necessary to run a pubnix. We do not do cookie or web tracking but we do collect anonymized access data to generate server usage statistics and to aid in the detection of abuse.


We collect your email address during sign-up and log the IP addresses used to access the system via ssh. We also of course store information related to your system account like your username, password and passwd GECOS entry (which traditionally is used to store a persons real name). Should you decide you want to populate the GECOS entry with your real name, it will be visible to other users logged in to UNX.BZ but not visible via the public web server.


We store any data you create or maintain in your public_html and home directory on the server which will include your .plan file, .project file and emails to and from UNX.BZ


How long do we retain data?

  • Email Addresses: Retained for account management.
  • Login IP addresses: Retained for a maximum of 90 days.
  • Home Dir Data: Retained for the duration of the account life.
  • public_html Dir Data: Retained for the duration of the account life.
  • Server Logs: retained as long as necessary for troubleshooting and abuse detection, typically 30-90 days.


Requesting data deletion

You may submit a deletion request via our contact page from the email address you signed up with. Account deletion will also remove all your data, typically within 14 days.


How do we protect your data?

Data is not encrypted at rest. Access is controlled by standard UNIX file permissions. Users should not store sensitive or confidential information on UNX.BZ

===============================================================================

Code of Conduct, Culture, Values & Focus +

Our Code of Conduct can be summed up in a single sentence: Don't be a jerk. The Terms of Service outline the hard lines around that. This document defines the soft lines. There is a particular culture and set of values we hope to promote.


This community exists so people can learn, tinker, and build cool things together without fear of being judged, talked over, or pushed around. You don’t need to perform an identity, win an argument, or prove anything to belong here. You just need to treat other people with basic respect.


What matters here is how you behave, not who you are. Be curious. Be kind. Be generous with what you know. Disagree without being disagreeable. If something isn’t your thing, it’s okay to quietly skip it.


This is a shared computing work space, not a soapbox and not social media. We value calm, focus, and good manners. Drama, cruelty, harassment, and ideological bullying, of any kind, don’t belong here and won’t be tolerated. Think of this place like a dinner with mixed company: interesting conversations, different viewpoints, and an expectation that everyone knows how to treat others with grace and respect.


In short: don’t be a jerk and help make this a place where people actually want to stick around.


Here is a non-exhaustive list of the things we value:


  • Inclusivity
  • Curiosity
  • Mentorship
  • Autonomy
  • Data sovereignty and privacy
  • Colaboration - This server / site is maintained by volunteers... and YOU!
  • The Unix Philosophy
  • The Hacker Ethic
  • The K.I.S.S. principle (It's just a single FreeBSD server!)
  • The Power of Plain Text
  • Distributed compute systems / grids
  • Computer Graphics / CGI, filmmaking and VFX
  • Making interesting things and sharing them. We are excited to see what you build!
  • ML/AI/LLMs as power tools. Love it or hate it, AI is here to stay. We encourage the use of AI as educational helpers and assistants. But keep using your own brain also!
  • Keeping it short. Short user names and succinct, descriptive file and directory names in the spirit of Unix are encouraged.
  • Keeping it smol. Web pages should be as efficient and light as possible. Stick to text, UTF-8 emojis and thoughtfully compressed images when needed. Not only will it make pages load faster for your guests but it will save bandwidth for the server, which remember is just a single shared Arm based FreeBSD computer on the Internet! It's fine to use CSS and JavaScript provided you keep the payloads from getting bloated. Caddy will also compress text based output as it serves it at runtime but the smaller the payload is to begin with the more compact the compressed version will be.
  • Keeping it interesting. We aren't all about a retro aesthetic here... more about promoting old school pubnix traditions like simple static sites and server side rendering. What can you do even in the face of a few constraints? Feel free to go nuts with CSS and JS. Style your pages however you want. Just keep the payloads from getting bloated and don't expect to host complex MVC apps here. There are other resources for that.

===============================================================================

The Terms and Conditions and Privacy Policy are adapted from thunix.net which are released under CC BY-SA 4.0 license. These modified Terms and Conditions, Privacy Policy and Code of Conduct, Culture, Values & Focus are likewise released under the CC BY-SA 4.0 license.