#postnuke — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #postnuke, aggregated by home.social.
-
Blog Question Challenge
Es gibt wieder eine Blogparade! Wisst ihr noch – diese Aktionen, in denen alle in ihrem Blog eine Liste von Fragen beantwortet haben. Gab es lange nicht mehr, weil alle meinte, Twitter und Facebook seien besser als ein eigenes Blog.
https://kaffeeringe.de/2025/02/12/blog-question-challenge/
#Blog #blogFragen #Blogparade #Fördeflüsterer #Kiel #Kiel4Kiel #Landesblog #MattMullenweg #OpenSource #Pixelfed #Postnuke #Wordpress
-
Blog Question Challenge
Es gibt wieder eine Blogparade! Wisst ihr noch – diese Aktionen, in denen alle in ihrem Blog eine Liste von Fragen beantwortet haben. Gab es lange nicht mehr, weil alle meinte, Twitter und Facebook seien besser als ein eigenes Blog.
https://kaffeeringe.de/2025/02/12/blog-question-challenge/
#Blog #blogFragen #Blogparade #Fördeflüsterer #Kiel #Kiel4Kiel #Landesblog #MattMullenweg #OpenSource #Pixelfed #Postnuke #Wordpress
-
Blog Question Challenge
Es gibt wieder eine Blogparade! Wisst ihr noch – diese Aktionen, in denen alle in ihrem Blog eine Liste von Fragen beantwortet haben. Gab es lange nicht mehr, weil alle meinte, Twitter und Facebook seien besser als ein eigenes Blog.
https://kaffeeringe.de/2025/02/12/blog-question-challenge/
#Blog #blogFragen #Blogparade #Fördeflüsterer #Kiel #Kiel4Kiel #Landesblog #MattMullenweg #OpenSource #Pixelfed #Postnuke #Wordpress
-
Blog Question Challenge
Es gibt wieder eine Blogparade! Wisst ihr noch – diese Aktionen, in denen alle in ihrem Blog eine Liste von Fragen beantwortet haben. Gab es lange nicht mehr, weil alle meinte, Twitter und Facebook seien besser als ein eigenes Blog.
https://kaffeeringe.de/2025/02/12/blog-question-challenge/
#Blog #blogFragen #Blogparade #Fördeflüsterer #Kiel #Kiel4Kiel #Landesblog #MattMullenweg #OpenSource #Pixelfed #Postnuke #Wordpress
-
Blog Question Challenge
Es gibt wieder eine Blogparade! Wisst ihr noch – diese Aktionen, in denen alle in ihrem Blog eine Liste von Fragen beantwortet haben. Gab es lange nicht mehr, weil alle meinte, Twitter und Facebook seien besser als ein eigenes Blog.
https://kaffeeringe.de/2025/02/12/blog-question-challenge/
#Blog #blogFragen #Blogparade #Fördeflüsterer #Kiel #Kiel4Kiel #Landesblog #MattMullenweg #OpenSource #Pixelfed #Postnuke #Wordpress
-
One way to promote the #Fediverse is by making the different fediverse software support custom profile skins and themes. This can potentially create an ecosystem of skin and theme creators, which in turn will make more people talk about it.
I differentiate between a skin and a theme because:
* A “skin” is like changing the CSS of the default layout. Adding an image here and there, new icons, and colours and gradients.
* While a “theme” can change the layout itself. The widgets available, or shuffle them around. Possible even a way to add custom ones (careful with this though).Remember the original #CMS in late 90s to 2010? #PHPnuke #PostNuke #Xaraya etc.?
You can add, remove, and move widgets around. Use custom ones easily. Change colours easily. Change the widths, the columns, and so on. That is a “theme”. There were even third-party frontend packages a developer can use so they don't have to worry much about it.
Skinning is the simplest method; and this was what made #Plurk popular when it launched in May 2008 (yes, Plurk is as old as the Fediverse network). There was a Plurk skin ecosystem, which in turn increased the number of people talking about Plurk.
Apply the theming feature from the early CMS brands with Plurk's user-level skinning feature, and we create a playground for the users.
#Misskey and forks already had a good start with their user-level skinning feature (and user-level plugins at that). We just need to see it in the other popular fediverse software.
Make it easier to understand. Write guidelines in layman's terms, not dev terms, and maybe, just maybe, we can spark the interest of new users. Who doesn't want a customisable user profile?
-
Ummm... Sort of, but not really.
I'm not bashing on you, really. There was a #Myspace era that kicked all this off, innocently - sure, #Google and #Apple were already showing the way of #surveillance state data farming prototypes already, and pre-Faceplant or other social networking consisted mostly of privacy respecting mediums like #IRC, #Usenet, #CMSes with groups such as MD-Pro and #PostNuke, or #forumware like #vBulletin, #FudForim, and #PhpBB.
Up until that point it was perfectly natural for everyone to depend upon their own self-hosted infrastructure with websites and shopping carts and their own merchant accounts, their own blogs, their own presence that was unique to them in complete control of their "Privacy"...
Then, many people caved in to the allure of #instant gratification - let someone else take care of that for you. You don't need to take responsibility for yourself or be accountable. You don't even need to understand the easy parts of the technology anymore, you just have to agree to be #subjugated #chattel, and become the product... We'll even make it so easy and seamless that you won't even begin to feel the theft for a decade or so, until there's nothing about you that doesn't belong to us - your #identity and even your #medical records which we're going to sell, you already gave us permission.
So yes. It's a good thing to start being #accountable for ourselves and our own presence and #privacy and commerce through our own #FOSS based infrastructure on the Internet - and I'm not talking about joining some big #monolithic #silo in the #Fediverse - because you are the Fediverse, you, on a #SmallWeb or single user instance that is so simple to #self-host, you can simply subscribe to a hosting provider to host it for you if you like.... That's how we built the Internet to be, then... **People sold their souls to the company store.**
#tallship #freedom #surveillance state
⛵
.
♲ nocorp.net/@koss/1101722100115… -
@r00tobo Oh yeah, I get that as well - I remember the #postnuke wars after MagicX took over as Lead Dev, which lead to multiple forks and new projects, none of which were completely compatible with each other, which created a lot of bad blood and left people worrying which one to use.
(I missed the #phpnuke wars, which lead to the forming of all the *nuke forks, thankfully).