degmods/degmods.com
6
1
Fork 0
Code Issues 24 Pull Requests Actions Packages Projects 3 Releases Wiki Activity

Published an edit for a mod post may be seen as a new published post #119

New Issue
Closed
opened 2024-11-08 10:59:58 +00:00 by freakoverse · 2 comments
freakoverse commented 2024-11-08 10:59:58 +00:00
Owner
Copy Link

I may have noticed that when publishing an edit, it might have been seen as a new published event / potentially seeing that on other clients as a new post?

I may have noticed that when publishing an edit, it might have been seen as a new published event / potentially seeing that on other clients as a new post?
freakoverse added the
Priority
Medium
 label 2024-11-08 10:59:58 +00:00
enes commented 2024-11-14 13:01:48 +00:00
Collaborator
Copy Link

After yesterday's discussion I believe this differs from client to client and how they're handling the editing and feed. We can keep it open until it's 100% confirmed that it's not something on our end.

After yesterday's discussion I believe this differs from client to client and how they're handling the editing and feed. We can keep it open until it's 100% confirmed that it's not something on our end.
freakoverse added this to the Extra Features project 2024-11-17 11:23:02 +00:00
freakoverse modified the project from Extra Features to Issues 2024-11-17 11:35:30 +00:00
freakoverse commented 2024-11-17 12:11:27 +00:00
Author
Owner
Copy Link

So this is considered fixed, considering we've followed the documentation of the kind/nip standard on how to go about it, but apparently, depending on the client, it will still show this issue there.

So this is considered fixed, considering we've followed the documentation of the kind/nip standard on how to go about it, but apparently, depending on the client, it will still show this issue there.
freakoverse added the
Kind/Bug
 label 2024-11-17 15:58:01 +00:00
freakoverse moved this to Done in Issues on 2025-01-15 12:35:49 +00:00
freakoverse moved this to Done in Issues on 2025-01-15 16:41:42 +00:00
enes moved this to Done in Issues on 2025-01-15 18:12:52 +00:00
enes moved this to Done in Issues on 2025-01-15 18:33:38 +00:00
enes moved this to Done in Issues on 2025-01-15 19:23:34 +00:00
freakoverse moved this to Done in Issues on 2025-01-27 11:54:34 +00:00
freakoverse moved this to Done in Issues on 2025-01-28 01:09:46 +00:00
freakoverse moved this to Done in Issues on 2025-01-28 01:12:01 +00:00
freakoverse moved this to Done in Issues on 2025-01-30 17:30:51 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Kind/Bug
Priority
Medium
Milestone
No items
No Milestone
Projects
Clear projects
No project Issues
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: degmods/degmods.com#119
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?