Hi Krys,
On Mon, 2015-03-09 at 17:23 -0800, Krys Nu wrote:
> I wish to express my interest in working on the above mentioned project. I
> have the required technical skill -PHP- and I am willing tread new grounds.
> I would love to discuss more about the project, what is really expected of
> the s
This has been merged now.
On Sat, 2015-02-21 at 18:27 +0100, hoo wrote:
> Hi Everyone,
>
> just wanted to quickly let you know that MediaWiki will verify that
> extensions register all rights they define in $wgAvailableRights (or
> using the "UserGetAllRights" hook).
>
> To make sure your exten
I think pretty much anything is better than the current situation. I'd
support this proposal.
The timing is right too with the WMF vs NSA lawsuit just happening.
On Mon, Mar 16, 2015 at 1:29 AM, Arlo Breault
wrote:
> I share Risker’s concerns here and limiting the anonymity
> set to the inters
On Wed, Mar 11, 2015 at 9:10 AM, Chris Steipp wrote:
> Setting up a proxy like this is definitely an option I've considered. As I
> did, I couldn't think of a good way to limit the types of accounts that
> used it, or come up with an acceptable collateral I could keep from the
> user, that would
On 2015-03-16 2:30 PM, Gergo Tisza wrote:
> On Wed, Mar 11, 2015 at 9:10 AM, Chris Steipp wrote:
>
>> Setting up a proxy like this is definitely an option I've considered. As I
>> did, I couldn't think of a good way to limit the types of accounts that
>> used it, or come up with an acceptable coll
On Mon, Mar 16, 2015 at 2:30 PM, Gergo Tisza wrote:
> Well, the obvious collateral is always money; and with bitcoin going
> mainstream, untraceable money transfers are now accessible even to
> nontechnical users (although I don't know Not sure if the mere act of
> buying bitcoins could endanger
LiquidThreads (LQT) has not been well-supported in a long time. Flow
is in active development, and more real-world use-cases will help
focus attention on the higher-priority features that are needed. To
that end, LQT pages at mediawiki.org will start being converted to
Flow in the next couple of we
How about just converting those threads back to Wikitext, instead? That
script already exists, I've seen it used on Mediawiki. Will it mess up the
pages that have already been converted using that script?
Bottom line, it makes no sense to replace software that was considered
barely suitable when
Fiayy!
So happy to hear this is happening :)
On 16 Mar 2015 17:52, "Nick Wilson (Quiddity)"
wrote:
> LiquidThreads (LQT) has not been well-supported in a long time. Flow
> is in active development, and more real-world use-cases will help
> focus attention on the higher-priority features
On Mon, Mar 16, 2015 at 6:02 PM, Risker wrote:
> How about just converting those threads back to Wikitext, instead? That
> script already exists, I've seen it used on Mediawiki. Will it mess up the
> pages that have already been converted using that script?
>
> Bottom line, it makes no sense to
On 16 March 2015 at 21:20, Ryan Lane wrote:
> On Mon, Mar 16, 2015 at 6:02 PM, Risker wrote:
>
> > How about just converting those threads back to Wikitext, instead? That
> > script already exists, I've seen it used on Mediawiki. Will it mess up
> the
> > pages that have already been converted
At the end of the day, the key is communicating with communities to work
things out with them - and that may well have to happen on a
project-by-project basis. Finding a mid-size project with a very active
admin corps that would be willing to try out whatever you folks come up
with is probably a p
On Mon, Mar 16, 2015 at 6:02 PM, Risker wrote:
> How about just converting those threads back to Wikitext, instead? That
> script already exists, I've seen it used on Mediawiki. Will it mess up the
> pages that have already been converted using that script?
>
> Bottom line, it makes no sense to r
On Mon, Mar 16, 2015 at 5:08 PM, Daniel Friesen
wrote:
> Bitcoin is not untraceable.
>
> An adversary capable enough to eavesdrop on dissidents' communication
> making them need Tor should be capable of tracing the publicly available
> bitcoin transaction logs back from the payment to the proxy o
Hi All,
I am Dibya Singh and I am applying for FOSS Outreachy 10. I have selected a
project from #possible-tech-projects list named One stop translation to
improve consistency for translation. I have been in contact with mentor
Niklas Laxström and Federico Leva alias for understanding the project
On 2015-03-16 7:55 PM, Gergo Tisza wrote:
> On Mon, Mar 16, 2015 at 5:08 PM, Daniel Friesen
> wrote:
>
>> Bitcoin is not untraceable.
>>
>> An adversary capable enough to eavesdrop on dissidents' communication
>> making them need Tor should be capable of tracing the publicly available
>> bitcoin t
I fully upport and welcome this, but at least for Project:Support_desk you
should communicate this on this LQT board, too, that it will be converted (if
you didn't do hat already, i haven't looked now, because LQT ist terrible on
mobile :P). There are probably very active supporters, who haven't
Nick Wilson (Quiddity) schreef op 2015/03/16 om 17:51:
LiquidThreads (LQT) has not been well-supported in a long time. Flow
is in active development, and more real-world use-cases will help
focus attention on the higher-priority features that are needed. To
that end, LQT pages at mediawiki.org wi
Nick Wilson (Quiddity) schreef op 2015/03/16 om 19:03:
On Mon, Mar 16, 2015 at 6:02 PM, Risker wrote:
How about just converting those threads back to Wikitext, instead? That
script already exists, I've seen it used on Mediawiki. Will it mess up the
pages that have already been converted using
Pardon me if I missed an announcement, but will there be any office hours
about Flow in the near future? I have a few general questions about
cross-wiki discussions and the relationship of Flow to VE. (I'm mostly
focused on VE right now.)
Thanks,
Pine
On Mar 16, 2015 11:21 PM, "Kevin Wayne William
20 matches
Mail list logo