Pinned Tweet
If you need help! Don’t hesitate to reach out! [email protected]
Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities. PHP is widely used for web applications. These vulnerabilities often provide a direct path to the server's file system or database. If an immediate update is not feasible, it is recommend that organizations take the system offline until it can be fully mitigated. NSA will follow up shortly with more specific guidance.
20
Separate the coverage gate from the coverage upload.
Fail CI if coverage drops below your threshold. If the reporting service is down, flag the missing report without making a passing build look broken.
4
Make destructive actions specific.
“Delete project” is clearer than “Continue,” especially when the next click can’t be undone.
6
If two people edit the same record, don't silently overwrite one person's work.
Show what changed and give them a way to resolve the conflict.
16
When a scheduled job misses its run, decide whether it should catch up or wait for the next slot.
Make that behavior explicit before a restart turns into a backlog.
11
During a rolling deployment, old and new app versions may run together.
Plan database changes so both can work until the rollout finishes.
8
ALLSAGETECH retweeted
Image inscriptions being traded for Runes and LTC-20 coming soon! #LTC
Use a stable sort order when paginating results.
If several records share the same timestamp, add a unique tie-breaker so they don’t jump between pages.
10
Let people paste into password fields.
Blocking paste makes password managers harder to use and adds friction for people trying to sign in securely.
8
Test names with accents, apostrophes, and non-Latin characters.
A person’s name should survive signup, search, and export unchanged.
13
Give automated retries a limit and a delay.
If a service is struggling, thousands of immediate retries can make recovery harder. Decide when to stop and alert someone.
16
Show file size limits and accepted formats before someone uploads.
Finding out after a five-minute wait is a frustrating way to learn the requirements.
6
Give temporary access an expiration date.
A contractor finishing a project should trigger a review of shared folders, admin roles, and service accounts.
8
Anyone building tools to compare results across #Litecoin node implementations?
What differences would you want flagged automatically?
1
43
ALLSAGETECH retweeted
We seek individuals interested in joining LiteDrive.io who value fair launches. #litecoin
Show the time zone beside appointment times.
A confirmation that says only “9:00” leaves the reader to supply a detail that can change the whole plan.
13
Check your app at 200% zoom.
Text, buttons, and error messages should still fit without covering the task someone is trying to finish.
6
Keep useful old links working during a redesign.
If a page moves, send visitors to its new address instead of making them start from the homepage.
13
ALLSAGETECH retweeted
Going 💪 #litecoin
explorer.litedrive.io
Give long-running jobs a way to cancel.
Tell the user what has already finished and what will stop, so cancelling doesn’t leave them guessing.
8
ALLSAGETECH retweeted
LiteDrive Core is running its initial 100,000-transaction trial; you can review it here. #litecoin
explorer.litedrive.io/




