#fediversedevs — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fediversedevs, aggregated by home.social.
-
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/homethe #mlem app for lemmy has added support natively for Fediverse Events 👀
-
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/homethe #mlem app for lemmy has added support natively for Fediverse Events 👀
-
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/homethe #mlem app for lemmy has added support natively for Fediverse Events 👀
-
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/homethe #mlem app for lemmy has added support natively for Fediverse Events 👀
-
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/homethe #mlem app for lemmy has added support natively for Fediverse Events 👀
-
React-like syntax with WebComponents.
After spending some time with Lit, I really appreciated its lightweight footprint but wasn't a fan of the class-based components. While Vue offers a great approach, I still prefer the intuitive nature of React's syntax for debugging and deterministic rendering. This led me to a challenge: could I build a UI framework using WebComponents that completely eliminates the need for transpilation?
I have written a breakdown of the concept, the architecture, and where I want to take it. I highly invite you to take a look, check out the code, and explore the live demo.
* How it works: https://positive-intentions.com/docs/projects/dim/dim-jsx-webcomponents
* Checkout the code: https://github.com/positive-intentions/dim
* Storybook demo: https://dim.positive-intentions.comPlease note, while the project is open-source, this is a personal exploration rather than an attempt to launch "yet another framework." It is not production-ready and is built for my own upcoming project migrations, but I am sharing it in hopes that the methodology is educational or interesting to the community.
I would love to hear your thoughts on this approach. Feel free to reach out if you have any questions or want to discuss the implementation details.
#WebDev #WebDevelopment #Frontend #FrontendDev #JavaScript #JS #TypeScript #TS #HTML #HTML5 #CSS #SoftwareEngineering #SoftwareEngineer #Coding #Programming #WebDesign #OpenSourceProject #IndieDev #SideProject #Tech #Technology #DevCommunity #Fediverse #FediverseDevs #WebStandards #CustomElements #ShadowDOM #VanillaJS #NoTranspiler #NoBuild #BuildStep #EsModules #ComponentDriven #UIUX #DesignSystems #TechExperiment #LearningInPublic #Developer #ComputerScience #OSS #Github #React #WebComponents #Lit #Vue #ReactJS #JSX #Storybook #TechArticle #TechBlog #TechWriting #WebDevArticles
-
React-like syntax with WebComponents.
After spending some time with Lit, I really appreciated its lightweight footprint but wasn't a fan of the class-based components. While Vue offers a great approach, I still prefer the intuitive nature of React's syntax for debugging and deterministic rendering. This led me to a challenge: could I build a UI framework using WebComponents that completely eliminates the need for transpilation?
I have written a breakdown of the concept, the architecture, and where I want to take it. I highly invite you to take a look, check out the code, and explore the live demo.
* How it works: https://positive-intentions.com/docs/projects/dim/dim-jsx-webcomponents
* Checkout the code: https://github.com/positive-intentions/dim
* Storybook demo: https://dim.positive-intentions.comPlease note, while the project is open-source, this is a personal exploration rather than an attempt to launch "yet another framework." It is not production-ready and is built for my own upcoming project migrations, but I am sharing it in hopes that the methodology is educational or interesting to the community.
I would love to hear your thoughts on this approach. Feel free to reach out if you have any questions or want to discuss the implementation details.
#WebDev #WebDevelopment #Frontend #FrontendDev #JavaScript #JS #TypeScript #TS #HTML #HTML5 #CSS #SoftwareEngineering #SoftwareEngineer #Coding #Programming #WebDesign #OpenSourceProject #IndieDev #SideProject #Tech #Technology #DevCommunity #Fediverse #FediverseDevs #WebStandards #CustomElements #ShadowDOM #VanillaJS #NoTranspiler #NoBuild #BuildStep #EsModules #ComponentDriven #UIUX #DesignSystems #TechExperiment #LearningInPublic #Developer #ComputerScience #OSS #Github #React #WebComponents #Lit #Vue #ReactJS #JSX #Storybook #TechArticle #TechBlog #TechWriting #WebDevArticles
-
React-like syntax with WebComponents.
After spending some time with Lit, I really appreciated its lightweight footprint but wasn't a fan of the class-based components. While Vue offers a great approach, I still prefer the intuitive nature of React's syntax for debugging and deterministic rendering. This led me to a challenge: could I build a UI framework using WebComponents that completely eliminates the need for transpilation?
I have written a breakdown of the concept, the architecture, and where I want to take it. I highly invite you to take a look, check out the code, and explore the live demo.
* How it works: https://positive-intentions.com/docs/projects/dim/dim-jsx-webcomponents
* Checkout the code: https://github.com/positive-intentions/dim
* Storybook demo: https://dim.positive-intentions.comPlease note, while the project is open-source, this is a personal exploration rather than an attempt to launch "yet another framework." It is not production-ready and is built for my own upcoming project migrations, but I am sharing it in hopes that the methodology is educational or interesting to the community.
I would love to hear your thoughts on this approach. Feel free to reach out if you have any questions or want to discuss the implementation details.
#WebDev #WebDevelopment #Frontend #FrontendDev #JavaScript #JS #TypeScript #TS #HTML #HTML5 #CSS #SoftwareEngineering #SoftwareEngineer #Coding #Programming #WebDesign #OpenSourceProject #IndieDev #SideProject #Tech #Technology #DevCommunity #Fediverse #FediverseDevs #WebStandards #CustomElements #ShadowDOM #VanillaJS #NoTranspiler #NoBuild #BuildStep #EsModules #ComponentDriven #UIUX #DesignSystems #TechExperiment #LearningInPublic #Developer #ComputerScience #OSS #Github #React #WebComponents #Lit #Vue #ReactJS #JSX #Storybook #TechArticle #TechBlog #TechWriting #WebDevArticles
-
React-like syntax with WebComponents.
After spending some time with Lit, I really appreciated its lightweight footprint but wasn't a fan of the class-based components. While Vue offers a great approach, I still prefer the intuitive nature of React's syntax for debugging and deterministic rendering. This led me to a challenge: could I build a UI framework using WebComponents that completely eliminates the need for transpilation?
I have written a breakdown of the concept, the architecture, and where I want to take it. I highly invite you to take a look, check out the code, and explore the live demo.
* How it works: https://positive-intentions.com/docs/projects/dim/dim-jsx-webcomponents
* Checkout the code: https://github.com/positive-intentions/dim
* Storybook demo: https://dim.positive-intentions.comPlease note, while the project is open-source, this is a personal exploration rather than an attempt to launch "yet another framework." It is not production-ready and is built for my own upcoming project migrations, but I am sharing it in hopes that the methodology is educational or interesting to the community.
I would love to hear your thoughts on this approach. Feel free to reach out if you have any questions or want to discuss the implementation details.
#WebDev #WebDevelopment #Frontend #FrontendDev #JavaScript #JS #TypeScript #TS #HTML #HTML5 #CSS #SoftwareEngineering #SoftwareEngineer #Coding #Programming #WebDesign #OpenSourceProject #IndieDev #SideProject #Tech #Technology #DevCommunity #Fediverse #FediverseDevs #WebStandards #CustomElements #ShadowDOM #VanillaJS #NoTranspiler #NoBuild #BuildStep #EsModules #ComponentDriven #UIUX #DesignSystems #TechExperiment #LearningInPublic #Developer #ComputerScience #OSS #Github #React #WebComponents #Lit #Vue #ReactJS #JSX #Storybook #TechArticle #TechBlog #TechWriting #WebDevArticles
-
React-like syntax with WebComponents.
After spending some time with Lit, I really appreciated its lightweight footprint but wasn't a fan of the class-based components. While Vue offers a great approach, I still prefer the intuitive nature of React's syntax for debugging and deterministic rendering. This led me to a challenge: could I build a UI framework using WebComponents that completely eliminates the need for transpilation?
I have written a breakdown of the concept, the architecture, and where I want to take it. I highly invite you to take a look, check out the code, and explore the live demo.
* How it works: https://positive-intentions.com/docs/projects/dim/dim-jsx-webcomponents
* Checkout the code: https://github.com/positive-intentions/dim
* Storybook demo: https://dim.positive-intentions.comPlease note, while the project is open-source, this is a personal exploration rather than an attempt to launch "yet another framework." It is not production-ready and is built for my own upcoming project migrations, but I am sharing it in hopes that the methodology is educational or interesting to the community.
I would love to hear your thoughts on this approach. Feel free to reach out if you have any questions or want to discuss the implementation details.
#WebDev #WebDevelopment #Frontend #FrontendDev #JavaScript #JS #TypeScript #TS #HTML #HTML5 #CSS #SoftwareEngineering #SoftwareEngineer #Coding #Programming #WebDesign #OpenSourceProject #IndieDev #SideProject #Tech #Technology #DevCommunity #Fediverse #FediverseDevs #WebStandards #CustomElements #ShadowDOM #VanillaJS #NoTranspiler #NoBuild #BuildStep #EsModules #ComponentDriven #UIUX #DesignSystems #TechExperiment #LearningInPublic #Developer #ComputerScience #OSS #Github #React #WebComponents #Lit #Vue #ReactJS #JSX #Storybook #TechArticle #TechBlog #TechWriting #WebDevArticles
-
The Fediverse is so cool because of the diversity of the different software. In the last weeks, I did build a (completely?) new one. The Menuverse consists of two software: 1) create daily changing dishes like in a canteen, and 2) can aggregate different of this actors in a marketplace. The working title for this is Menuverse.
Every canteen is Fediverse actor and not only can these marketplaces subscribe to this, but also other softwares like Mastodon, Misskey and so on.
I created a demo setup with live data from different university canteens here:
https://mahlzeitheute.de/ This is the marketplace software)
(The data and frontend is currently only in German).
You can also visit or follow the nearest canteen to me here: @fl-ca1.You can find the full software here: https://codeberg.org/54GradSoftware/menuverse
But please note that this still quite experimental and I would not advise running in production (unsupervised).I would love to get (technical) feedback, and I'm looking for real canteens who would like to test the software.
More information in the next posts (this is a thread). [1/4]
-
The Fediverse is so cool because of the diversity of the different software. In the last weeks, I did build a (completely?) new one. The Menuverse consists of two software: 1) create daily changing dishes like in a canteen, and 2) can aggregate different of this actors in a marketplace. The working title for this is Menuverse.
Every canteen is Fediverse actor and not only can these marketplaces subscribe to this, but also other softwares like Mastodon, Misskey and so on.
I created a demo setup with live data from different university canteens here:
https://mahlzeitheute.de/ This is the marketplace software)
(The data and frontend is currently only in German).
You can also visit or follow the nearest canteen to me here: @fl-ca1.You can find the full software here: https://codeberg.org/54GradSoftware/menuverse
But please note that this still quite experimental and I would not advise running in production (unsupervised).I would love to get (technical) feedback, and I'm looking for real canteens who would like to test the software.
More information in the next posts (this is a thread). [1/4]
-
The Fediverse is so cool because of the diversity of the different software. In the last weeks, I did build a (completely?) new one. The Menuverse consists of two software: 1) create daily changing dishes like in a canteen, and 2) can aggregate different of this actors in a marketplace. The working title for this is Menuverse.
Every canteen is Fediverse actor and not only can these marketplaces subscribe to this, but also other softwares like Mastodon, Misskey and so on.
I created a demo setup with live data from different university canteens here:
https://mahlzeitheute.de/ This is the marketplace software)
(The data and frontend is currently only in German).
You can also visit or follow the nearest canteen to me here: @fl-ca1.You can find the full software here: https://codeberg.org/54GradSoftware/menuverse
But please note that this still quite experimental and I would not advise running in production (unsupervised).I would love to get (technical) feedback, and I'm looking for real canteens who would like to test the software.
More information in the next posts (this is a thread). [1/4]
-
The Fediverse is so cool because of the diversity of the different software. In the last weeks, I did build a (completely?) new one. The Menuverse consists of two software: 1) create daily changing dishes like in a canteen, and 2) can aggregate different of this actors in a marketplace. The working title for this is Menuverse.
Every canteen is Fediverse actor and not only can these marketplaces subscribe to this, but also other softwares like Mastodon, Misskey and so on.
I created a demo setup with live data from different university canteens here:
https://mahlzeitheute.de/ This is the marketplace software)
(The data and frontend is currently only in German).
You can also visit or follow the nearest canteen to me here: @fl-ca1.You can find the full software here: https://codeberg.org/54GradSoftware/menuverse
But please note that this still quite experimental and I would not advise running in production (unsupervised).I would love to get (technical) feedback, and I'm looking for real canteens who would like to test the software.
More information in the next posts (this is a thread). [1/4]
-
The Fediverse is so cool because of the diversity of the different software. In the last weeks, I did build a (completely?) new one. The Menuverse consists of two software: 1) create daily changing dishes like in a canteen, and 2) can aggregate different of this actors in a marketplace. The working title for this is Menuverse.
Every canteen is Fediverse actor and not only can these marketplaces subscribe to this, but also other softwares like Mastodon, Misskey and so on.
I created a demo setup with live data from different university canteens here:
https://mahlzeitheute.de/ This is the marketplace software)
(The data and frontend is currently only in German).
You can also visit or follow the nearest canteen to me here: @fl-ca1.You can find the full software here: https://codeberg.org/54GradSoftware/menuverse
But please note that this still quite experimental and I would not advise running in production (unsupervised).I would love to get (technical) feedback, and I'm looking for real canteens who would like to test the software.
More information in the next posts (this is a thread). [1/4]
-
Introducing the MAN Protocol ($MAN): An uncheatable, perfectly equal economic network for humanity. 🌍
I have spent years designing an open-source economic experiment built to permanently address the global wealth gap and hyperinflation. Today, the core architecture is officially live.
🔗 Read the complete blueprint: https://github.com/El-Eye-Jah-7/man-protocol
Feel free to challenge any thoughts on this and I'll be happy to resolve your doubts.
Join in and let's get started.
(1/4) #OpenSource #Crypto #Web3 #UBI #MANProtocol #FediverseDevs
-
Introducing the MAN Protocol ($MAN): An uncheatable, perfectly equal economic network for humanity. 🌍
I have spent years designing an open-source economic experiment built to permanently address the global wealth gap and hyperinflation. Today, the core architecture is officially live.
🔗 Read the complete blueprint: https://github.com/El-Eye-Jah-7/man-protocol
Feel free to challenge any thoughts on this and I'll be happy to resolve your doubts.
Join in and let's get started.
(1/4) #OpenSource #Crypto #Web3 #UBI #MANProtocol #FediverseDevs
-
Introducing the MAN Protocol ($MAN): An uncheatable, perfectly equal economic network for humanity. 🌍
I have spent years designing an open-source economic experiment built to permanently address the global wealth gap and hyperinflation. Today, the core architecture is officially live.
🔗 Read the complete blueprint: https://github.com/El-Eye-Jah-7/man-protocol
Feel free to challenge any thoughts on this and I'll be happy to resolve your doubts.
Join in and let's get started.
(1/4) #OpenSource #Crypto #Web3 #UBI #MANProtocol #FediverseDevs
-
Introducing the MAN Protocol ($MAN): An uncheatable, perfectly equal economic network for humanity. 🌍
I have spent years designing an open-source economic experiment built to permanently address the global wealth gap and hyperinflation. Today, the core architecture is officially live.
🔗 Read the complete blueprint: https://github.com/El-Eye-Jah-7/man-protocol
Feel free to challenge any thoughts on this and I'll be happy to resolve your doubts.
Join in and let's get started.
(1/4) #OpenSource #Crypto #Web3 #UBI #MANProtocol #FediverseDevs
-
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/home -
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/home -
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/home -
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/home -
... and if you're a Fediverse app developer (or just want to look at the source code):
Source: https://sc07.dev/sc07/canvas
Developer Docs: https://sc07.dev/fediverse.events/fediverse.events-api/-/wikis/home -
Day 5 design-tips wrap-up.
We ship dual-surface SaaS dashboards — dark for sessions, light for reads, design tokens for both. Five-year-old apps with magic-number CSS are why this matters.
Portfolio: risesitelab.com/#portfolio
GrowthSite Lab.
-
Dark mode looks cool. Light mode reads. In premium SaaS you ship both.
Default by context — not trend. Session-heavy apps default dark. Read-heavy default light. Respect prefers-color-scheme on first visit. Persist the user's choice forever after they toggle.
WCAG 4.5:1 on body text — both palettes — is non-negotiable. Design tokens, never magic numbers; light + dark are two themes of the same color tree.
GrowthSite Lab.
-
Dark mode looks cool. Light mode reads. In premium SaaS you ship both.
Default by context — not trend. Session-heavy apps default dark. Read-heavy default light. Respect prefers-color-scheme on first visit. Persist the user's choice forever after they toggle.
WCAG 4.5:1 on body text — both palettes — is non-negotiable. Design tokens, never magic numbers; light + dark are two themes of the same color tree.
GrowthSite Lab.
-
Dark mode looks cool. Light mode reads. In premium SaaS you ship both.
Default by context — not trend. Session-heavy apps default dark. Read-heavy default light. Respect prefers-color-scheme on first visit. Persist the user's choice forever after they toggle.
WCAG 4.5:1 on body text — both palettes — is non-negotiable. Design tokens, never magic numbers; light + dark are two themes of the same color tree.
GrowthSite Lab.
-
Dark mode looks cool. Light mode reads. In premium SaaS you ship both.
Default by context — not trend. Session-heavy apps default dark. Read-heavy default light. Respect prefers-color-scheme on first visit. Persist the user's choice forever after they toggle.
WCAG 4.5:1 on body text — both palettes — is non-negotiable. Design tokens, never magic numbers; light + dark are two themes of the same color tree.
GrowthSite Lab.
-
Premium tech brands rarely use more than two typefaces. Clean contrast wins trust.
Five pairs we ship in 2026: Satoshi + Inter (clean modern SaaS) · Neue Haas Grotesk + Space Grotesk (Swiss editorial) · Cormorant + Inter (luxury aesthetic) · Obviously + General Sans (confident startup) · Tiempos + Söhne (editorial premium).
Cap the weight ladder at three (200/400/700). Mid-weights read muddy at small sizes.
GrowthSite Lab.
-
Premium tech brands rarely use more than two typefaces. Clean contrast wins trust.
Five pairs we ship in 2026: Satoshi + Inter (clean modern SaaS) · Neue Haas Grotesk + Space Grotesk (Swiss editorial) · Cormorant + Inter (luxury aesthetic) · Obviously + General Sans (confident startup) · Tiempos + Söhne (editorial premium).
Cap the weight ladder at three (200/400/700). Mid-weights read muddy at small sizes.
GrowthSite Lab.
-
Micro-interactions aren't decoration — they're feedback. Tiny animations answering: 'Was my click registered?', 'Is my work safe?', 'Where am I going?'.
Premium product feel comes from how the surface responds, not how it looks at rest. 120ms hover, 200ms transition, zero layout shift, skeleton over spinner, reduced-motion honored.
GrowthSite Lab.
-
A medspa redesign concept built around a single editorial cover plate that replaces the need for prospect-specific photography.
Same client photos, different positioning: cream/champagne/ink palette, Cormorant Garamond serif display, 5-section narrative arc — Hero, Trust, Services, Before-After, CTA. Vite + React 18 + Tailwind v4 + Framer Motion 11. 97 KB gzip total bundle, 1.4s mobile load.
Built by GrowthSite Lab.
#WebDev #ReactJS #TailwindCSS #FramerMotion #FediverseDevs #UIUX
-
Micro-interactions aren't decoration — they're feedback. Tiny animations answering: 'Was my click registered?', 'Is my work safe?', 'Where am I going?'.
Premium product feel comes from how the surface responds, not how it looks at rest. 120ms hover, 200ms transition, zero layout shift, skeleton over spinner, reduced-motion honored.
GrowthSite Lab.
-
A hero section is a 5-second contract.
Headline answers 'what do I get'. Subhead answers 'why now'. One CTA — never two. One trust signal above the fold. Numbers beat adjectives.
Found this rule by auditing 50+ funded SaaS landings. The median sits between 50-70 on mobile Lighthouse — and the hero is where the bleeding starts.
GrowthSite Lab.
-
A SaaS landing built around the Command Palette as a conversion surface — not decoration.
CMDK wired to live state, streaming AI responses, R3F dashboard backdrop running off the main thread. Lighthouse 96 mobile · LCP 1.6s · CLS 0.03.
Stack: Next.js 15 App Router · Tailwind v4 @Theme · Framer Motion 12 · Vercel AI SDK. Performance budget enforced in CI. Built by GrowthSite Lab.
-
A hero section is a 5-second contract.
Headline answers 'what do I get'. Subhead answers 'why now'. One CTA — never two. One trust signal above the fold. Numbers beat adjectives.
Found this rule by auditing 50+ funded SaaS landings. The median sits between 50-70 on mobile Lighthouse — and the hero is where the bleeding starts.
GrowthSite Lab.
-
Five thousand nodes, 60fps, one Three.js scene.
A knowledge graph 3D visualization built on React Three Fiber + d3-force-3d + Vite. Instanced sphere geometry for nodes, batched line geometry for edges, auto-frame camera on first paint. Vertex colors disabled on the material — that's the landmine that costs a weekend if you miss it.
Built by GrowthSite Lab.
-
A tattoo studio website should respect the work, not compete with it.
Six services, a 6-image masonry gallery, WhatsApp-first booking, and a Trust Bar with the actual 271 reviews and 15K community. Italian + English copy, dark/gold palette, LCP under 2.5s on mobile.
Built by GrowthSite Lab.
#WebDev #TattooIndustry #PerformanceBudget #FediverseDevs #ItalianBusiness
-
Let’s say you have an HTTP server running locally that returns a custom Fediverse timeline… How would you make it available to fediverse clients?
First thing I have tried to build was a Firefox extension that redirects `/timelines` requests for a masto instance to the local server, but mastodon does not look happy about the different IP.
On the other side, taking an existing client (e.g. @elk) and adding an extra timeline looks way easier, but rather ad-hoc.
-
Let’s say you have an HTTP server running locally that returns a custom Fediverse timeline… How would you make it available to fediverse clients?
First thing I have tried to build was a Firefox extension that redirects `/timelines` requests for a masto instance to the local server, but mastodon does not look happy about the different IP.
On the other side, taking an existing client (e.g. @elk) and adding an extra timeline looks way easier, but rather ad-hoc.
-
Let’s say you have an HTTP server running locally that returns a custom Fediverse timeline… How would you make it available to fediverse clients?
First thing I have tried to build was a Firefox extension that redirects `/timelines` requests for a masto instance to the local server, but mastodon does not look happy about the different IP.
On the other side, taking an existing client (e.g. @elk) and adding an extra timeline looks way easier, but rather ad-hoc.
-
Let’s say you have an HTTP server running locally that returns a custom Fediverse timeline… How would you make it available to fediverse clients?
First thing I have tried to build was a Firefox extension that redirects `/timelines` requests for a masto instance to the local server, but mastodon does not look happy about the different IP.
On the other side, taking an existing client (e.g. @elk) and adding an extra timeline looks way easier, but rather ad-hoc.
-
Let’s say you have an HTTP server running locally that returns a custom Fediverse timeline… How would you make it available to fediverse clients?
First thing I have tried to build was a Firefox extension that redirects `/timelines` requests for a masto instance to the local server, but mastodon does not look happy about the different IP.
On the other side, taking an existing client (e.g. @elk) and adding an extra timeline looks way easier, but rather ad-hoc.
-
#Mastodon #MastodonClients #AskMastodon #FediverseDevs #Devs #FediDevs
Which Mastodon client is the most extensible?
Are there any with a full-on plugin architecture with good documentation? Is that question hilarious?
I am a wee bit tired of the randomness of my feed and I want to work on that, but no idea where to get started. I don't want to add a new feature to the server software, I want to work on the front end specifically.
edit: #Python preferred, I'm good at that already.
-
#Mastodon #MastodonClients #AskMastodon #FediverseDevs #Devs #FediDevs
Which Mastodon client is the most extensible?
Are there any with a full-on plugin architecture with good documentation? Is that question hilarious?
I am a wee bit tired of the randomness of my feed and I want to work on that, but no idea where to get started. I don't want to add a new feature to the server software, I want to work on the front end specifically.
edit: #Python preferred, I'm good at that already.
-
#Mastodon #MastodonClients #AskMastodon #FediverseDevs #Devs #FediDevs
Which Mastodon client is the most extensible?
Are there any with a full-on plugin architecture with good documentation? Is that question hilarious?
I am a wee bit tired of the randomness of my feed and I want to work on that, but no idea where to get started. I don't want to add a new feature to the server software, I want to work on the front end specifically.
edit: #Python preferred, I'm good at that already.
-
#Mastodon #MastodonClients #AskMastodon #FediverseDevs #Devs #FediDevs
Which Mastodon client is the most extensible?
Are there any with a full-on plugin architecture with good documentation? Is that question hilarious?
I am a wee bit tired of the randomness of my feed and I want to work on that, but no idea where to get started. I don't want to add a new feature to the server software, I want to work on the front end specifically.
edit: #Python preferred, I'm good at that already.
-
Please boost for visibility!
I highly recommend using this app SoraSns. It’s beautiful with cool features, the best is yet to come. Currently works for #Mastodon #Misskey but will support #Calckey #Firefish accounts in the next update.
I won’t spoil the fun but there’s also some features coming that have been topics of discussion recently.
https://apps.apple.com/us/app/sorasns-for-mastodon-misskey/id6450969760
#fediverse #fedidevs #fediversedevs #SoraSns -
Please boost for visibility!
I highly recommend using this app SoraSns. It’s beautiful with cool features, the best is yet to come. Currently works for #Mastodon #Misskey but will support #Calckey #Firefish accounts in the next update.
I won’t spoil the fun but there’s also some features coming that have been topics of discussion recently.
https://apps.apple.com/us/app/sorasns-for-mastodon-misskey/id6450969760
#fediverse #fedidevs #fediversedevs #SoraSns