@Moshe not really, git is just a code organization tool.
Run git fetch to get the latest commits. Then git checkout master in case you're not already on master, and then git reset --hard origin/master to update your code to the latest version.
@[email protected] yes! Kelowna is great.
Didn't they evacuate it 
@jasonwch I blame AI for exposing DNS rebinding as a problem at all.
@jasonwch is the plugin still active? ./nodebb plugins
Also links to expand must be made on a separate line
@[email protected] the fediverse is pulling a @[email protected] by playing dumb, asking basic ActivityPub questions, and watching the fireworks fly.
@[email protected] "hey bud, can I work in?"
<img class="not-responsive emoji" src="https://community.nodebb.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f606.png?v=b3bda0f1f23" title="
" />
@jasonwch try latest develop branch if you don't want to wait for 4.15
@Moshe most likely you'll want to run ./nodebb build again, and watch the console output for errors.
@Moshe send over the full stack trace.
Edit: And not seeing any issue on both sites I run. Make sure you have fully updated NodeBB and rebuilt assets.
@jasonwch latest NodeBB should have this patched already, thanks.
@jasonwch no, I javent looked into the issue yet š«¤
> julian said:
>
> the Activity Intents behaviour is meant to be active even if federation is disabled.
Actually, you're right, it's not meant to work without federation
@jasonwch the Activity Intents behaviour is meant to be active even if federation is disabled.
I'll fix up the behaviour so it is consistent even if federation is disabled.
@Moshe no that's not what I mean.
If the plugin cached private, sensitive data, that is an information disclosure vulnerability.
The plugin acting as a guest and not a logged in user is a feature, not a bug.
@baris I think that's best case.
Link preview accesses as guest and caches it so we wouldn't want to leak any info out accidentally.
The technical specifics behind how forum federation works, and how it is accessible in other sites shouldn't be top of mind (or thought about at all) for anybody except those who are maintaining it.
For everybody else, it should just work.
@[email protected] said in Against fragmentation: unifying dev discussions with forum federation:
> Can you explain the user workflow here in more detail? What the user does, what the software involved does in response, and what data is moved across AP and how when it does.
I don't have one yet, but I'm planning out an FEP for this once I have some implementors interested.
The UI would be a dedicated cross posting action. How that ends up looking is up to the implementation.
Mentioning a group actor doesn't work reliably because someone could mention the group actor in passing, and not mean to have the entire conversation imported.
@[email protected], with regard to your idea about pulling in topics by mentioning the group actor... I don't think it need be as complicated as that.
A simpler UX flow would be for a user to "cross-post" a topic to a local category. In fact NodeBB already allows for this, I regularly move microblog content into local categories for discussion purposes.
Now, granted, it's "moving" a topic, which isn't quite cross posting, but I'm hoping to distil the idea down to some actionable UX and activities so it can be done in a common manner across different implementations.
@[email protected] it should work, try mentioning the ActivityPub or testing ground category. Fingers crossed.
