/next/ - Infinity Next

>>1090

None so far, everything looks like it's going well. Josh, what are your thoughts on the >>1084 thread?

>>1092

Just look up thread migration in the catalog. I assume that your suggested feature is pretty much the same.

Regarding:

1) Yes. No avatars, no flair texts, no fluff. At max that what you described yourself. Imageboard = anon community.

2) sounds great. as long as you can still opt to not have a single account.

also less shekels = work faster ;) I unfortunately already transferred you all my bits. maybe next month I get a few more I can spare

>>1111

>For handling reports I'm a big fan of desuwa's work on improving the 4chan moderation tools. Especially the keyboard shortcuts.

That's pretty good. I like how the actions are so visible. I'll see if I can take anything away from that design.

>For 'interaction', would you be interested in something like automating the installation using vagrant? So people can more easily poke around with their own virtual machine installation, and exposed on localhost?

I've never used Vagrant before and wouldn't know what that entails, but having a very easy installation and setup with as wide a platform as possible is pretty important to me. I was setting up Infinity Next on new servers today (btw https://infinitydev.org is now on its own machines) and was moderately pleased at how easy it was, but documentation definitely needs to be reviewed and expanded upon.

I'll look into Vagrant, I'm familiar with its concept only.

>Haven't gotten around to installing it and poking around yet, but that's what I'm planning on doing this saturday. It looks highly modular.

I try to keep things are abstracted as possible without being cumbersome, but we'll see how it actually plays out. In my experience, when I need to revisit things that are already built, pulling out something and dropping in new code in its place is about as easy as you could hope for.

>>1111

are you running google botnet on apple botnet and gettin quads? well, neat.

isn't using homestead already pretty easy to set up next?

Sorry for lack of updates. I've been spread thin and hit a logical error a few days ago that halted progress.

I've finally sat down and thought out how I want to refactor our permission system to work with 8ch. I was originally modeling the permission system after XenForo and other forums, but the issues come from the Board Owner.

Currently, the software uses a "Yes / Inherit / Never" permission mask. By default, all permissions are Inherit (soft no). As permissions are given at different levels, they allow the user to do more. If a permission mask has a "Never" permission, it overrides all existing and future "Yes" permissions as the mask is compiled.

If the user was "Never" allowed to do something, a Board Owner could tell a Global Administrator that he cannot post on his board. To remedy this, I figured I was going to remove the "Never" permission and only allow additive "Yes" permissions, but that would mean we would have to consider Tor users completely separate from Anonymous users and build the default permission layer twice just to revoke the "Upload an image" permission. This would also mean that board owners couldn't revoke permission to use the Name field, that would have to be mitigated to a board option, which defeats the entire purpose of a staggered permission layer.

I've settled on changing "Yes / Inherit / Never" to "Yes / Inherit / Revoke", and adding weights to each layer of the permission mask. The "Revoke" setting would, instead of never allowing a permission to be set, instead revoke "Yes" permissions given on lower levels.

All users inherit the Anonymous permission mask, and users on Tor inherit the Tor permission mask.

00g - Anonymous

10g - Tor

20g - Janitor

30g - Owner

40g - Moderator

50g - Administrator

If a mask is made custom for a board, it's weight would be +5g. So, for instance, lets say we made this board where namefagging is disabled and tor images are enabled for /pol/.

00g - Anonymous (Global): ALLOW names, ALLOW images.

05g - Anonymous (/pol/): REVOKE names, INHERIT images (inherits allow).

10g - Tor (Global): INHERIT names (inherits deny), REVOKE images.

15g - Tor (/pol/): INHERIT names (inherits deny), ALLOW images (sets on top previous revoke).

20g - Janitor (Global): ALLOW names, ALLOW images.

And this permission for allowing board permissions is constantly reset from this point up so that staff can always post names and images.

I think this is the best possible system for giving granularity to the permission system as well as protecting the staff's ability to do their job. I'm going to write a database upgrade and begin retooling the permission system.

>>1135

Permission masks are very complicated and I didn't do them perfectly in the first month so now I am going back to improve my concepts.

I've gotten the changes done and rebuilt the database seeder considerably so that adding new permissions in the future will be easy.

Tomorrow, I'm going to try something different and build unit tests for this. Unit tests involve writing code that anticipates an output, and then building your code so that it meets those expectations. A lot of people consider this to be cumbersome, as do I, but in the case of the permission masks the concept is so lofty, abstract, and hard to work with, it'll probably be a lot easier with unit tests.

So yeah. This is a little bit frustrating because I'm going a lot slower on this big, important update than i want to be. There's a reason why I put it off for months. Yuck. It's going to turn out really cool, though.

>>1130

>are you running google botnet on apple botnet

no, that's from the /int/cident

>isn't using homestead already pretty easy to set up next?

I wasn't aware of homestead. basically the same thing, although what i'd do is infrastructure automation scripts specific to setting up infinity so it's all documented. that's pretty much the only difference, while homestead is a generic development environment.

Okay, so ...

1. I completely rewrote the permission system. Apparently deleted 1200 lines of code and wrote 1800. Permission masks compile successfully.

2. I clarified some existing permissions and split some out. The permission to post has been split into the permission to make a new thread and a new reply.

Likewise, I have split the permission to post an image to the ability to post a new image and the ability to post an existing image (as recognized by the hash database). By default, users posting under the "unaccountable" mask (Tor users) will be able to upload images that have been once uploaded via the clearnet.

Inversely, a board owner could set upload new to true and upload old to false on everyone and force posters to be more creative.

3. I also fixed an extant issue on 8ch with being able to post the same image multiple times on one post, just cuz I was in the neighborhood.

I think that's about it. I improved the DB seeder a little bit and fixed my severely neglected unit tests in the process of adding unit tests for development of the permission system. I'm now back on to the original task of adding customizable castes to boards, which I should hopefully be able to do tonight.

>>1139

yeap what I think would be easiest is just having a simple script or something that you can run on a vanilla homestead and then everything is set up. that'd be a really fast way to get into developing but also would use the standard laravel container.

>>1157

Looks cool Josh.

I hope you get some funding to finish this off.

Do you have any plan B?

>>1158

It's not like you die directly when your funds run low. Cost of living in Singapore is also not really excessive.

>>1178

I'm in the Philippines. I just use a proxy in either HK/JP/SP because it stops PLDT from fucking with my connection.

>>1156

I like the permissions setup. Very Xenforo looking which is a great system to use.

>>1184

Oh gosh, you know my secret. I borrow a lot of ideas from XenForo because I think it's great.

>>1180

Right. My geography is horrible. I thought Venezuela was an island last week.