| Age | Commit message (Collapse) | Author |
|---|
|
It turns out that moving to Rizon's IRC network was a bad idea after
all. One or more developers (myself included) are unable to connect to
Rizon for using Tor or operating Tor exits.
Now there's this split: Users and Pomf site maintainers are on #pomfret
on Rizon (where I don't have frequent access) and development has moved
back to #pomf on Partyvan (where there's also #/g/hostingtalk).
Given how I personally play such a big role in leading Pomf development,
it has no longer been practical to continue development communication on
an IRC network I can't access. There was no interest to finish setting
up a mailing list for Pomf development because IRC was considered more
important.
Thus, the stagnation and stalled development of pantsu/pomf between
2016-01-31 and 2016-04-30 as seen in commit logs.
There used to be an IRC channel called #pantsucat on Partyvan's IRC
network, before development moved to Rizon. That channel is no longer
active.
See: pantsu/pomf@5846ba7ccb1aa6af2850b3fcf34c6bd396995161
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
|
|
Reword the "no Git issue tracking" policy in contributing section.
Previously the contributing section in README.md would say we don't use
git.pantsu.cat's issue tracker to track issues. That Git service
repository's issues have been disabled today, so we might as well say we
don't use any Git service issue tracking. Unofficial mirrors like the
one on notabug.org may still have issue tracking, which I believe we
have no control over.
This commit also clarifies that we do it for ethical and technical
objections. (In short, it's because the Git service is centralized and a
walled garden.) For more information, see
wubthecaptain/deathwatch-pomf@fc86cbf for information why.
|
|
Me and antonizoon have decided to create a new central channel for
Pomf.se clone discussion. This leaves #/g/hostingtalk dedicated to its
intended purpose, general server hosting discussion.
The channel name #pomfret comes from ArchiveTeam's EFnet channel of the
same name, which was used to rescue Pomf.se's files. The channel on
EFnet is without OPs these days. antonizoon also suggested lots of
imageboard/chan channels are also on Rizon, so Rizon was chosen for the
channel as a good fit. Rizon also houses the #bibanon channel, which is
the official channel for Bibliotheca Anonoma.
OK ewhal@
|
|
The link to real world example at Pantsu.cat is not semantically a
feature, but its own demonstration. Adding a subheader for the example
increases semantics further, and makes it easier to find.
|
|
The README.md lacks a features section, which is worthful for those
searching for a suitable file sharing platform to host.
This change lists the features and seperates "Requirements" to its own
section.
Worthy read: "How to Write a Readme Worth Reading" by Diana Thayer.
https://orchestrate.io/blog/2014/07/16/how-to-write-a-readme-worth-reading/
|
|
Thanks to alchimist@ for doing editorial review.
|
|
The previous example can create a feeling of worry in the mind of the
reader. This will aim to fix that.
|
|
We use IRC for code review, so naturally merge requests also happen
there.
|
|
|
|
Worthy read: "Top ten reasons why I won’t use your open source project"
by Adam Stacoviak.
https://changelog.com/top-ten-reasons-why-i-wont-use-your-open-source-project/
|
|
It seems neku doesn't have a working HTTPS website anymore. It certainly
used to.
|
|
|
|
This also adds a mention of the IRC channel.
Worthy read: "Readme Driven Development" by Tom Preston-Werner:
http://tom.preston-werner.com/2010/08/23/readme-driven-development.html
|
|
A punctuation mark always precedes e.g. In American English a comma
should follow e.g. The list of examples following e.g. should not be
exhaustive.
Reference: https://en.wiktionary.org/wiki/e.g.
|
|
.example is a reserved domain name intended to be used for
documentation, defined in RFC 2606. The purpose is to reduce the
likelihood of conflict and confusion.
OK ewhal@
|
|
Ciro Santilli's Markdown Style Guide advises to mark these as code.
|
|
English nouns begin with an indefinite article "a" or "an". Usually "a"
is used when the word that follows starts with a consontant, and "an"
is used when the word that follows starts with a vowel.
The word "attacker" starts with a vowel and has no different
pronunciation of the first letter, so the correct indefinite article to
use is "an". The correct way to pronounce it is "an attacker".
This fixes an error introduced in commit db66648.
|
|
MIT has used many licenses for software. Calling this project to be
available under a "MIT" license is misleading.
|
|
Fenced code blocks are not part of the original markdown standard, thus
less portable. Even if fenced code blocks were used, they should specify
the code language with it.
Indented code blocks with 4 spaces are portable, which we prefer.
|
|
|
|
|
|
|
|
The moe panel is more of an extension of the core, but not necessary for
Pomf's functionality. The code also suffers from bad practices and it's
more of a prototype. The panel is also mostly unmaintained by its
author.
This code will be in a seperate Git repository called pomf-moe from now
on.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Remove an 's' (damn random plurals)
|
|
Add some info about how to enable gzip compression on Apache servers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
