#pkpsprint — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pkpsprint, aggregated by home.social.
-
Thanks to all the attendees and our hosts for a great first day of #pkpTur2024!
Today the first four groups worked on:
📌 Typesetting / XML / HTML
📌 #OpenMonographPress
📌 GDPR compliance
📌 Open Peer Review -
Thanks to all the attendees and our hosts for a great first day of #pkpTur2024!
Today the first four groups worked on:
📌 Typesetting / XML / HTML
📌 #OpenMonographPress
📌 GDPR compliance
📌 Open Peer Review -
Thanks to all the attendees and our hosts for a great first day of #pkpTur2024!
Today the first four groups worked on:
📌 Typesetting / XML / HTML
📌 #OpenMonographPress
📌 GDPR compliance
📌 Open Peer Review -
Thanks to all the attendees and our hosts for a great first day of #pkpTur2024!
Today the first four groups worked on:
📌 Typesetting / XML / HTML
📌 #OpenMonographPress
📌 GDPR compliance
📌 Open Peer Review -
Thanks to all the attendees and our hosts for a great first day of #pkpTur2024!
Today the first four groups worked on:
📌 Typesetting / XML / HTML
📌 #OpenMonographPress
📌 GDPR compliance
📌 Open Peer Review -
The 2024 @PublicKnowledgeProject Sprint begins in the incredible Il Circolo dei lettori. Fifty representatives from around the world to begin work, complete work, and get creative on OJS, OMP, and OPS. But, just as importantly to meet and spend time together in the beauty of Turin with the amazing welcome, support, and hospitality of Elena Giglia, the Open Science Officer Università degli Studi di Torino.
#PKPSprint #PKPTur2024 #OpenInfrastructure #FOSS #ScholarlyPublishing
-
The 2024 @PublicKnowledgeProject Sprint begins in the incredible Il Circolo dei lettori. Fifty representatives from around the world to begin work, complete work, and get creative on OJS, OMP, and OPS. But, just as importantly to meet and spend time together in the beauty of Turin with the amazing welcome, support, and hospitality of Elena Giglia, the Open Science Officer Università degli Studi di Torino.
#PKPSprint #PKPTur2024 #OpenInfrastructure #FOSS #ScholarlyPublishing
-
The 2024 @PublicKnowledgeProject Sprint begins in the incredible Il Circolo dei lettori. Fifty representatives from around the world to begin work, complete work, and get creative on OJS, OMP, and OPS. But, just as importantly to meet and spend time together in the beauty of Turin with the amazing welcome, support, and hospitality of Elena Giglia, the Open Science Officer Università degli Studi di Torino.
#PKPSprint #PKPTur2024 #OpenInfrastructure #FOSS #ScholarlyPublishing
-
The 2024 @PublicKnowledgeProject Sprint begins in the incredible Il Circolo dei lettori. Fifty representatives from around the world to begin work, complete work, and get creative on OJS, OMP, and OPS. But, just as importantly to meet and spend time together in the beauty of Turin with the amazing welcome, support, and hospitality of Elena Giglia, the Open Science Officer Università degli Studi di Torino.
#PKPSprint #PKPTur2024 #OpenInfrastructure #FOSS #ScholarlyPublishing
-
The #PKPSprint in collaboration with CRAFT-OA starts today in Turin! A great opportunity for the community to contribute to advancing open-source publishing tools like #OJS, #OMP, and #OPS. #DiamondOA #OpenSource #AcademicPublishing
@PublicKnowledgeProject -
The #PKPSprint in collaboration with CRAFT-OA starts today in Turin! A great opportunity for the community to contribute to advancing open-source publishing tools like #OJS, #OMP, and #OPS. #DiamondOA #OpenSource #AcademicPublishing
@PublicKnowledgeProject -
The #PKPSprint in collaboration with CRAFT-OA starts today in Turin! A great opportunity for the community to contribute to advancing open-source publishing tools like #OJS, #OMP, and #OPS. #DiamondOA #OpenSource #AcademicPublishing
@PublicKnowledgeProject -
The #PKPSprint in collaboration with CRAFT-OA starts today in Turin! A great opportunity for the community to contribute to advancing open-source publishing tools like #OJS, #OMP, and #OPS. #DiamondOA #OpenSource #AcademicPublishing
@PublicKnowledgeProject -
Exciting news! The CRAFT-OA team is hosting a PKP Sprint on 08-09 Oct 2024 in Turin, Italy. Join the PKP community to advance open-source publishing software like OJS, OMP, and OPS. Register by 21 July 2024: https://events.gwdg.de/event/833/ #OpenAccess #PKPSprint #ScholarlyPublishing
-
Exciting news! The CRAFT-OA team is hosting a PKP Sprint on 08-09 Oct 2024 in Turin, Italy. Join the PKP community to advance open-source publishing software like OJS, OMP, and OPS. Register by 21 July 2024: https://events.gwdg.de/event/833/ #OpenAccess #PKPSprint #ScholarlyPublishing
-
Exciting news! The CRAFT-OA team is hosting a PKP Sprint on 08-09 Oct 2024 in Turin, Italy. Join the PKP community to advance open-source publishing software like OJS, OMP, and OPS. Register by 21 July 2024: https://events.gwdg.de/event/833/ #OpenAccess #PKPSprint #ScholarlyPublishing
-
Exciting news! The CRAFT-OA team is hosting a PKP Sprint on 08-09 Oct 2024 in Turin, Italy. Join the PKP community to advance open-source publishing software like OJS, OMP, and OPS. Register by 21 July 2024: https://events.gwdg.de/event/833/ #OpenAccess #PKPSprint #ScholarlyPublishing
-
really I should just make a GD blogpost about this...and I will but also I am doing laundry and am exhausted.
-
really I should just make a GD blogpost about this...and I will but also I am doing laundry and am exhausted.
-
really I should just make a GD blogpost about this...and I will but also I am doing laundry and am exhausted.
-
really I should just make a GD blogpost about this...and I will but also I am doing laundry and am exhausted.
-
really I should just make a GD blogpost about this...and I will but also I am doing laundry and am exhausted.
-
I will say, and I'm sure this will come up at #LPF24 tomorrow and Thursday:
for all we talk about "open infrastructure," many libraries are adopting tools/platforms that on the technical side are over-engineered, require substantial computing power, and often, considerable attention from people with technical expertise.
To say nothing of the fact that to load a single page, you are asking your users (who aren't using the latest MacBook Pros on 1+ gbit connections like many developers or first-world librarians, especially in the US/Canada) to load tons of webfonts and JavaScript, asking them to do all sorts of stuff in order to access an ostensibly open textbook.
The result of the first part is that our 'open' infrastructure becomes highly centralized, we surrender privacy protections that we (hopefully!!) have for things we host/manage ourselves, and we risk locking ourselves into a vendor/client relationship. Just like with Elsevier/Springer/et al. And lol, what happens in 5-6 years when you can't afford whatever they're charging? Or when the company that you pay for hosting realizes that maintaining this complicated code monster isn't worth the effort?
The result of the second part is that we make it actively harder for people who aren't at ARL Libraries, who don't have lots of resources, who have a hard time accessing sites because the only internet connection outside of campus is their phone?
Compare this to something like @PublicKnowledgeProject's Open Journal System which is a drastically simpler application based on 20+ year old technology that is rock solid.* That is easy to maintain. That is easy to understand. That is secure. Serving pages that are lightweight and easily accessible.
Not based on the popular programming language of the week. Not based on whatever the latest trend is.
Built on technology that very simply: JUST WORKS.
...and yes, we can make it have a slide carousel on the front page.
*technical: it's a (BSD/Linux/Mac/Windows)/Apache/MariaDB/PHP stack
-
I will say, and I'm sure this will come up at #LPF24 tomorrow and Thursday:
for all we talk about "open infrastructure," many libraries are adopting tools/platforms that on the technical side are over-engineered, require substantial computing power, and often, considerable attention from people with technical expertise.
To say nothing of the fact that to load a single page, you are asking your users (who aren't using the latest MacBook Pros on 1+ gbit connections like many developers or first-world librarians, especially in the US/Canada) to load tons of webfonts and JavaScript, asking them to do all sorts of stuff in order to access an ostensibly open textbook.
The result of the first part is that our 'open' infrastructure becomes highly centralized, we surrender privacy protections that we (hopefully!!) have for things we host/manage ourselves, and we risk locking ourselves into a vendor/client relationship. Just like with Elsevier/Springer/et al. And lol, what happens in 5-6 years when you can't afford whatever they're charging? Or when the company that you pay for hosting realizes that maintaining this complicated code monster isn't worth the effort?
The result of the second part is that we make it actively harder for people who aren't at ARL Libraries, who don't have lots of resources, who have a hard time accessing sites because the only internet connection outside of campus is their phone?
Compare this to something like @PublicKnowledgeProject's Open Journal System which is a drastically simpler application based on 20+ year old technology that is rock solid.* That is easy to maintain. That is easy to understand. That is secure. Serving pages that are lightweight and easily accessible.
Not based on the popular programming language of the week. Not based on whatever the latest trend is.
Built on technology that very simply: JUST WORKS.
...and yes, we can make it have a slide carousel on the front page.
*technical: it's a (BSD/Linux/Mac/Windows)/Apache/MariaDB/PHP stack
-
I will say, and I'm sure this will come up at #LPF24 tomorrow and Thursday:
for all we talk about "open infrastructure," many libraries are adopting tools/platforms that on the technical side are over-engineered, require substantial computing power, and often, considerable attention from people with technical expertise.
To say nothing of the fact that to load a single page, you are asking your users (who aren't using the latest MacBook Pros on 1+ gbit connections like many developers or first-world librarians, especially in the US/Canada) to load tons of webfonts and JavaScript, asking them to do all sorts of stuff in order to access an ostensibly open textbook.
The result of the first part is that our 'open' infrastructure becomes highly centralized, we surrender privacy protections that we (hopefully!!) have for things we host/manage ourselves, and we risk locking ourselves into a vendor/client relationship. Just like with Elsevier/Springer/et al. And lol, what happens in 5-6 years when you can't afford whatever they're charging? Or when the company that you pay for hosting realizes that maintaining this complicated code monster isn't worth the effort?
The result of the second part is that we make it actively harder for people who aren't at ARL Libraries, who don't have lots of resources, who have a hard time accessing sites because the only internet connection outside of campus is their phone?
Compare this to something like @PublicKnowledgeProject's Open Journal System which is a drastically simpler application based on 20+ year old technology that is rock solid.* That is easy to maintain. That is easy to understand. That is secure. Serving pages that are lightweight and easily accessible.
Not based on the popular programming language of the week. Not based on whatever the latest trend is.
Built on technology that very simply: JUST WORKS.
...and yes, we can make it have a slide carousel on the front page.
*technical: it's a (BSD/Linux/Mac/Windows)/Apache/MariaDB/PHP stack
-
I will say, and I'm sure this will come up at #LPF24 tomorrow and Thursday:
for all we talk about "open infrastructure," many libraries are adopting tools/platforms that on the technical side are over-engineered, require substantial computing power, and often, considerable attention from people with technical expertise.
To say nothing of the fact that to load a single page, you are asking your users (who aren't using the latest MacBook Pros on 1+ gbit connections like many developers or first-world librarians, especially in the US/Canada) to load tons of webfonts and JavaScript, asking them to do all sorts of stuff in order to access an ostensibly open textbook.
The result of the first part is that our 'open' infrastructure becomes highly centralized, we surrender privacy protections that we (hopefully!!) have for things we host/manage ourselves, and we risk locking ourselves into a vendor/client relationship. Just like with Elsevier/Springer/et al. And lol, what happens in 5-6 years when you can't afford whatever they're charging? Or when the company that you pay for hosting realizes that maintaining this complicated code monster isn't worth the effort?
The result of the second part is that we make it actively harder for people who aren't at ARL Libraries, who don't have lots of resources, who have a hard time accessing sites because the only internet connection outside of campus is their phone?
Compare this to something like @PublicKnowledgeProject's Open Journal System which is a drastically simpler application based on 20+ year old technology that is rock solid.* That is easy to maintain. That is easy to understand. That is secure. Serving pages that are lightweight and easily accessible.
Not based on the popular programming language of the week. Not based on whatever the latest trend is.
Built on technology that very simply: JUST WORKS.
...and yes, we can make it have a slide carousel on the front page.
*technical: it's a (BSD/Linux/Mac/Windows)/Apache/MariaDB/PHP stack
-
I will say, and I'm sure this will come up at #LPF24 tomorrow and Thursday:
for all we talk about "open infrastructure," many libraries are adopting tools/platforms that on the technical side are over-engineered, require substantial computing power, and often, considerable attention from people with technical expertise.
To say nothing of the fact that to load a single page, you are asking your users (who aren't using the latest MacBook Pros on 1+ gbit connections like many developers or first-world librarians, especially in the US/Canada) to load tons of webfonts and JavaScript, asking them to do all sorts of stuff in order to access an ostensibly open textbook.
The result of the first part is that our 'open' infrastructure becomes highly centralized, we surrender privacy protections that we (hopefully!!) have for things we host/manage ourselves, and we risk locking ourselves into a vendor/client relationship. Just like with Elsevier/Springer/et al. And lol, what happens in 5-6 years when you can't afford whatever they're charging? Or when the company that you pay for hosting realizes that maintaining this complicated code monster isn't worth the effort?
The result of the second part is that we make it actively harder for people who aren't at ARL Libraries, who don't have lots of resources, who have a hard time accessing sites because the only internet connection outside of campus is their phone?
Compare this to something like @PublicKnowledgeProject's Open Journal System which is a drastically simpler application based on 20+ year old technology that is rock solid.* That is easy to maintain. That is easy to understand. That is secure. Serving pages that are lightweight and easily accessible.
Not based on the popular programming language of the week. Not based on whatever the latest trend is.
Built on technology that very simply: JUST WORKS.
...and yes, we can make it have a slide carousel on the front page.
*technical: it's a (BSD/Linux/Mac/Windows)/Apache/MariaDB/PHP stack
-
also as I just noted IRL:
THANK YOU to the @PublicKnowledgeProject folks for developing platforms and software that aren't, for lack of a better and more succinct expression, a roaring tire fire.
imagine that.
-
also as I just noted IRL:
THANK YOU to the @PublicKnowledgeProject folks for developing platforms and software that aren't, for lack of a better and more succinct expression, a roaring tire fire.
imagine that.
-
also as I just noted IRL:
THANK YOU to the @PublicKnowledgeProject folks for developing platforms and software that aren't, for lack of a better and more succinct expression, a roaring tire fire.
imagine that.
-
also as I just noted IRL:
THANK YOU to the @PublicKnowledgeProject folks for developing platforms and software that aren't, for lack of a better and more succinct expression, a roaring tire fire.
imagine that.
-
also as I just noted IRL:
THANK YOU to the @PublicKnowledgeProject folks for developing platforms and software that aren't, for lack of a better and more succinct expression, a roaring tire fire.
imagine that.
-
All I'm saying is don't reinvent the wheel every other week and don't over-complicate things.
PLEASE I am begging you people.
-
All I'm saying is don't reinvent the wheel every other week and don't over-complicate things.
PLEASE I am begging you people.
-
All I'm saying is don't reinvent the wheel every other week and don't over-complicate things.
PLEASE I am begging you people.
-
All I'm saying is don't reinvent the wheel every other week and don't over-complicate things.
PLEASE I am begging you people.
-
All I'm saying is don't reinvent the wheel every other week and don't over-complicate things.
PLEASE I am begging you people.
-
Specifically thinking of systems that I have openly criticized before, including one developed/funded by a different unit at my own university which I actively disdain.*
5 MB pages for...text....because you're loading in 20 webfonts from multiple CDNs. Using 2-3 GB of RAM on a brand new VPS and a brand new install because you've got an enormous Rails application doing nothing but sitting there with no users or publications. That's not kosher. Don't abuse users like that. Especially students from disadvantaged backgrounds or people with lower-bandwidth internet connections.
see also: node apps that do the same thing.
see also: rust web assembly apps that do the same thingwhat if instead we use lightweight, easy to use, and accessible applications driven by cross-platform Apache/PHP/MariaDB/etc.??
Not shiny. Not sexy. It just works. and works well, tbqh.
*manifold. it's manifold.
-
Specifically thinking of systems that I have openly criticized before, including one developed/funded by a different unit at my own university which I actively disdain.*
5 MB pages for...text....because you're loading in 20 webfonts from multiple CDNs. Using 2-3 GB of RAM on a brand new VPS and a brand new install because you've got an enormous Rails application doing nothing but sitting there with no users or publications. That's not kosher. Don't abuse users like that. Especially students from disadvantaged backgrounds or people with lower-bandwidth internet connections.
see also: node apps that do the same thing.
see also: rust web assembly apps that do the same thingwhat if instead we use lightweight, easy to use, and accessible applications driven by cross-platform Apache/PHP/MariaDB/etc.??
Not shiny. Not sexy. It just works. and works well, tbqh.
*manifold. it's manifold.
-
Specifically thinking of systems that I have openly criticized before, including one developed/funded by a different unit at my own university which I actively disdain.*
5 MB pages for...text....because you're loading in 20 webfonts from multiple CDNs. Using 2-3 GB of RAM on a brand new VPS and a brand new install because you've got an enormous Rails application doing nothing but sitting there with no users or publications. That's not kosher. Don't abuse users like that. Especially students from disadvantaged backgrounds or people with lower-bandwidth internet connections.
see also: node apps that do the same thing.
see also: rust web assembly apps that do the same thingwhat if instead we use lightweight, easy to use, and accessible applications driven by cross-platform Apache/PHP/MariaDB/etc.??
Not shiny. Not sexy. It just works. and works well, tbqh.
*manifold. it's manifold.
-
Specifically thinking of systems that I have openly criticized before, including one developed/funded by a different unit at my own university which I actively disdain.*
5 MB pages for...text....because you're loading in 20 webfonts from multiple CDNs. Using 2-3 GB of RAM on a brand new VPS and a brand new install because you've got an enormous Rails application doing nothing but sitting there with no users or publications. That's not kosher. Don't abuse users like that. Especially students from disadvantaged backgrounds or people with lower-bandwidth internet connections.
see also: node apps that do the same thing.
see also: rust web assembly apps that do the same thingwhat if instead we use lightweight, easy to use, and accessible applications driven by cross-platform Apache/PHP/MariaDB/etc.??
Not shiny. Not sexy. It just works. and works well, tbqh.
*manifold. it's manifold.
-
Specifically thinking of systems that I have openly criticized before, including one developed/funded by a different unit at my own university which I actively disdain.*
5 MB pages for...text....because you're loading in 20 webfonts from multiple CDNs. Using 2-3 GB of RAM on a brand new VPS and a brand new install because you've got an enormous Rails application doing nothing but sitting there with no users or publications. That's not kosher. Don't abuse users like that. Especially students from disadvantaged backgrounds or people with lower-bandwidth internet connections.
see also: node apps that do the same thing.
see also: rust web assembly apps that do the same thingwhat if instead we use lightweight, easy to use, and accessible applications driven by cross-platform Apache/PHP/MariaDB/etc.??
Not shiny. Not sexy. It just works. and works well, tbqh.
*manifold. it's manifold.
-
today (now that I'm in the pre-conf after some administrative stuff): talking about @PublicKnowledgeProject's role in the #OpenPublishing #ScholComm #OpenAccess ecosystem (hint: it's really gd important) (2nd hint: and immensely better than the alternative)
-
today (now that I'm in the pre-conf after some administrative stuff): talking about @PublicKnowledgeProject's role in the #OpenPublishing #ScholComm #OpenAccess ecosystem (hint: it's really gd important) (2nd hint: and immensely better than the alternative)
-
today (now that I'm in the pre-conf after some administrative stuff): talking about @PublicKnowledgeProject's role in the #OpenPublishing #ScholComm #OpenAccess ecosystem (hint: it's really gd important) (2nd hint: and immensely better than the alternative)
-
today (now that I'm in the pre-conf after some administrative stuff): talking about @PublicKnowledgeProject's role in the #OpenPublishing #ScholComm #OpenAccess ecosystem (hint: it's really gd important) (2nd hint: and immensely better than the alternative)
-
today (now that I'm in the pre-conf after some administrative stuff): talking about @PublicKnowledgeProject's role in the #OpenPublishing #ScholComm #OpenAccess ecosystem (hint: it's really gd important) (2nd hint: and immensely better than the alternative)
-
okay so things are ✨happening ✨!!
Fun with #PHP: creating a plugin to enable better diagnostics, accessible remotely via an API to enable debugging.
Improving OJS discussions, notifications, and editorial workflow. Provide more context to editors and make it easier for non-technical editors.
Improving the experience for journals using open-review. Provide more gradients of control for how open-review works for each journal.
Porting in further language/translation and accessibility improvements, especially for plugins
Fixing/Updating Documentation: taking a more task based approach to how OJS/etc. works instead of making people read through a whole thing about the whole workflow for something.
More documentation: integrating progress from previous sprints including for newly created plugins.
(Unofficial) working on thinking about how integrating OJS into the fediverse might work (me, it's me, this is my fault)
-
okay so things are ✨happening ✨!!
Fun with #PHP: creating a plugin to enable better diagnostics, accessible remotely via an API to enable debugging.
Improving OJS discussions, notifications, and editorial workflow. Provide more context to editors and make it easier for non-technical editors.
Improving the experience for journals using open-review. Provide more gradients of control for how open-review works for each journal.
Porting in further language/translation and accessibility improvements, especially for plugins
Fixing/Updating Documentation: taking a more task based approach to how OJS/etc. works instead of making people read through a whole thing about the whole workflow for something.
More documentation: integrating progress from previous sprints including for newly created plugins.
(Unofficial) working on thinking about how integrating OJS into the fediverse might work (me, it's me, this is my fault)
-
okay so things are ✨happening ✨!!
Fun with #PHP: creating a plugin to enable better diagnostics, accessible remotely via an API to enable debugging.
Improving OJS discussions, notifications, and editorial workflow. Provide more context to editors and make it easier for non-technical editors.
Improving the experience for journals using open-review. Provide more gradients of control for how open-review works for each journal.
Porting in further language/translation and accessibility improvements, especially for plugins
Fixing/Updating Documentation: taking a more task based approach to how OJS/etc. works instead of making people read through a whole thing about the whole workflow for something.
More documentation: integrating progress from previous sprints including for newly created plugins.
(Unofficial) working on thinking about how integrating OJS into the fediverse might work (me, it's me, this is my fault)
-
okay so things are ✨happening ✨!!
Fun with #PHP: creating a plugin to enable better diagnostics, accessible remotely via an API to enable debugging.
Improving OJS discussions, notifications, and editorial workflow. Provide more context to editors and make it easier for non-technical editors.
Improving the experience for journals using open-review. Provide more gradients of control for how open-review works for each journal.
Porting in further language/translation and accessibility improvements, especially for plugins
Fixing/Updating Documentation: taking a more task based approach to how OJS/etc. works instead of making people read through a whole thing about the whole workflow for something.
More documentation: integrating progress from previous sprints including for newly created plugins.
(Unofficial) working on thinking about how integrating OJS into the fediverse might work (me, it's me, this is my fault)
-
okay so things are ✨happening ✨!!
Fun with #PHP: creating a plugin to enable better diagnostics, accessible remotely via an API to enable debugging.
Improving OJS discussions, notifications, and editorial workflow. Provide more context to editors and make it easier for non-technical editors.
Improving the experience for journals using open-review. Provide more gradients of control for how open-review works for each journal.
Porting in further language/translation and accessibility improvements, especially for plugins
Fixing/Updating Documentation: taking a more task based approach to how OJS/etc. works instead of making people read through a whole thing about the whole workflow for something.
More documentation: integrating progress from previous sprints including for newly created plugins.
(Unofficial) working on thinking about how integrating OJS into the fediverse might work (me, it's me, this is my fault)
-
that gets sent over around the fediverse which could be useful for our wordpress journals.
https://wp.anelki.net/2024/05/13/and-heres-a-regular-article/
-
that gets sent over around the fediverse which could be useful for our wordpress journals.
https://wp.anelki.net/2024/05/13/and-heres-a-regular-article/
-
that gets sent over around the fediverse which could be useful for our wordpress journals.
https://wp.anelki.net/2024/05/13/and-heres-a-regular-article/
-
that gets sent over around the fediverse which could be useful for our wordpress journals.
https://wp.anelki.net/2024/05/13/and-heres-a-regular-article/
-
Reblog via anelki
at the request of some UMN editors, I’ll be exploring ways to potentially integrate activity pub into PKP publishing projects.
what are we even doing here??
but lets see how this works, ie., wordpress creating activitypub posts. Could we use this for PKP/OJS? how would that work?
https://wp.anelki.net/2024/05/13/wordpress-as-an-activitypub-actor-could-we-use-this-for-pkp-ojs/
-
Reblog via anelki
at the request of some UMN editors, I’ll be exploring ways to potentially integrate activity pub into PKP publishing projects.
what are we even doing here??
but lets see how this works, ie., wordpress creating activitypub posts. Could we use this for PKP/OJS? how would that work?
https://wp.anelki.net/2024/05/13/wordpress-as-an-activitypub-actor-could-we-use-this-for-pkp-ojs/
-
Reblog via anelki
at the request of some UMN editors, I’ll be exploring ways to potentially integrate activity pub into PKP publishing projects.
what are we even doing here??
but lets see how this works, ie., wordpress creating activitypub posts. Could we use this for PKP/OJS? how would that work?
https://wp.anelki.net/2024/05/13/wordpress-as-an-activitypub-actor-could-we-use-this-for-pkp-ojs/
-
Reblog via anelki
at the request of some UMN editors, I’ll be exploring ways to potentially integrate activity pub into PKP publishing projects.
what are we even doing here??
but lets see how this works, ie., wordpress creating activitypub posts. Could we use this for PKP/OJS? how would that work?
https://wp.anelki.net/2024/05/13/wordpress-as-an-activitypub-actor-could-we-use-this-for-pkp-ojs/