Skip to content
View in the app

A better way to browse. Learn more.

LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Charlie686

Members
  • Joined

  1.    JeffreyK23 reacted to a file: 686 Callouts
  2.    Charlie686 reacted to a comment on a file: GrammarPolice
  3.    Jed Cooper reacted to a file: 686 Callouts
  4.    YobB1n reacted to a review on a file: Yobbin Callouts
  5. catblanita started following Charlie686
  6.    Skydrohz reacted to a file: 686 Callouts
  7.    Mo3zPain reacted to a file: 686 Callouts
  8.    MountainTime307 reacted to a file: 686 Callouts
  9.    Michael21107 reacted to a post in a topic: Suggestion - 'Exclude AI Files' Toggle
  10.    Cyan reacted to a post in a topic: Suggestion - 'Exclude AI Files' Toggle
  11. Thanks as always, glad to hear it is on the roadmap. Have a nice bank holiday weekend 🙂
  12. Morning all, Wanted to share some feedback re filtering on Scripts & Plugins. I love the addition of the 'Made with AI' tag, but it doesn't work effectively for me because: It takes 5 clicks to exclude the tag. The tag needs to be reapplied on each page visit (at least in my experience - please correct me if I am wrong) For something that is becoming a common tag, this creates a fair amount of friction/difficulty for what feels like a popular user action. There's also a UX/usability perspective as well - when one or two files have this tag, it is much easier for these to stand out. With nearly half the page having this tag, it becomes harder to visually filter them out when browsing (and therefore increasing reliance on filtering tools instead...) Taking LSPDFR Plugins / Callouts for example. That filter is easier to use, persistent-ish (in the sense it updates the URL) and makes sense because it is something that users would often want to separate. That sort of sets the scene for why I am making this suggestion. Frequently used filters can work better when accessible and persistent, which is why I would like to see an accessible toggle for the 'Made with AI' tag. I'm not trying to penalise AI files with this suggestion, but I think filters that are often used should be prioritised for visibility. If you go into the effort of maintaining an AI classification system, you get more out of it by allowing users to take advantage of it in an easier way. Thanks for considering this suggestion, Charlie
  13. LAPDFR GET started following Charlie686
  14. Spanglishking started following Charlie686
  15.    Charlie686 reacted to a review on a file: 686 Callouts
  16.    Charlie686 reacted to a comment on a file: 686 Flock Safety Pack
  17.    Charlie686 reacted to a file: 686 Flock Safety Pack
  18. Oh look - this does look nice! 😇 There is a small error in your XML that I did notice, so I have attached the file for you here. I'm not sure if this would cause a crash but I believe some of the customisation options could be ignored. Thanks for the upload! FlockSafetyAlert.xml
  19.    Charlie686 reacted to a comment on a file: 686 Callouts
  20.    Charlie686 reacted to a post in a topic: Marking AI Content on Your Files
  21. Thanks all - this feels like a genuinely positive first step for transparency & inaccurate descriptions. I think it's also worth acknowledging the wider impact, with low-effort uploads affecting developers who invest significant time into creating, testing & maintaining projects - so it's not just a user filtering issue, but a fairness and visibility one too. Thanks for this update, I will be looking out for this disclaimer soon 👀
  22.    Charlie686 reacted to a comment on a file: 686 Callouts
  23.    Charlie686 reacted to a comment on a file: 686 Callouts
  24. Please feel free to join my Discord Server (via profile or file page) and reach out to me via a ticket to receive a free copy of Early Access as a thank you! 💌
  25.    Charlie686 reacted to a comment on a file: 686 Callouts
  26.    Charlie686 reacted to a comment on a file: 686 Callouts
  27. Hey James, I'm assuming you mean the grey line of sight-styled area? That's not a blip but a native (though attached to a blip): SET_BLIP_SHOW_CONE Thanks Lenny 🙂
  28. When a file is presented as entirely AI-generated (thumbnail...description...) it sets certain expectations. Scripts & plugins developed solely with AI often do not work, cause crashes, and displace genuine files. Given the AI thumbnail and AI description - why should anyone assume the script is any different? 🙂 You don't give them a reason to, and I would encourage you to show off the mod with the uniqueness it deserves.
  29. Charlie686 started following Camb
  30. Camb started following Charlie686
  31. dillon1992 started following Charlie686
  32. Charlie686 started following unitedOrange66
  33. Thanks Cyan - that looks great along with the light/dark mode switch. Sounds like I will just need to do a description update. 😃
  34. Hi Cyan, Thanks for implementing those fixes & enjoying the Christmas theme. I've now been able to access editing my callout page, and noticed a few things: Stop The Ped acts as if it is hyperlinked (does nothing when you click it)...but I certainly did not hyperlink it and do not intend to! The editor does not match up with what is displayed. Perhaps the latter is just something that can't get fixed, but thought I would raise it anyway as I assume it'd affect all other previously uploaded files. Many thanks, Charlie
  35. You're welcome, Cyan. Just on VirusTotal, I agree it doesn't serve a hugely positive purpose - no file uploaded to LCPDFR.com has a virus as your team checks scripts & plugins, so what point is there in showing a flag from VirusTotal? It is like admitting some files have a virus! If it is kept though, the first thing anyone thinks when they see a flagged file is "Why?!" so yes, the balance is a bit off currently. Best wishes with future development. This upgrade has gone down well.^^
  36. Good work on the website improvement, it is great to see new improvements for LCPDFR.com being driven forward. I will certainly hold you to it in regard to those API improvements! :) My current observations that I hope will be helpful to you: Unable to use the login modal (which can be worked around via lcpdfr.com/login/) Unable to edit my uploaded file. "This content can no longer be edited. It may have been moved or deleted, or too much time may have passed since it was posted for it to be edited." My public file has the option to 'show file to the public' rather than an option to hide it. Choosing the burger menu on a file comment > Feature displays two pop-ups when opening. You are no longer able to view the VirusTotal results, other than the Clean/Flagged icon. Being able to view a flagged result is important context if this was an intended change. The Albums tab on my profile is empty, when for others it is hidden (have I done something here?) The Creator Dashboard/Centre is no longer accessible. Profile > Manage File Update Notifications does not work. I am not sure if this is a new feature compared to following a file. Viewing File Stats occasionally results in a Bad Gateway error, and any attempt to change the date range causes the stats page to disappear. Once again, this version marks a huge improvement. Time well spent and I look forward to using the new customisation options available for files.
  37. Glad to see 686 Callouts inspiring other developers in the community & having a positive impact!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.