Show Navigation
Notices by KemoNine (kemonine@social.holdmybeer.solutions), page 2
-
Being here is like having family all over the globe. You're family, you get the news first.
The Lollipop Cloud project is currently looking for a help writing a project synopsis.
They are offering a $50 USD bounty for a more accessible synopsis of the project to use on their landing page.
Full detail : https://git.lollipop.holdmybeer.solutions/lollipop-cloud/website/issues/2
#lollipopcloud #helpwanted #bounty #writing
(image desc : lollipop cloud logo)
-
The Lollipop Cloud project strives for transparency. Our chats are open for public review, our server details are public and soon our metrics will be public too.
We have a FULL transparency report at https://lollipop.holdmybeer.solutions/page/transparency/ . This includes links to our server monitoring, git sources and more.
Our goal is *not* to hide but to help others self-host a project, a blog, chat, etc.
Transparency in what we have deployed (and how we configured our software) is important. It helps reduce the number of spoons and matches expended by others.
#lollipopcloud
(image desc : lollipop cloud logo)
-
The Lollipop Cloud project is real. Website, source code, chat rooms.
Even better?!? It's wholly self-hosted using the Lollipop Cloud sources!
😁
Inaugural blog post
https://lollipop.holdmybeer.solutions/post/2018/06/hello-there/
Official website
https://lollipop.holdmybeer.solutions/
Contact Page
(including PUBLIC Matrix/XMPP rooms)
https://lollipop.holdmybeer.solutions/page/contact/
[This time with CW for those preferring shorter toots to boost]
-
@kaniini makes a very good point.
"What is 'lollipop project'"
It's an attempt to lower the friction of self hosting. Preferably on Raspberry Pi's, Orange Pi's and other lean, small ARM mini-computer boards.
I've been quietly working for the last 3 months on building a self-hosted cloud that's rarely online (only to get updates really) as well as provide services for myself and others while 'disconnected'. Services like contact/calendar/gpx track sync. GPX tracking. Blog, more.
As I've worked on the project a few very amazing folks have made suggestions about how it could be used to lower the barrier of 'just self host' for a LOT of people floating around the federverse.
After some thinking and quiet time I realized it's time to make this a real project.
The 'Lollipop Cloud' is born of a desire to self host when nomadic, facilitating sync when 'in the jungle' or just wanting to give 🖕 to the various corporate entities who harvest your data.
A cloud in a very small box is the goal. A box the size of a credit card or as big as a rack mount server. YOU decide.
More will be online/posted soon.
If your daring the current public 'stuff' is at http://git.lollipop.holdmybeer.solutions/
-
@alcinnz @cwebber mentioned ocap-ld to me earlier but it's not quite there yet.
Hopefully with the AP network growing and getting more software we'll see things like ocap-id progress quickly.
The more we can all work together on decentralization the better IMHO. The megacorps are due for some foundation shaking.
https://w3c-ccg.github.io/ocap-ld/
-
Remember
Not everyone can self host software systems.
Not everyone wants to self host software systems.
Not everyone gives a shit about tech
Most people just want to go online, do their thing and move on with their day
If there is a mass exodus from GitHub / GitLab or others we people hosting our own infra need to be good about discovery, community building, community engagement and more.
We also need to figure out how to federate authn/authz. I'll skip over submitting small things if it means yet another account on yet another server run by yet another random.
Centralization isn't great but it does facilitate discovery, community and engagement.
We need to keep this at the back of our mind.
-
@kaniini @href I know this but I'm in a position of convincing others that this is the case.
The pleroma devs are about the code, quality of code and reasonable features and reasonable prioritization of development.
As a professional programmer I <3 this approach.
It can be a pain in the ass to put forth to non-devs though.
I deployed pleroma *because* you and other are decidedly non-assholes by default and focused on building good code and being reasonable about said code.
Aside from the code the pacmaning of gnusocial instances by pleroma puts the non-programmer ethos in a difficult position. I don't assume you are pro-jackass admin but at the same time your software is taking over those instances.
*That* is the hard problem to solve and one I've already argued in favor of pleroma