New Features Added & Suggestions

[allright]

Is it possible to have a preference to show most recent posts in a thread first. I believe Xenforo has that option.

 

[ikeo1]

Hello,

In the menu go to what’s new. You can click on what’s new or new posts.

 

[ikeo1]

One more note,

You can also click New Post on mobile..

 

[allright]

Hello,

In the menu go to what’s new. You can click on what’s new or new posts.

View attachment 7278

ikeo1, I'm looking for a way to open a thread, and the top of the first page will show the most recent post. What you're suggesting doesn't accomplish this, unless there's something I don't understand.

 

[ikeo1]

ikeo1, I'm looking for a way to open a thread, and the top of the first page will show the most recent post. What you're suggesting doesn't accomplish this, unless there's something I don't understand.

I see what you’re saying, click on the date/time of the most recent post. That will take you the latest post in the thread.

If you’re looking for it as a setting, I’ll see if I can find that but I think most services it’ll take you to the beginning instead of the end.

 

[MattS]

Hi,

Couple of items to add to your list.

1. Would it be possible to save a filtered query in a given section of the Classifieds and drive an alert notification for new (unread) posts?

--Example: when a new post happens in the Private Handguns section for the Sacramento sub-region, I would love to get notified on that.

2. Saved searches and notification of new matches. If you could save searches and get a notification of new matches of a saved search, like you can on Autotrader, that would be amazing!

--Example: setup a saved search containing "LTT Elite 92" in Sacramento subregion, then send an alert when a new matching post is listed.

Thanks!

 

[ikeo1]

1. Would it be possible to save a filtered query in a given section of the Classifieds and drive an alert notification for new (unread) posts?

--Example: when a new post happens in the Private Handguns section for the Sacramento sub-region, I would love to get notified on that.

2. Saved searches and notification of new matches. If you could save searches and get a notification of new matches of a saved search, like you can on Autotrader, that would be amazing!

--Example: setup a saved search containing "LTT Elite 92" in Sacramento subregion, then send an alert when a new matching post is listed.

These are both fairly similar. I was working on something like this early on, but paused when traffic died down. There's a lot of development that goes into this and computational power.

As we grow, this is slated as a subscriber benefit because we'll have to scan each listing for keywords in real time. This would not be a free option because the overhead would be very high.

I can't say when this will be released, but it is on the roadmap if this site does well. I can then get this built and already have it spec'd out. It would be relatively simple and limited to a set of keywords to avoid complexity.

Depending on the amount of computation power needed for this another tier might be needed. In the beginning it'll be available to CAsupporters group but again, not anytime soon. Our main goal is to build the community. This feature would be a perk for those who want notification of the best deals first.

 

[MattS]

Yeah, that is a lot of compute that goes into that query, filtering of results and driving an alert workflow off of it. "On the roadmap" - thanks!

 

[allright]

I see what you’re saying, click on the date/time of the most recent post. That will take you the latest post in the thread.

If you’re looking for it as a setting, I’ll see if I can find that but I think most services it’ll take you to the beginning instead of the end.

View attachment 7343

Ikeo1, it's possibly this?

 

[ikeo1]

Ikeo1, it's possibly this? View attachment 7390

I think i get it now. When you click a post you want to sort from latest to oldest vs oldest to latest.. I'm not sure if that's available, but I'll look at it when I can get to it. Not a bad suggestion, but start to finish is standard.

You might be able to do it custom on your filters like you're showing but i think that's for the posts not necessarily the threads. Let me know if it works for you.

 

[ikeo1]

Ikeo1, it's possibly this? View attachment 7390

After reading the docs.. That's the right place to save your settings.. Otherwise, I'm still not sure what you're asking to do. It's already defaulted to last message descending. If you're talking about showing the newest thread first, that's a paid feature.

 

[Gandini]

I'm also in tech (as a designer, so barely). I've wondered what shape forums will take in the future. There's a gulf between the endless scroll of Reddit/Discord and orderly legacy forums stuffed with broken Photobucket links.

I'm seeing more Vercel/Next communities built like a progressive web app. Watchcrunch is a good example. I imagine classifieds especially would benefit from leaving the forum format and building like a SPA. Thumbnail/card nav instead of tables, seller profiles, collections/stores, favorites, etc. But that makes less sense when it's attached to a traditional forum.

Anyways, thanks for taking this on. It's a lot of work even without a designer derailing you.

 

[ikeo1]

My point is I didn't see the report or edit texts, and wouldn't know where to hover. There is very little contrast between the text color and background color. It's more of an accessibility feature. But I have middle aged eyes and don't see as well as I used to. Thanks for all your hard work.

Can you post this in site feedback please.. easier for me to work through

 

[lopez1171]

Put the page number/ selector on the top of the page. Both top and bottom

 

[lopez1171]

Could have sworn I saw this feature added and then it was gone.

 

[wtf_calguns_migration]

This is the main reason why we haven’t put it in yet. Too much categorization too early makes the listing process more difficult than it needs to be for the stage we’re at. Everything gets subdivided into longer and longer lists. For now, replicating what people are used to with the biggest improvements like region and roster with keywords should work for the 80% with minimal effort. When the listings grow this may be needed and can be implemented at any time.

The goal is more like Google search vs navigational search. It saves from the list being really long to navigate, but still benefits from good search results. Hopefully the search engine should satisfy the majority. My question would be have you tried the search function in its current form? I would suggest you try it to see if it works without all the sub categories

Most people would type in Glock 19 and check NorCal , vs search through a list of manufacturers, check counties, check striker fired, check Glock models, when there’s not a lot of listings. It gets cumbersome.

Otherwise, we do appreciate the feedback and it is all very valuable and things can and will definitely be adjusted according to usage. We listen here, and prefer to have a conversation. The main tell for me on the backend is when search engine usage goes up, then I can add the navigation links and the field to bring it back down. Both are two different engines. Navigation would hit the database. Search gets indexed incrementally.

One thing to note: I keep a list of suggestions so that anytime if people start to want a feature more. I'll implement it. When you create a post in this forum, there's an up and down vote arrow for people to vote.

1). Temp Forum Black Friday ads page and a list of confirmed stores that price match would be valuable.


2). Search issue:

You'd use sql Views rather than ad hoc queries or a forest of ephemeral user generated Procedures.
That simplifies UI changes to bubble up a users most searched whatever.
They can be Grouped, or more prevalent is to isolate and segment the common View to a cached result to a pool of users.

ie SoCal -> P365 -> under $550 search fires and they see a changed/unchanged view of the same search string.

Its like firing off the same $11 chicken fried steak lunch special order. Unique/changed orders can be addressed individually, but you'd assemble chicken fried steak en masse and tag out the ones that have diff requests. Fire out the plates, user consumes, drop/recycle.

You wouldnt normally allow pressure from every single search to be handled as unique as that would consume your resources and generate a bunch of on DB friction. Better to offload the Views and segment shots of the DB off a read only db snap for the most common search work.

 

[ikeo1]

1). Temp Forum Black Friday ads page and a list of confirmed stores that price match would be valuable.


2). Search issue:

You'd use sql Views rather than ad hoc queries or a forest of ephemeral user generated Procedures.
That simplifies UI changes to bubble up a users most searched whatever.
They can be Grouped, or more prevalent is to isolate and segment the common View to a cached result to a pool of users.

ie SoCal -> P365 -> under $550 search fires and they see a changed/unchanged view of the same search string.

Its like firing off the same $11 chicken fried steak lunch special order. Unique/changed orders can be addressed individually, but you'd assemble chicken fried steak en masse and tag out the ones that have diff requests. Fire out the plates, user consumes, drop/recycle.

You wouldnt normally allow pressure from every single search to be handled as unique as that would consume your resources and generate a bunch of on DB friction. Better to offload the Views and segment shots of the DB off a read only db snap for the most common search work.

What’s the issue you’re noticing? Search here doesn’t touch the database. We have a separate search service which is why things return real time. Everything is served from memory so results return in < 10 ms. There’s an active issue with keywords right now. If you have suggestions for ES, glad to hear them. We had to pay to upgrade to use this and also pay to use an adapter for the classifieds section. The recent saved search feature is yet another paid function. We don’t rely on free



Feel free to open a thread or BF deals in the Deals & Coupons forum

 

[wtf_calguns_migration]

What’s the issue you’re noticing? Search here doesn’t touch the database. We have a separate search service which is why things return real time. Everything is served from memory so results return in < 10 ms. There’s an active issue with keywords right now. If you have suggestions for ES, glad to hear them. We had to pay to upgrade to use this and also pay to use an adapter for the classifieds section. The recent saved search feature is yet another paid function. We don’t rely on free

View attachment 17664

Feel free to open a thread or BF deals in the Deals & Coupons forum

Ok, you're seeing things as clickops.
Regardless of platform provider, just turning on cache can help scaling problems.
If you do not know if your query scaling issues are horizontal or vertical then just enabling elasticache vs redis is a valid temporary coin flip.

What I was talking about is the Dev component:

Welcome - Amazon ElastiCache

Amazon ElastiCache is a web service that makes it easier to set up, operate, and scale a distributed cache in the cloud.

docs.aws.amazon.com

Redis Developer

Redis Developer Community. Redis Developer has 392 repositories available. Follow their code on GitHub.

github.com

This would be taking the known pressures of search and optimizing whatever your n-tier Web stack is written on.
Search offload to cache is architectural choices made based on what you're seeing.
Most people load test before committing anything to Prod so they get a read on how much or how fast the commit is worth (for now).
You have to write that for yourself, based on real data from your real deployments.

Platform provider cert material tends to teach basic clickops mitigations for horizontal OR vertical pressure.
Both and more have been usual architectural implementations since about when everyone got a smart phone and discovered talking constantly on platforms.
That means you go as far as you can with whatever you have, gathering data.
That data will infer what happens when you have to rip the visual elements of this site and stick it on an informed rewrite/replatform based on your Operational lessons learned.

Anyone that's done structural building work, commercial teardowns/builds, dealt with residential units with weather impacts, etc will get the gist of what I'm saying.
You can throw stuff up, patch as absolutely needed, roll until it needs to be torn down.
You can engineer over a lifecycle focusing specifics to improve whatever criteria is quality of life important.
Tends to not be that much in the middle.

 

[ikeo1]

Ok, you're seeing things as clickops.
Regardless of platform provider, just turning on cache can help scaling problems.
If you do not know if your query scaling issues are horizontal or vertical then just enabling elasticache vs redis is a valid temporary coin flip.

What I was talking about is the Dev component:

Welcome - Amazon ElastiCache

Amazon ElastiCache is a web service that makes it easier to set up, operate, and scale a distributed cache in the cloud.

docs.aws.amazon.com

Redis Developer

Redis Developer Community. Redis Developer has 392 repositories available. Follow their code on GitHub.

github.com

This would be taking the known pressures of search and optimizing whatever your n-tier Web stack is written on.
Search offload to cache is architectural choices made based on what you're seeing.
Most people load test before committing anything to Prod so they get a read on how much or how fast the commit is worth (for now).
You have to write that for yourself, based on real data from your real deployments.

Platform provider cert material tends to teach basic clickops mitigations for horizontal OR vertical pressure.
Both and more have been usual architectural implementations since about when everyone got a smart phone and discovered talking constantly on platforms.
That means you go as far as you can with whatever you have, gathering data.
That data will infer what happens when you have to rip the visual elements of this site and stick it on an informed rewrite/replatform based on your Operational lessons learned.

Anyone that's done structural building work, commercial teardowns/builds, dealt with residential units with weather impacts, etc will get the gist of what I'm saying.
You can throw stuff up, patch as absolutely needed, roll until it needs to be torn down.
You can engineer over a lifecycle focusing specifics to improve whatever criteria is quality of life important.
Tends to not be that much in the middle.

Switching to ES was necessary for the region/caliber/etc separation. We use a lot of custom fields which is why even if CGN came back online they couldn’t match what we do here without a lot of customization. We offload the database so it can focus on actionable tasks vs reading.

This also isn’t my first rodeo. We leverage a number of caches at different points in the architecture to minimize direct hits at several points in the system. If you read the engineering blog and migration you can see we can scale both horizontally and vertically with minimal deployments. I’ve done this for the last 20 years growing sites to millions of users and have a lot of experience with scaling. So a lot of the headaches were built in early on. We can scale pretty easily.

Are you seeing a problem or are you offering general guidance? We also have a test site but when it comes to load, there’s not much its very small compared to what I’m used to. Moderation takes the most amount of time. Handling policies and rules that are strong and enforced helps with automating tasks and help moderate without any bias. This is the hardest thing about the forum. For systems its easy, rules are programmatically enforced.

We use redis and have from the get go back in April. I put a lot of thought early on so I don’t have to rearchitect it later. I wasn’t kidding when I said this site is over engineered. The site as is can scale to 100k+ users with absolutely no changes other than vertical scaling (5 minutes here annd there) and performance will remain consistent the entire time. Everything is vertically scalable and has a caching layer in front where applicable.



Let me know if you have any questions. I am open to advice and appreciate it.

 

[MIKESTACTICALSLLC]

what is the instagram name for CAGUNS.NET? I don't want to tag or follow the wrong account