CIRCLE WITH A DOT

Okay, I've incorporated the suggestions and I've got it working on my Dev Server.

So the final product will use human-readable URL parameters, so if it is "?type=group" only the three Group options will be in the dropdown list. And I did something similar for the "Page" and "Personal" options. No/invalid params means it shows the whole list of account type options. Trimming the list and pre-selecting is now handled on the backend in PHP rather than on the front-end with JS.

I'll try to put this together into a PR sometime this weekend.

@marcusxms Nice!

@marcusxms Oh, okay I get it now. I guess I was confusing "endpoint" with "route" and was thinking I needed to create a whole new URL in routes with another PHP page and template. If it's just getting the URL parameters and working with them on the backend that's not a problem. I already wrote JS to do this on the client side so I'll just rewrite that in PHP.

Out of curiosity, is there some particular reason to hide the label on password fields? Both the core and theme field_password.tpl templates have this in them:

{{if $label != false}}
	<label for="id_{{$field.0}}">{{$field.1}}{{if $field.4}} <span class="required" title="{{$field.4}}">*</span>{{/if}}</label>
{{/if}}

It's easy to override it by putting {{assign name="label" value="true"}} before the template call, I just don't understand why it normally hides the password field label?

@marcusxms I can see the value in the URL parameters being human readable rather than a "magic number." Really the only thing I don't like about switching from a number to a string is processing the number into the database takes 2 lines of code while the string requires 36 lines of code (because it needs constants defined first then needs a switch-case to equate it to the numbers).

But that part is all on the backend and invisible to users. The URL params are visible to users in the browser address bar, so should probably be human readable.

@marcusxms I don't really know how to correctly create a new endpoint in Friendica. I assume there's some preferred way of doing it and I'm pretty sure I wouldn't accidentally do it the right way.

Is there any reason I shouldn't be exposing the account type and page flag data on the front-end?

The way I wrote my mod each option has a numerical value. The first digit represents the account type and the second the page flag. So any URL with parameters to auto-select an account type from the dropdown would be like ?type=32.

But it could also be written to use strings for the option values and then equate those to numbers on the backend, so then the URL with params would be like ?type=group.

@andy @marcusxms I don't think "connection request" or "connections" is the way to go with terminology. I think most people are familiar with the terminology of "Friend request" and "Followers" over "connections."

IMO Friendica should really try to use the more common terminology. Which is why I think "nickname" should also be replaced with "handle." "Circles" is probably fine, though "Lists" seem to be the more common term for such a feature. That's what Mastodon calls it. That's what Facebook used to call it, when they had that feature.

@andy @marcusxms Private Groups automatically accept new followers? That doesn't seem right if that's how it works. Shouldn't a private group require manual approval of new members?

@andy I agree with that. I was considering:

• Personal (standard account)
• Personal Soapbox (auto-approve Follow requests)
• Personal Love-all (auto-approve Friend requests)
• Organization Page
• News Page
• Public Group
• Restricted Group
• Private Group (experimental)

Not sure about including the explanations behind Soapbox and Love-all though.

@marcusxms I think I would prefer linking to the help page descriptions rather than putting them in that form. Friendica is too cluttered to begin with, I don't want to clutter it up even more.

@roland Yes it did, thanks!

This was a comment on my other post but I want to raise it as its own issue as to whether this solution addresses the problem of new users not knowing how to create a Page or Group on Friendica?#Friendica @developers
RE: dillyofapickle.com/objects/8aa…

Turn back pengies! Turn back!

sciencenews.org/article/empero…