Skip Navigation

Posts
2
Comments
72
Joined
2 yr. ago

  • Its a responsive designed website, why do you need an Application?

  • We use radiators because every house had a gas line for heating, boiling water and cooking. Radiators were more efficient than gas fires.

    Most residential gas boilers are 20-35kwh, air source heat pumps (£4k-£5k) are linked to compression cylinders which provided 11kwh of heating and cost of £9k each, with the need for a water tank, etc... and then installation cost.

    Putting air conditioning in still requires the heat pump with a unit (£500-£1k) for each room, plus installation costs.

    If you take a 3 bed room house, you are looking at £15k for an air source heat pump vs £9k to put air conditioning into every room (it gets worse for air sourced heat pumps the bigger the property).

    Once you move to air conditioning for each room you don't need radiators. This means your hot water supply is dishwashers, washing machines, taps, baths and showers.

    Dishwashers and washing machines boil their own water (for efficiency).

    Taps and showers have electric solutions. The price difference between the two is so great you could buy a hot tub to replace your bath.

    Air source heat pumps don't make sense

  • It isn't surprising.

    I tried to replace my gas boiler in 2020 (it failed), I reached out to 8 companies to get an estimate for a ground or air sourced heat pump. 5 didn't pickup/return emails. 2 told me they don't do residential.

    The last qouted £21k plus installation costs, then told me if I had a gas boiler that would be cheaper to maintain/run.

    I have just met someone to qoute for air conditioning, they told me you can use it for heating. The initial estimate is the same as a gas boiler.

  • I am currently teaching python and JavaScript devs Typescript. Everytime they hit a problem they switch to any

    Sigh

  • Activity Pub has a few parts, Lemmy implements the Threaded message part.

    Mastodon implements a short messaging (posts) part. Meta's Threads will implement this.

    KBin implemented both parts, within KBin you'll see microblog as an option for magazines (communities/subredits). This shows either 'posts' made to the magazine or posts with hastags associated with the magazine.

    The posts and threaded message parts have overlap in how they work so mastodon users can see certain threaded messages and comment on them.

  • Github stars is not a good metric, firstly because KBin is hosted on codeberg but mainly because a healthy project has lots of unique contributors and regular updates/enhancements.

    KBin has 79 open Pull Requests, while Lemmy has 29. From a visual check PR's seem to be older than 2 weeks. Its hard to say one is "healthier" than the other, without scraping information into a spreadsheet.

    Secondly Rust is new and has a lot of hype surrounding it, as a result you get a lot of people using it on random projects.

    Languages have strengths and weaknesses and developer ecosystems build on the strengths.

    For example if I was writing a web application with a database backend I would choose C#, Java or Node.js because there are loads of libraries, tools and frameworks to make it really easy.

    Rust is gaining a lot of adoption by embedded system users (replacing C mostly). Lemmy is the only Rust based web server project I am aware of. Which means the level of work to do anything and to keep it updated falls on the Lemmy devs rather than spread out amongst a larger community.

    Everyone loves to insult PHP but it has a niche in webservers and won't disappear anytime soon. KBin effort will thus be spent on KBin.

  • There is a standard for sharing tweet style information and for threaded type information between websites.

    You have software which implements the tweet standard (Mastodon), the threaded standard (lemmy) and both (KBin).

    You'll notice some communities will be community@kbin.social or community@kbin.cafe, etc.. this indicates they are not local to the website your using and those addresses are KBin instances, its just your website has a copy of the information.

    KBin is newer than Lemmy, it has a fairly simple responsive design that works well on mobile. Lemmy has a REST api so its easier to build mobile applications, a lot of people seem to expect/need to access websites via mobile applications.

    The key difference is Lemmy is developed by Tankies, they think China's genocide of Ughurs is justified and they administer lemmy.ml.

  • Reading the article that isn't the goal.

    They are working on controlling access to the wider internet. The goal is to push people off of western services on to ones they control. This is so they can control the information their citizens see

    They wouldn't stop Russian bot farms or hacking.

  • Engineering is tradeoffs.

    A command shell is focused on file operations and starting/stopping applications. So it makes it easy to do those things.

    You can use scripting languages (e.g. Node.js/Python) to do everything bash does but they are for general purpose computing and so what and how you perform a task becomes more complicated.

    This is why its important to know multiple languages, since each one will make specific tasks easier and a community forms around them as a result.

    If I want to mess with the file system/configuration I will use Bash, if I want to build a website I will use Typescript, if I want to train a machine learning model I will use Python, if I am data engineering I will use Java, etc .

  • You've just moved the packaging problem from distributions to app developers.

    The reason you have issues is historically app developers weren't interested in packaging their application so distributions would figure it out.

    If app developers want to package deb, rpm, etc.. packages it would also solve the problem.

  • Nice out of date dependencies with those lovely security vulnerabilities!

  • If Firefox, MS Teams, etc.. were on a website called "nazis.social" would you still happily sign up?

    Tankies will tell you the rape and abduction of Ukrainian children by Russian soliders is western propoganda and Russia is right to invade because Ukraine isn't a country and provoked them.

    Tankies will tell you China's forced sterilisation of Ughurs and their mass execution for organ donation is just western propoganda or justified because the west has done worse things.

    This is why I asked my original question, their views are as extreme and unpleasant as Nazi's. The only difference is general awareness of how vile they are.

    Personally I don't care what communities are on lemmy.ml or lemmygrad.ml. Those instances are administered by Tankies, everyone on those instances has chosen to associate themselves with Tankies.

    I choose not to associate with Tankies.

  • KBin/Lemmy should provide a combined local view for duplicated magazines/communities across the fediverse. Treating the concept like a hashtag.

    The point of the fediverse is to distribute content so no one has a monopoly. People squatting on communities/magazines don't understand there is nothing stopping people creating one on a hundred other instances.

    Each kbin/lemmy instance decides to follow magazines/communities from others through activity pub and stores it locally for the instance.

    Having the UI retrieve all local posts with the same magazine/community name (e.g. m/startrek@kbin.social c/startrek@lemmy.world). Wouldn't be hugely difficult, I believe Kbin uses postgres database as the local store and suspect it would be a tweak to the SQL query it runs.

    Even if that wasn't an option, there is a means to get all of the magazines/communities from the kbin UI/lemmy REST API. As well as retrieve all posts for a specific magazine/community. So you could do it entirely in a web client, for KBin it would be more work.

    The combined view wouldn't change how you comment on specific posts. The issue is where do you post and what view would take dominance (e.g. if a magazine had themed itself).

    The solution here would be to default your local instance if it exists or the instance providing the most posts/comments. Perhaps with a drop down so users can choose.

    I would also configure things so instances can select a site wide default if they can't moderate it effectively. For example pushing all posts to the star trek instance rather than local magazine with a mod who is MIA.

    This would remove most of the concerns users have about the fediverse, since they wouldn't be confronted by different instances. To them the fediverse is insert instance it would also encourage distribution of content.

  • The big argument for mono repos is checking out multiple repositories is "hard" while checking out one repository is "easy" but...

    Service Oriented Architecture became a thing because monolithic code bases were often becoming spaghetti. I worked on a project where removing an option from a preference window (max map zoom), broke a message table (because the number of visible rows in a table (not its size in the UI) was linked to the max zoom you supplied to a map library, for no reason).

    Thus the idea you should wrap everything you do as a self contained service, with a known interface. The idea being you could write an entirely new implementation of a service, implement the interface and everything would work. Microservices are a continuation of this idea.

    Yet every node/python based mono repo I have seen will have python files directly imported filed from inside anouther component/service. Not simply common aretfacts but all sorts of random parts. Subverting the concept of micro service (and recreating the problem).

    Separate repositories block this because each repository will be built in isolation on a CI, flagging the link. This forces you to release each repository and pull things in as a dependency. Which encourages you to design code to support that.

    A common monorepo problem is to shove everything in a docker image and call it a day. Then if you need a class from one monorepo in anouther one, you don't have an artefacts so lazy devs just copy/paste files between monorepos.

    Monorepos aren't bad practice by themselves, they encourage bad practice. Separate repositories encourage good practice (literally the need to manage them separately drives it).

  • Debian Bookworm.

    The purpose of my home computer is to help me work or play games. I don't want to expend effort updating/fixing my computer.

    I would use Ubuntu but Snaps is impossible to turn off and they are insanely slow. CentOS/RHEL/Rocky seem to make every package require a full Gnome install and I use KDE. That only leaves OpenSUSE and the multi arch Debian installer makes installing Debian easier than OpenSUSE.